Why is a CoAgent not responding or no longer working?
Check the work delivery, computer state, AI connection and access separately. A computer can be running without an active task, and a connected AI subscription does not prove that the CoAgent received your assignment.
An Account owner or admin can perform the following checks in Admin. If you do not have either role, ask an existing owner or admin to check the CoAgent and share the relevant error.
- Open Admin, select CoAgents → CoAgents, and open the intended CoAgent.
- Expand Computer and advanced settings and check Computer → Status and any error. Sleeping allows automatic wake when supported work arrives. Paused blocks automatic work until you choose Resume work. Provisioning, Waking or Upgrading means a transition is in progress; Failed needs the displayed error investigated.
- Check the connection status under AI subscription, such as Connected or Reconnect required. If the status is Not connected, the section is titled Connect ChatGPT or Connect Claude instead. Use the connection recovery guide for an expired sign-in or Reconnect required. Check the provider's usage allowance as well as Socra billing.
- Select View activity. Find the relevant event and read its outcome or View error. Inspect the original Channels conversation, Cortex Issue or scheduled Task to confirm the work actually reached the CoAgent.
- If access failed, check permissions for the CoAgent's own identity on the named resource. Your access does not transfer to it.
Add the CoAgent commands to the Socra CLI once if they are not listed in socra --help:
socra install agent
From an authorized CLI session, these commands read saved state without waking the computer. Replace AGENT with its username or ID:
socra agent get AGENT
socra agent activity AGENT
socra agent message list AGENT --status queued
Mailbox queued means waiting for delivery; delivered means handed to the runtime without an acknowledgement yet. An acknowledged event has an outcome, which may be succeeded, failed or canceled. A successful event does not automatically close an Issue, publish a change, or send a reply.
If a billing problem with the Socra HQ subscription prevents the computer from starting, read the error and ask an Account owner to check Billing. Changing Socra billing does not fix a provider usage limit or a missing resource permission.
Before retrying interrupted work, inspect its actual effects: a commit, deployment, file change or sent message may already exist. Do not assume that no action happened merely because the final response is missing.
Wake computer can start compute and incur running usage. The behavior of socra agent connection check AGENT depends on the CoAgent's connection:
- With a shared ChatGPT or Claude connection, it returns saved state without waking the computer.
- For a Codex CoAgent using a local ChatGPT sign-in, it runs a live connection check and can start the computer and incur running usage. Use this check only when you intend to start the computer.
Neither result proves a new task will succeed or that a fresh provider sign-in has completed. See CoAgent troubleshooting.