THE HOUSE AGENT · RUNS ENTIRELY ON YOUR MAC
Petals Build,
petal by petal.
The built-in agent that ships with Petals: local models, zero API keys, and a toolbox that now rivals the biggest CLIs, with a few tricks none of them have.
Type / and everything appears.
A live command palette, right in the terminal: every command surfaces as you type, arrows choose, tab completes, enter runs. Commands with follow-ups open arrow-key pickers, models, folders, files, checkpoints.
Drop your own commands into ~/.petals/commands and they join the palette like they were born there.
Every prompt is a
save point.
Before each prompt, Petals Build snapshots your whole project. /rewind opens a picker of every moment, pick one and the files roll back, including files that didn't exist yet. Rewind all the way to blank.
Underneath, every successful turn becomes a real git commit. /undo , /diff and /rewind sit on actual history, not hope.
Leave a comment.
It gets done.
Type an AI! comment in any file, from any editor, and save. Within seconds the idle agent notices, does exactly what the comment asks, removes the marker, and commits. You never left your editor.
Broken files never reach you.
After every write, Petals Build checks its own work, JSON parsed, Python compiled, JS syntax-checked, shell linted, HTML tags balanced. Anything broken goes straight back to the model for a fix round before the turn ends.
WebKit screenshots index.html at 720px, real layout
"1. Text is nearly invisible against the dark background…"
✎ edit styles.css · color: #f4f4f5 · contrast restored ✓
It looks at what
it built. Literally.
/verify renders your page with real WebKit, hands the screenshot to a local vision model, and lets it judge like a design critic. Real problems come back as fixes, contrast, layout, overflow, unreadable text.
Cloud tools do browser checks. Nobody else does it fully offline.
mistral-large · plans in the cloud
qwen2.5:7b · types locally, for free
One model thinks.
Another types.
/architect splits the work: a stronger model, cloud or your biggest local, writes the plan; your fast everyday model executes it exactly. Aider proved the pattern. Petals Build makes it one picker.
Thirteen tools. One action language.
open any project file
create files whole
surgical search & replace
add to a file's end
shell, always asks first
see the project's shape
grep everything
pull a page or API
show the result
its own task board
run parallel subtasks
any MCP server's tools
Small things, done properly.
Plan first, build after your yes
A numbered plan, then one picker: Build it, or hold.
Drag & drop anything
PDFs with page counts, Word docs, images, code, attached instantly.
Sessions that survive
Every turn saved per project; pick up where you left off.
The session as a page
One command exports a beautiful dark transcript to send around.
Your rules, enforced
Hook scripts veto commands, format on write, notify on finish.
Skills that self-attach
Brain docs and SKILL.md packs surface when a prompt needs them.
Speak the prompt
On-device dictation, press Enter, review, send. Stays on your Mac.
A repo map, always
The model sees your project's shape before it acts, no blind edits.
All of it, included.
Petals Build ships with every copy of Petals no extra key, no extra fee.
