Approvals and decisions
Your team stops and asks you in a few places: before it builds a large plan, before it ships, when it has a question only you can answer, and when something fails in a way it can't fix alone. Every one of those shows up in two places: inline in its thread, and in Needs you.
Decision cards
A decision card has a saffron edge and sits in the thread right where the work is. The main action is always on ⌘↵.
| Card | Main action | Other actions |
|---|---|---|
| A plan is ready | Approve plan | Send back with a note |
| Ready to ship | Ship it | View changes, Send back |
| A question for you | Answer | |
| Something failed | Retry | Open the task |
| Task limit reached | Raise limit | Stop here |
Send back takes a short note ("keep the old endpoint working too") and returns the task to the team, who plan or build again with it in mind. View changes opens the diff before you decide.
Needs you
Needs you in the sidebar lists every decision across the project, newest first, with its count in saffron. Each item has the same inline actions as its card, so you can approve or answer without opening the thread. Click an item to jump to it in context.
ThreadGrid also sends a Mac notification for anything that needs you.
The gates
In Settings → Autonomy & gates you choose where the team stops for you:
| Gate | Gated (default) | Autopilot |
|---|---|---|
| Ideas | Wait for you to promote them | Promoted on their own when they score 7 or more |
| Plans | Large tasks (size L and above) wait for approval | Don't wait |
| Ships | Every ship waits for Ship it | Don't wait |
You can set the plan gate to wait for every plan, only large ones or never.
The composer pills override the gates for a single ask: Plan first forces a plan approval, and Ship when ready skips the ship approval.
Checks are never a gate you can turn off. Verify (code review and QA) runs on every task, and work that fails verify doesn't ship.
Guardrails
Approvals decide when your team acts. Guardrails decide what they can do at all. Agents running in ThreadGrid can't:
- push, switch branches, rebase, tag, change remotes or rewrite git history;
- use
ghto open pull requests, publish releases or change repositories; - publish packages or deploy;
- use
sudo, the Keychain or system commands; - edit files outside their own worktree;
- use MCP servers other than ThreadGrid's board and 21st.dev, unless you allow them.
Pushing, tagging, pull requests and deploys happen only in the ship step, which is ThreadGrid's own code, using the targets you've turned on. Codex teammates also run inside Codex's sandbox.
These are guardrails, not a sandbox: agents run as you, on your Mac. Keep secrets out of your repositories, as you would with any tool.
Pausing and stopping
- Pause a project from its menu. Running steps finish; nothing new starts.
- The menu bar icon has Pause everything and Stop everything now.
- Closing the window doesn't stop the team; it keeps working from the menu bar. Choose Quit When Done to let running steps finish first, or Quit Now.
Something unclear or out of date? Email [email protected].