Shortcuts and privacy

Keyboard shortcuts, what Burnstate sends where, and how to remove it cleanly.

Keyboard shortcuts

These work while the panel is open.

[keys]	[action]
`⌘1`	Providers tab
`⌘2`	Sessions tab
`⌘F`	Filter providers
`⌘N`	Add provider
`⌘I`	Insights
`⌘B`	Burn report
`⌘T`	Take a break
`⌘,`	Settings
`esc`	Back, or close the panel
`⌘E`	Archive the open session
`⌘⌫`	Move the open session’s transcript to the Trash
`⌘Z`	Undo archive or trash
`⌘Q`	Quit Burnstate

Burnstate has no account, no analytics and no server of its own. What it does send goes straight to where it’s needed:

Usage requests go to each connected provider’s own service (Claude Code, Codex, Cursor, Vercel, Setapp AI), with that provider’s login.
Insights and summaries go to Setapp AI, only when you ask for one or turn on automatic summaries.
Update checks ask the npm registry, or Homebrew for a CLI you installed with it, for the newest version of the CLIs you have installed.
Release notes come from GitHub, only when you ask “what’s new in my ai tools?” in Insights.
Setapp is told when you open the panel, which is how Setapp counts that you use the app. Nothing about your usage goes with it.
Burn reports aren’t sent anywhere. The numbers live in the link you share.

Tokens and cost come from the logs your tools already keep on your Mac. The Privacy Policy has the details.

Logins and keys you add in Burnstate: your Keychain, in items whose name starts with dev.burnstate.
Settings, your report handle, archived sessions and Cooldown’s record of today at the keyboard: Burnstate’s preferences on this Mac.
The permission hook: one entry in ~/.claude/settings.json while Burnstate runs.

Quit it
Select quit in the panel or press ⌘Q. This removes the permission hook from Claude Code.
Uninstall it
In Setapp, find Burnstate and choose Uninstall.
Clear its logins, if you like
Disconnect providers before you uninstall, or open Keychain Access afterwards and delete the items that start with dev.burnstate.

To see the welcome tour again, you don’t need to reinstall: write to us and we’ll tell you how.

Something not working, or not covered here? Write to the address below. Release notes for every version are in the changelog.