Skip to content
OpenComputer

Approvals, questions and plans

When the harness needs a decision, the runner posts a prompt in the thread and the turn waits; prompts never expire

Permission requests

A permission request appears when the session’s permission mode does not let a tool call through. In the default mode, bypassPermissions, none appear.

The prompt names the tool and shows the command for Bash or the diff for an edit (up to 2,500 characters), or the content for a new file (up to 1,500).

A permission request in a thread: Claude wants to use Bash, the command, and the buttons Allow, Allow Bash for this session and Deny
AnswerEffect
AllowThis call runs.
Allow <tool> for this sessionThis call runs, and the harness stops asking for the same kind of call in this session. Shown only when the harness offers it.
DenyThe call is refused and the agent is told.
Typed replyDeclines the request; the agent gets your text as what to do instead.

Once answered, the prompt message is deleted and the step card shows the outcome and who gave it.

Questions

A question prompt with two questions, each with a button per option, and the line: or reply here with your own answer
AnswerEffect
Option buttonAnswers that question.
Typed replyAn answer that is not among the options.
Typed reply, more than one question still openCloses the whole prompt: the agent gets your text with the answers already given by button.

Plans

In plan mode the agent presents its plan as a message titled “Plan ready for review”.

A plan titled Plan ready for review with the buttons Approve · auto-accept edits, Approve · ask before edits and Keep planning
AnswerEffect
Approve · auto-accept editsThe plan is approved and the session’s mode becomes acceptEdits.
Approve · ask before editsThe plan is approved; edits ask for approval. The footer and !status still show plan.
Keep planningThe plan is rejected and the agent continues planning.
Typed replyDeclines the plan; the agent gets your text as the change you want.

The plan message stays, updated with the outcome and who decided.

The same plan after approval: the buttons are gone and a line reads plan approved · auto-accepting edits · Dana

All prompts

RuleDetail
Who can answerAnyone whose messages are delivered to the session. See Shared threads.
First answer winsLater clicks do nothing.
Typed messagesWhile a prompt is open, a delivered message answers or declines the latest open prompt; it starts no new turn.
ExpiryNone. The idle exit does not end a turn waiting on a prompt.
Stop!stop or Slack’s stop button closes the open prompts and stops the turn.
Runner restartThe buttons of an open prompt do nothing, and nothing in the thread says so. Send the request again.
APIThe same prompts; an answer from either side closes the prompt for both. See Asks.