Supervise a coding agent
Choose which agent actions wait for a person, approve or deny them, and undo what an agent session created.
All pages
Each project has an approval policy. It decides which calls from a coding agent wait for a person before they run:
standard, the default: deleting a project, an environment, a service or a custom domain waits, and so does applying staged changes that delete a variable, a service or a database copy.strict, on Team: those deletions wait, and so does launching a service that has a monthly price.sandbox: nothing waits.
On Solo, setting strict is refused. A project that already holds strict runs as standard there and keeps strict for when the workspace moves back to Team. Lowering the policy works on every plan.
A call you make yourself never waits. Ghaym counts a call as an agent's when the CLI runs inside Claude Code or Cursor, or when GHAYM_AGENT names the agent. Set a project's policy with one command. With the CLI:
ghaym cloud projects update shop --approval-policy strict- A call that waits doesn't run.
The agent's command exits with
6and an approval ID, and the agent runsghaym cloud approvals wait <id>, which returns once the request is decided. Nothing changes while it waits. - In the console, open the project. Open the activity: each request sits above the feed, names the agent, and says what it would do, for example "Deleting the environment tears down every service running in it." A request for the whole project is marked Whole project; the others belong to the environment whose activity you're reading.
Its Activity button shows how many requests are waiting on you.
- Choose Approve the request to run it, or Deny.
For a deletion or a launch, the button says Approve the deletion or Approve the launch. A request nobody answers lapses on its own, at the time the card shows after Lapses automatically.
Only the person whose agent made the request can answer it, and an agent can't answer any. From your own terminal, outside the agent:
ghaym cloud approvals list --status pending
ghaym cloud approvals approve <id>
ghaym cloud approvals deny <id>approvals wait exits 0 only when the request was approved. A denied or lapsed request exits 6, and so does a wait that runs out of time: 300 seconds, unless --timeout sets another. The agent then waits again instead of repeating the call.
Each CLI command an agent runs opens a session, unless GHAYM_SESSION holds one ID for the whole chain.
ghaym cloud sessions list --project shop
ghaym cloud sessions get <id>
ghaym cloud sessions watch <id>sessions list shows each session's agent, intent, actions, failures and waiting requests. sessions get shows one session's actions and what they touched, and sessions watch follows its actions live.
To undo a session, read the plan first, then run it:
ghaym cloud sessions rollback <id> --dry-run
ghaym cloud sessions rollback <id>A rollback deletes the projects, environments, services and custom domains the session created that still exist, newest first. Every other action is listed with the reason it can't be undone: a change kept no earlier value, a deletion is final, and a deploy is undone by rolling back to an earlier one. An agent that asks for a rollback waits for a person, unless the project is sandbox.