Wake the agent’s sandbox
Ask the daemon serving this agent to bring its cluster sandbox to Running without starting a turn, so the workspace reads become available again. Pass sessionId to wake that isolated session’s own sandbox instead of the agent’s: it is only ever resumed onto the claim it already has, so a session whose sandbox was removed answers 404 with code WORKSPACE_SANDBOX_REMOVED (its next message creates a new one), and a daemon too old to wake one session wakes the agent’s sandbox as before. A sessionId the caller cannot browse reads 404. Answers with what the daemon observed: 202 with running (reachable now) or starting (resume in flight — poll the workspace read); 200 with unsupported when there is nothing to wake (a machine-placed agent, or a daemon that runs no sandboxes). Wakes are debounced per sandbox: one in flight is joined, and one settled within the last 30 s is answered from its result. For a pool agent nobody currently serves, the wake reaches a live member, which claims the agent the way a turn would. Requires edit access; 503 when no daemon can be reached.
Authorization
bearerAuth In: header
Path Parameters
Query Parameters
1 <= lengthResponse Body
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/v1/orgs/string/agents/string/wake"{ "state": "running"}