Managing an agent
Pause, resume, redeploy, and delete your agents, and read what their status means.
Everything here happens from the agent's page in the dashboard. Open an agent and you will find its status, its web address, and the actions below.
The four actions
Suspend
Stops the agent from running. Its files and memory are kept, so you can bring it back later. Use this when you want to stop the work (and the spend) for a while.
Resume
Starts a suspended agent again, right where it left off.
Redeploy
Applies changes — a new model, new keys, a new channel — and restarts the agent with them.
Delete
Removes the agent for good, along with its files and memory. This cannot be undone.
Delete is permanent. If you might want the agent later, suspend it instead — suspending keeps everything.
What the status means
| Status | What is happening |
|---|---|
| Provisioning | The agent is being set up. Give it a minute. |
| Ready | The agent is live and healthy. Open its web address to use it. |
| Suspended | You paused it. Its files are safe; resume to start it again. |
| Failed | Something went wrong on startup. The dashboard shows a message with the reason. |
Right after an agent becomes Ready, its web page may briefly show a 503 while the last piece comes online. Wait a few seconds and refresh.
When an agent fails
A Failed status usually means the agent could not start. Common causes:
- A missing or wrong API key. Check your secrets and, for BYOK, that the provider key is valid.
- The wrong model or provider for that runtime. See Model access.
Fix the cause, then Redeploy. Sokko retries failures automatically a few times before it gives up and waits for you.
Doing this from the terminal
You can list your agents and their status from the sokko CLI:
sokko instances ls