Levo help · Memory, CPU and agents

Coding agents leave a mess: worktrees, sessions and temp folders

Coding agents work in copies of your project. Each task can make a git worktree or a temp folder with its own node_modules or build, and nothing removes them when the task ends. A few weeks of agent work can take tens of gigabytes.

What Levo looks for

• Agent worktrees: from Claude Code, Codex, Cursor, Conductor and T3 Code.
• Temporary folders an agent made to test something.
• Agent and editor history: session logs from Claude Code, Codex, opencode, aider, Copilot and Gemini CLI, and VS Code workspace data.
• Tool caches of the agents and editors themselves.
• Old editor extensions.

Worktrees and git

A worktree with unfinished work is never removed. If it has uncommitted changes, commits that aren’t merged, or a lock, Levo leaves it and says why. A clean, merged worktree is removed with git worktree remove, so git’s own records stay tidy.

Live sessions

Levo knows which sessions are alive. It reads the activity of Claude Code, Codex, Cursor, Conductor and T3 Code, and a worktree a live session is working in is locked until the session ends. So are folders touched in the last few minutes. See Agent sessions.

Session logs

Session history and an agent’s memory are yours, not cache. They’re listed with their sizes, and Levo leaves them for you to tick. An agent’s own memory is never cleaned.

A good routine

1. Analyse, then open Agent worktrees.
2. Rows are ticked when their branch is merged and nobody is in them.
3. Clean up. Anything with unmerged work stays, and the row says so.