Skip to main content
An agent is a running container, and sometimes you need to do something with it: restart it, see where it got stuck, or take a copy before a risky task. All of this lives in three settings sections: Log, Terminal, and Management.

​
Log

Settings → Log is the agent’s technical diary: what it did and where it got stuck.
Log section: a live console with technical lines and an auto-refresh toggle
You don’t need to read it in full, and it wouldn’t help. Come here in two cases: the agent is silent and you want to know why, or support asks you to share the log lines. The Auto toggle keeps the console live, and there’s a manual refresh button next to it.
When you contact support, attach the last log lines from the time things broke. It speeds up troubleshooting many times over.

​
Management

Settings → Management covers everything you do with the container as a whole.
Management section: the Status block showing Running and the Agent Panel block with a password

​
Diagnostics

This is the first thing to click when the agent behaves strangely. Check only inspects; Check and Fix repairs what it finds, and the agent may restart in the process.

​
Backup

The Download Backup button gives you the archive. Make one before any major change: deleting skills, rewriting the personality, or giving the agent access to live data.
Diagnostics, Backup, and Danger Zone blocks with a press-and-hold delete button

​
Deletion

The Danger Zone button works on press-and-hold, not a click, so you can’t trigger it by accident. The agent and all its data are deleted permanently: files, memory, conversations.
Deleting an agent is the only way to free up a slot if your account already has two deployed agents. Download a backup first: the platform can’t restore a deleted agent.

​
Terminal

Settings → Terminal is a command line inside the agent’s container.
Terminal section: Connected status and a real shell prompt
This section is for people who know what they’re doing: you can break settings here. If you do, run Diagnostics → Check and Fix. You don’t need the terminal for everyday work: the agent will do anything you need in the container if you ask in chat.

​
If the agent breaks

1

Check the status

Look for the green dot next to the agent’s name at the top of the workspace. No dot means the container isn’t running.
2

Restart

Management → Restart. It takes half a minute and clears most hang-ups.
3

Run diagnostics

Check and Fix finds problems with the model key, a channel, or a stuck lock on its own.
4

Check the log

If that didn’t help, the last log lines show where it’s stumbling.
5

Contact support

Include the log lines and a description of what you did before it broke: Support.

​
FAQ

None of the files or memory: they’re on the container’s disk. Only current conversations, scheduled tasks, and connected channels are interrupted, for about a minute.
A stopped agent does nothing: no scheduled tasks, no replies. Spending comes from model work, and there’s no work.
To open the agent panel outside the workspace, for example in another browser. You don’t need it inside the workspace. The buttons next to the field show and copy the password.
There’s no backup upload button in the interface: you keep the archive, and restoring is handled with support. That makes a backup insurance, not a full time machine.
Check the log to see whether the task ran at all. After a migration or long downtime, background tasks may fail to start, and the agent won’t tell you. See Where the Agent Fails.

​
What’s next

Where the Agent Fails

Common failures and how to catch them

Security and Access

Minimal permissions and a backup before risk

Models

Fallback models keep the agent from going silent

Support

When you’ve tried everything