Skip to content

cockpit 0.4.0: context and rate-limit alerts, protected folders, burn rate

Latest

Choose a tag to compare

@izzatum izzatum released this 09 Oct 13:48
f25e297

cockpit 0.4.0 adds context and rate-limit alerts, your own protected folders, a burn rate on the dashboard, and CI.

Install or update

/plugin install cockpit --marketplace izzatum/claude-code-cockpit

Already installed: claude plugin update cockpit@claude-code-cockpit, then /reload-plugins.

New

  • Context alert (contextAlert, default 80%): one pop-up when the context window reaches the line, suggesting /compact. It fires again once context drops back under and climbs past it.
  • Rate-limit alert (rateAlert, default 90%): one pop-up per rate-limit window, such as the 5-hour limit, with the time it resets. /clear does not repeat it for the same window.
  • Reset times and burn rate on the /cockpit dashboard: each rate limit shows the time left until it resets, and after 5 minutes the cost shows $/h and about how long until your budget alert. The countdowns update every minute while the pane is open.
  • Protected folders (guardPaths): extra folders, split by ;, where recursive deletes are blocked, such as ~/work; /Volumes/NAS. A folder counts when Claude works inside it or a command names it: quoted or not, with escaped spaces, through ~, $HOME, ${HOME} or the full home path, and in Windows or Git Bash form.
  • desktopSync: treat ~/Desktop and ~/Documents as synced folders, for iCloud Drive "Desktop & Documents Folders" or OneDrive folder backup.

Fixed

  • The guard now catches a recursive delete split over lines with a trailing \ (for example find x \ then -delete on the next line). A \ at the end of a comment still joins nothing.
  • Sync-app names in code and prose (new Dropbox(, -t Dropbox,OneDrive) are no longer read as folders.
  • Three guard patterns that could take seconds on long, crafted commands now run in linear time.
  • The blocked-command count and the context alert start over on /clear.

Also

  • GitHub Actions CI runs claude plugin validate and claude plugin test on every push and pull request.
  • The cloud-sync guard is still a safety net, not a sandbox: see Limits and caveats.

Tested on Claude Code 2.1.295. Full docs: README.