Skip to main content
Barrier

Documentation

Trace and disk cleanup

What account cleanup, trace cleanup and disk cleanup remove, and what they keep.

Every cleanup starts with a plan you review. Nothing outside that plan is touched.

Account cleanup

Removes what Claude and Claude Code leave on the computer, including:

  • running Claude Code processes
  • proxy leftovers, proxy environment variables and shell profile lines
  • the DNS cache and related hosts entries
  • Claude-only keychain (macOS) and Credential Manager (Windows) entries
  • site data
  • .claude/statsig and .claude/ide lock files
  • editor extension state for VS Code, VS Code Insiders, Cursor, Windsurf and VSCodium, including their remote servers
  • crash reports (DiagnosticReports, CrashDumps, Crashpad, Sentry)
  • macOS HTTPStorages and cookie files, and npm logs that mention Claude Code

Regular cleanup keeps sign-in credentials and work history by default. You can select either option. When this device is marked for verification after an account restriction, both options are selected and locked. Review the list and confirm once to run cleanup.

After cleanup each item is checked again on the new Static Residential IP.

Trace cleanup

Moves old proxy logs, IP lookups in shell history and terminal contents into a quarantine you can restore.

Disk cleanup

Scans the disk with built-in rules and deletes only what the reviewed plan lists.

Browser cookies are cleaned through a paired browser extension rather than by editing the browser’s files. Cleanup needs a signed-in, approved account.