Needs approval to run the rooms migration.
vitest run rooms
Rewriting the pricing page copy.
Finished the rate limit for the push route.
Grenade listens to Claude Code's own hooks, so your phone knows the moment Claude needs a permission, asks a question or finishes. Answer on a card, by typing, or by voice.
Grenade starts Claude Code with its own hooks, passed for that session only: nothing in ~/.claude changes. They report to the daemon on your own Mac and nowhere else. The one-line summary on each session is written on the Mac through your Claude Code login, so there is no API key to set.
grenade setup
grenade new api --cwd ~/code/api --agent claude
Not installed yet? Two steps on the Mac.
No. Grenade starts the Claude Code that is already on your Mac, with the login it already has. There is no Grenade account: you pair your phone by scanning a QR code on the Mac.
No. Its hooks are passed to Claude Code for that session only, so nothing in ~/.claude changes.
Yes. When Claude wants to run a command or edit a file, the phone shows the request in full on a card. Allow it once, or deny it and say what to do instead. Questions and plans arrive the same way.
Remote Control reaches one Claude Code session through your Anthropic account. Grenade lists every agent on your Mac, Codex and shells included, with no account, and shows which one is waiting. The two side by side.
Yes. Sessions in the same folder form a group, and each one shows a color: amber when it needs an answer, green when it has finished, blue while it works.
The agent runs on your Mac as it always does, and Grenade adds no server that can read it. What your phone shows of the terminal travels end-to-end encrypted, directly on your Wi‑Fi or through a relay that sees only encrypted bytes.
The session keeps running: it lives in tmux on your Mac, so closing a window ends nothing. The phone reconnects by itself and shows where the session is now.