> ## Documentation Index
> Fetch the complete documentation index at: https://aitextura.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Agent Maintenance
> Log, terminal, and container management: restart, diagnostics, agent panel password, backup, and deletion.
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.
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](/en/guides/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.
| Block | What it does |
| --------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Status** | Container status plus **Restart** and **Stop** buttons |
| **Agent Panel** | Password for the agent's own panel. You don't need it in the workspace, only if you open the panel in another browser |
| **Diagnostics** | Checks the container, the model key, channels, and stuck locks |
| **Backup** | An archive of the agent's full state: settings, personality, memory, conversations |
| **Danger Zone** | Deletes the agent |
### 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.
### 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.
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
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.
**Management → Restart**. It takes half a minute and clears most hang-ups.
**Check and Fix** finds problems with the model key, a channel, or a stuck lock on its own.
If that didn't help, the last log lines show where it's stumbling.
Include the log lines and a description of what you did before it broke: [Support](/en/guides/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](/en/guides/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](/en/agents/limits).
## What's next
Common failures and how to catch them
Minimal permissions and a backup before risk
Fallback models keep the agent from going silent
When you've tried everything