Petals
macOS · one orchestration · your logins

Five AI coders.
One brain.
One build.

Claude Code, Codex, Grok, Kimi and Kiro — running as one team on one project, every agent reading and writing the same shared brain. You describe the build once. Petals distributes, watches, and integrates.

Get Petals Watch the film · 84s
The team Claude CodeCodexGrokKimiKiro + Petals Build, the local house agent
Petals — calculator-modern-minimal
✿
✳
⌬
◎
K
✿ Petals Build · planner ✓ done
❯ build a modern minimal calculator app
✎ edit PETALS.md · plan — one task per agent
tasks: structure · logic · design · integration
✚ write index.html · 96 lines ✓
STATUS: DONE — structure ready for the team
C Claude Code ✓ done
“You are one member of a team building this project…”
⏺ Opening PETALS.md — my task: calculator logic
✓ app.js · operations, memory, keyboard
note → Updates board: “exposed calc() for sci mode”
STATUS: DONE — logic wired to the team's markup
G Grok ✓ done
reading PETALS.md — my task: scientific mode
⚡ Writing scientific.js…
✓ scientific.js · trig, log, memory keys
PETALS.md updated · ready for Claude to import
STATUS: DONE — worked for 51s
C Claude Code · integration lead ✓ done
⏺ My task's done; switching to integration.
checking the Updates board — fixing only what's broken
✎ index.html · wire scientific.js import
✚ PETALS.md · Integration report + Team note
STATUS: INTEGRATED · verified end to end
Project complete · one brain, four hands · preview 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.
01 · The USP

One brain.
Every agent reads it.
Every agent writes it.

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.

PETALS.md
  • 01
    The plan lives thereOne prompt becomes a work distribution — ### Task — Claude Code, one disjoint slice per agent, no collisions by design.
  • 02
    Notes flow through itAgents 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.
  • 03
    Done is declared thereEach agent ends its slice with STATUS: DONE — Petals watches the brain and the terminals, and ticks them off as they land.
  • 04
    It ends with a team noteThe lead integrates, verifies end to end, and writes an Integration report — plus a short note signed by the whole team.
02 · The film

Eighty-four seconds,
start to bloom.

03 · The agents

Every major coding CLI.
Named, known, ready.

Petals auto-detects what's installed and uses the logins you already have. No wrappers, no forks — the real tools, in real terminals.

Claude Code
by Anthropic

The deep reasoner. Architecture, tricky refactors, long-horizon tasks — resumes its conversation across Petals launches.

claude · auto-detected
Codex
by OpenAI

Fast, precise implementation. Great at grinding through well-scoped feature work while the others think big.

codex · auto-detected
Grok
by xAI

Quick, opinionated, tireless. Point it at tests, tooling, or a stubborn bug and let it chew.

grok · auto-detected
Kimi
by Moonshot AI

A bulk-implementation workhorse with a huge context window — hand it the wide, repetitive slices of the plan.

kimi · auto-detected
Kiro
by AWS

Spec-driven and methodical. Strong on structured tasks, cloud wiring, and keeping work traceable.

kiro-cli · auto-detected
Petals Build
built in · runs local

The house agent. Runs on your local Ollama models (or Groq / Mistral keys), with a live command palette and drag-and-drop attachments.

included · no API key needed
Sign in once per CLI — Petals detects your existing logins and shows exactly who's ready in Settings.
👾
Creatures in the notchOne pixel companion per pane — pink while working, green when done, amber when they need you. Approvals open the island by themselves.
🌐
Preview without leavingFinished builds render inside Petals; minimize the preview into an elegant edge drawer and pull it back with a click.
🔔
Approvals, your wayApprove a command for this terminal, this session, or the whole project — asked once, remembered properly.
✓
Done means donePer-agent ticks, a chime per landing, and a project report with each agent's audit — plus the team's joint note.
04 · Petals Build

A house agent that runs
entirely on your Mac.

  • /
    A live command paletteType / and every command appears as you type — arrows choose, tab completes, enter runs.
  • ⊕
    Drag & drop anythingPDFs, Word docs, images, code — dropped on the pane, attached instantly, page counts and all.
  • ⚡︎
    Local models, zero keysAuto-picks your strongest Ollama coding model, or runs on Groq / Mistral keys — switch mid-session with /model.
  • ✎
    A real toolboxRead, write, edit, search, fetch, run, undo, diff — every action collapses into a tidy receipt card.
petals build
❯ /mo
❯ /modelswitch model — picker if no name
  /modelsinstalled models
Pick a model  ↑↓ choose · enter · esc
    qwen2.5:7b  ● current ★ recommended
  ❯ qwen3-vl:4b
⊕ attached brief.pdf · 4 pages — rides along with your message
✚ write index.html · 214 lines ✓
05 · Pricing

Simple, like it should be.

Every feature in every plan. Your logins and local models — Petals never meters your tokens.

Annual
$45.99/ year
All of Petals, always current.
  • ✓ All CLI panes + Petals Build
  • ✓ One-brain orchestration
  • ✓ Project reports & team notes
  • ✓ Notch creatures & approvals
  • ✓ Every update while subscribed
Start with Annual
Best value
Lifetime
$99.99once, forever
Pay once. Bloom forever.
  • ✓ Everything in Annual
  • ✓ Lifetime license — no renewals
  • ✓ All future updates included
  • ✓ Less than three months of most AI subscriptions
Get Lifetime
Runs on your machine with your own model accounts — no token markups, no lock-in.