[docs]
Permissions and questions
When Claude Code asks to run a tool or asks you to choose, a card in the corner of your screen shows exactly what it wants. Answer it there, without finding the terminal.
Read the card
The card says Claude Code needs permission, with the project, the branch and the session’s title, then what it wants, like Wants to run and the command. Ember shows its “!” until you answer.
Allow or deny
Select Allow to let it run this once, or Deny to refuse and tell Claude Code you said no. Open brings the session’s terminal or editor to the front instead.
The terminal keeps showing its own prompt. Whichever you answer first wins, and the other one goes away.
When Claude Code asks you to choose, the card reads Claude Code has a question, or a number of questions. Each question is a step: pick an option, tick several, or type your own answer, then select next and finally submit. The terminal offers its own picker at the same time.
A waiting session is also on top of the sessions tab, under [needs you]. Open it to see the same ask with [allow] and [deny], or the question’s form.
When Burnstate starts, it adds a hook to Claude Code’s settings file, ~/.claude/settings.json, and to the settings in any other Claude Code config folder you use. The hook sends each prompt to Burnstate on your Mac and nowhere else. Burnstate removes the hook when it quits, and if Burnstate isn’t running, Claude Code works exactly as before.