Agents

Devbroom knows five agents and looks at each one's folders the way that agent behaves: what the agent cleans itself it leaves to the agent, what has its own command it leaves to that command, and it never touches your account or your settings.

Beyond these it also finds and shows the data of Gemini CLI, Aider, Cline, Windsurf, Copilot CLI, Amp, Kiro; nothing of theirs is cleaned for now.

Claude Code

Session logs, checkpoints, scratch workspaces, worktrees. Devbroom finds them all, and tells you which ones Claude Code deletes itself, which are left to you and which are never touched.

Location	What	Devbroom
`/private/tmp/claude-<uid>`	Scratch workspaces	Assessed
`~/Library/Caches/claude-cli-nodejs`	MCP and error logs	Assessed
`~/.claude/projects`	Session logs	With claude purge
`~/.claude/file-history`	Checkpoints	Claude Code deletes
`~/.claude/debug` `~/.claude/shell-snapshots` `~/.claude/paste-cache` `~/.claude/image-cache`	Logs and caches	Claude Code deletes
`~/.local/share/claude/versions`	CLI versions	The updater manages
`~/.claude/plugins/cache` `~/.claude/plugins/marketplaces`	Plugins	Never touched
`~/Library/Application Support/Claude`	Desktop app data	Never touched

Protected: ~/.claude.json, ~/.claude/.credentials.json, settings.json · settings.local.json, ~/.claude/history.jsonl, ~/.claude/agent-memory, ~/.claude/plugins. No verdict ever opens these to cleaning.

Tested versions: 2.1.0 - 2.1.292. Format check: The logs in ~/.claude/projects must carry these two fields, which tie a session to a folder. If its folders live elsewhere, it follows CLAUDE_CONFIG_DIR, CLAUDE_CODE_TMPDIR.

Claude Code page

Codex

Sessions, archived sessions, temporary git repositories, caches and Codex worktrees. Devbroom finds them all, and tells you which ones Codex manages itself, which are left to you and which are never touched.

Location	What	Devbroom
`~/.codex/.tmp`	Temporary git repositories	Assessed
`~/.codex/cache` `~/.codex/log` `~/Library/Logs/com.openai.codex`	Cache and logs	Assessed
`~/.codex/sessions` `~/.codex/archived_sessions`	Sessions	With codex delete
`~/.codex/worktrees`	Codex worktrees	Codex manages
`~/.codex/shell_snapshots`	Shell snapshots	Codex deletes
`~/.codex/plugins/cache`	Plugins	Never touched
`~/Library/Application Support/Codex` `~/.codex/*.sqlite`	Desktop app data	Never touched

Protected: ~/.codex/auth.json, ~/.codex/config.toml, ~/.codex/history.jsonl, ~/.codex/sqlite. No verdict ever opens these to cleaning.

Tested versions: 0.115.0 - 0.159.2. Format check: The log files in ~/.codex/sessions must start with a metadata line that carries the session's folder. If its folders live elsewhere, it follows CODEX_HOME.

Codex page

Cursor

Agent worktrees, transcripts, chats and caches. Devbroom finds and shows them; since Cursor's file format isn't verified yet, it cleans none of them for now.

Cursor's file format isn't verified yet: its data is only read, and none of it counts as ready to clean.

Location	What	Devbroom
`~/.cursor/projects`	Agent transcripts	Read only for now
`~/Library/Application Support/Cursor/CachedData` `~/Library/Application Support/Cursor/logs`	Cache and logs	Read only for now
`~/Library/Application Support/Cursor/User/globalStorage/state.vscdb`	Chat and agent database	Through Cursor itself
`~/.cursor/chats`	CLI chats	Through Cursor itself
`~/.cursor/worktrees`	Cursor worktrees	Cursor manages
`~/.local/share/cursor-agent/versions`	CLI versions	The updater manages

Protected: state.vscdb · -wal · -shm, ~/.cursor/mcp.json, ~/.cursor/cli-config.json, ~/.cursor/hooks.json. No verdict ever opens these to cleaning.

Tested versions: none yet. Format check: Cursor's files haven't been verified on a real install yet, so its data is only read. If its folders live elsewhere, it follows CURSOR_CONFIG_DIR.

Cursor page

OpenCode

Session database, undo snapshots, old session files, logs and worktrees. Devbroom only reads the database and checks its format on every scan; if the format doesn't hold, none of OpenCode's data counts as ready to clean.

Location	What	Devbroom
`~/.local/share/opencode/snapshot`	Undo snapshots	Assessed
`~/.local/share/opencode/storage`	Session files from before 1.2	Assessed
`~/.local/share/opencode/log` `~/.cache/opencode`	Logs and cache	Assessed
`~/.local/share/opencode/opencode.db`	Session database	Through OpenCode itself
`~/.local/share/opencode/worktree`	OpenCode worktrees	Through OpenCode itself
`~/.local/share/opencode/tool-output`	Tool output	OpenCode deletes

Protected: opencode.db · -wal · -shm, auth.json, mcp-auth.json. No verdict ever opens these to cleaning.

Tested versions: none yet. Format check: opencode.db must open read only and its session table must have these two columns. If its folders live elsewhere, it follows XDG_DATA_HOME, XDG_CACHE_HOME, OPENCODE_DB.

OpenCode page

Orca

Orca's workspaces are git worktrees. Devbroom assesses each one on its own with git itself, and shows the ones Orca already removed and half-finished setups separately.

Location	What	Devbroom
`~/orca/workspaces`	Workspaces	Assessed
`<repo>/.orca-worktree-trash`	Removed workspaces	Assessed
`~/orca/workspaces/.orca-preparing`	Workspaces being set up	Assessed

Tested versions: 1.4.0 - 1.4.221. Format check: Only git worktrees are used, read with git itself; nothing relies on a file format of Orca's own.

Orca page

Other tools

Worktrees in any tool's ~/.<tool>/worktrees or ~/.<tool>/workspaces folder are shown with that tool's name as their likely owner. When it isn't clear which agent left something, the verdict is Unknown.

PreviousIntegrations

Last updated: October 7, 2026