Recipes
A recipe is a saved brief plus its preferred mode, budget caps, and the set of tools its planner is allowed to call. Recipes are how you turn "a thing I keep typing into chat" into "a one-click workflow." Six ship with v1 and you can author your own.
What ships with v1
market_scan — Factory. Given a list of competitor URLs, produces a one-page strategic brief and a comparison table. Average run: 8 agents, ~$0.35, ~14 minutes.
ship_a_feature — Factory. Given a GitHub repo and a feature brief, proposes a PR with code and tests. Requires GitHub OAuth in Settings → Integrations. Average run: 12 agents, ~$1.20.
inbox_triage, daily_journal, lead_research, competitor_diff — smaller live-mode recipes documented inside the app.
Writing your own
Recipes are a tiny Python module. Drop one in your project's recipes/ directory and Loom hot-reloads it:
from loom.recipes import Recipe
market_scan = Recipe(
name="Market scan",
mode="autonomous",
brief_template=(
"Visit each URL in {urls}, extract pricing, positioning, "
"and ICP, then write a 1-page strategic brief to "
"final/brief.md."
),
default_caps={"max_steps": 80, "max_usd": 1.50},
allowed_tools=["web_fetch", "web_search", "file_io"],
expected_agents=8,
)Sharing recipes
Recipes are portable. Export from the recipe card's overflow menu; the result is a single JSON file you can drop into a teammate's Loom instance or check into your repo at .loom/recipes/. Loom auto-imports anything under that path on next startup.