Agents · Cursor

What Cursor leaves on your Mac.

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.

What it looks at

Every folder has its own rule.

Devbroom handles every place the way Cursor itself behaves. What the agent cleans itself it leaves to the agent; what has its own command it leaves to that command.

Cursor's file format hasn't been verified on a real install yet. So today Devbroom only reads and shows Cursor's data; none of it counts as ready to clean.
AssessedOnce the format is verified, each item will be checked on its own. For now it's only read.
Through Cursor itselfShould only be cleaned with Cursor's own commands.
Cursor managesThe agent cleans up itself; Devbroom only shows them.

Agent transcripts

Agent transcripts left behind when chats are deleted in the interface.

~/.cursor/projects
Read only for now

Cache and logs

A separate cache folder for every version, never pruned; the newest two should stay. Logs are only logs.

~/Library/Application Support/Cursor/CachedData~/Library/Application Support/Cursor/logs
Read only for now

Chat and agent database

Should be cleaned with “Developer: Delete Old Chats” or “Developer: GC Agent KV Blobs” in Cursor; never edited while Cursor is open.

~/Library/Application Support/Cursor/User/globalStorage/state.vscdb
Through Cursor itself

CLI chats

Kept only on this Mac, with no backup; should be deleted from the CLI.

~/.cursor/chats
Through Cursor itself

Cursor worktrees

Cursor keeps 25 on this Mac and may also delete other worktrees in this folder.

~/.cursor/worktrees
Cursor manages

CLI versions

The updater prunes unused versions.

~/.local/share/cursor-agent/versions
The updater manages
Protected

Your account and settings stay untouched.

These files and folders are protected. No verdict ever opens them to cleaning; they stay where they are whatever their size.

Cursor database (holds session keys)state.vscdb · -wal · -shm
MCP settings~/.cursor/mcp.json
CLI settings~/.cursor/cli-config.json
Hooks~/.cursor/hooks.json
Worktrees

Recognizes Cursor's worktrees by their traces.

It tells a worktree belongs to Cursor from these traces. Since Cursor's data is only read, these worktrees don't count as ready to clean for now.

  • LikelyInside the ~/.cursor/worktrees folder
  • PossibleA branch name starting with cursor/
  • Read only for now. Until Cursor's format is verified these worktrees don't count as ready to clean.
Compatibility

Checks Cursor's files first.

Before trusting an agent's data, Devbroom checks that its files are in the expected format. If they aren't, that data is only read; none of it counts as ready to clean.

Tested versionsnone yet

A version outside this range still works if the format holds, and shows as “not tested yet”.

Format checknot verified yet

Cursor's files haven't been verified on a real install yet, so its data is only read.

Your versiondevbroom compat

If its folders live elsewhere, it follows CURSOR_CONFIG_DIR.

Let Cursor work. Devbroom cleans up after it.