Turret Download

All help topics

How-to · Tools and permissions

Answer a permission request

Decide what happens when a session stops mid-turn to ask before it runs something.

A session has stopped to ask before it runs something. The ask sits as a card at the foot of the transcript rather than a popup.

  1. Read the card's first line, naming the tool, and the arguments below it.
  2. Type a reason in the field under the arguments, or leave it blank. Denying sends it to the session; allowing discards it.
  3. Press Deny and stop to refuse the call and interrupt the session's turn.
  4. Press Deny to refuse the call and let the session try something else.
  5. Press Allow once to let the call through and nothing else.

Pressing Escape denies the request, as long as the card still holds focus.

A card that can become a standing rule shows a box above the buttons, naming the rule it would store and where. Its Allow always control stores that rule and allows the call in the same action. The three buttons above still answer only this ask. A card that cannot become a rule explains why in that box instead.

A question from AskUserQuestion looks different: no allow or deny, only the options Claude offers. Choose from the options offered, or type an answer in the field under them, then press Send.

Press Skip to tell the session nobody answered. It carries on with its own judgement.

A Codex session can ask questions too, in a card headed Codex is asking. Each question has a box of its own under its options for a note. A question with no options is answered in its box. A box for a secret hides what you type, and Turret does not show it again once sent.

Send needs a pick or a note on any question; leave the rest blank. Escape skips from an option or a button, never from a box, so a stray key does not lose what you typed. Once settled, the question stays in the transcript as a row saying whether it was answered, skipped or not answered.

See Permission rule syntax for what pressing Allow always stores.