One Brain
Infinite Outcomes
Get Petals
Petals orchestrates five AI coders as one team
on one project every agent, one shared brain
Claude Code
Codex
Grok
Kimi
Kiro
Petals BuildClaude CodeCodexGrokKimiKiroPetals BuildClaude CodeCodexGrokKimiKiroPetals BuildA real session, wireframed: one prompt became a plan in the shared brain, each agent took its task, left notes for the others, and the lead integrated.
One brain.
5 Coders. Zero Silos
Other tools give you tabs. Petals gives you a team because every CLI works from the same file: PETALS.md, the shared brain that lives inside your project.
The plan lives there
One prompt becomes a work distribution ### Task → Claude Code , one disjoint slice per agent, no collisions by design.
Notes flow through it
Agents leave one line heads ups on the Updates board "renamed a function", "exposed calc() for sci mode" and skim each other's notes to stay in sync.
Done is declared there
Each agent ends its slice with STATUS: DONE Petals watches the brain and the terminals, and ticks them off as they land.
It ends with a team note
The lead integrates, verifies end to end, and writes an integration report plus a short note signed by the whole team.
Eighty four seconds, start to bloom.
Every major coding
CLI Named, known, ready.
A real session, wireframed: one prompt became a plan in the shared brain, each agent took its task, left notes for the others, and the lead integrated.
Claude Code
by AnthropicAnalyzing markets and moodboarding to define a strategic visual direction and wireframe foundation before execution.
Codex
by OpenAIAnalyzing markets and moodboarding to define a strategic visual direction and wireframe foundation before execution.
Grok
by xAIAnalyzing markets and moodboarding to define a strategic visual direction and wireframe foundation before execution.
Kimi
by Moonshot AIAnalyzing markets and moodboarding to define a strategic visual direction and wireframe foundation before execution.
Kiro
by AWSAnalyzing markets and moodboarding to define a strategic visual direction and wireframe foundation before execution.
Petals Build
Built inAnalyzing markets and moodboarding to define a strategic visual direction and wireframe foundation before execution.
Sign in once per CLI - Petals detects your existing login and shows exactly who's ready in Settings.
Creatures in the notch
One pixel companion per pane, pink while working, green when done, amber when they need you. Approvals open the island by themselves.
Preview without leaving
Finished builds render inside Petals; minimize the preview into an elegant edge drawer and pull it back with a click.
Approvals, your way
Approve a command for this terminal, this session, or the whole project, asked once, remembered properly.
Done means done
Per-agent ticks, a chime per landing, and a project report with each agent's audit, plus the team's joint note.
A house agent that runs
entirely on your Mac.
Every feature, petal by petal →A live command palette
Type / and every command appears as you type, arrows choose, tab completes, enter runs.
Drag & drop anything
PDFs, Word docs, images, code, dropped on the pane, attached instantly, page counts and all.
Local models, zero keys
Auto picks your strongest Ollama coding model, or runs on Groq / Mistral keys, switch mid session with /model.
A real toolbox
Read, write, edit, search, fetch, run, undo, diff, every action collapses into a tidy receipt card.
Simple, like it should be.
Every feature in every plan. Your logins and local models, Petals never meters your tokens.
Annual
All of Petals, always current.
- ✓All CLI panes + Petals Build
- ✓One brain orchestration
- ✓Project reports & team notes
- ✓Notch creatures & approvals
- ✓Every update while subscribed
Lifetime
Pay once. Bloom forever.
- ✓Everything in Annual
- ✓Lifetime license, no renewals
- ✓All future updates included
- ✓Less than three months of most
AI subscriptions
Runs on your machine with your own model accounts, no token markups, no lock-in.
