Wants to run migration 0042.
Building the checkout form.
Retrying failed payments.
✓ 112 passed
Documented the orders API.
Published the release notes.
Split a feature across several Claude Code sessions and the hard part is no longer the code: it is knowing which terminal is waiting. Grenade runs each agent in a session of its own, groups them by project and gives each one a color.
Each grenade new in the same folder joins that folder's group. --agent picks what runs.
Not installed yet? Two steps on the Mac.
grenade new api --cwd ~/code/shop --agent claude
grenade new web --cwd ~/code/shop --agent claude
grenade new worker --cwd ~/code/shop --agent codex
grenade new tests --cwd ~/code/shop --agent shell
grenade ls # every session and its status
No. Grenade starts each agent in the folder you give it and does not touch your repository. To keep agents apart, give each its own folder or worktree with --cwd, and put them in one group with --with.
Claude Code and Codex tell the daemon on your Mac through their own hooks, passed for that session only. A plain shell has no hooks, so its status is read from the screen.
Yes. The Grenade Mac app shows a project's agents as panes side by side, and grenade terminal iterm opens each group as an iTerm2 tab with its sessions side by side.
No. These are separate Claude Code sessions, each with its own conversation, that you start and steer yourself. What a session does inside, subagents included, is Claude Code's own.