Levo help · Memory, CPU and agents
Agent sessions: what they are and when they can go
Agents like Claude Code and Codex keep a record of every session. Over weeks it adds up to gigabytes. Levo lists them as Agent and editor history.
What's a session
For Claude Code, a session is a transcript plus its folder of subagent and tool output. For Codex, a session is a rollout file. Levo shows one row per project folder, which stands for the sessions inside it. Open the row to tick sessions one by one.
When one can go
| Careful | Balanced | Aggressive | |
|---|---|---|---|
| A whole Claude Code session | idle 7 days | idle 2 days | idle 3 hours |
| Only its subagents and tool output | idle 3 days | idle 1 day | idle 3 hours |
| A Codex rollout | idle 7 days | idle 2 days | idle 3 hours |
Removing only subagents and tool output is the gentle option: you can still resume the conversation. A session whose working folder is gone, such as a removed worktree, goes one level earlier, because nobody can resume it where it ran. Once your agent has judged a project's sessions, its own idle times apply instead.
What's never removed
- A session that's running right now.
- The agent's memory.
- Any file that's open.
- Anything changed in the last five minutes.
- Anything in the folder that isn't a transcript or its sidecars.
The cleaner checks each part again right before removing it.
Why bother
Old sessions are rarely resumed, they hold large tool output, and they sit in your home folder where nothing else prunes them. Worktrees and temp folders agents leave behind are listed alongside them.