Plans and questions
Two things stop Claude and wait for you: a question and a plan. Both arrive as cards pinned to the bottom of the transcript, like a permission request, and both block until you answer.
Questions
When Claude needs to choose between approaches and cannot tell which you want, it asks — with options, and a short explanation of each.
The card lets you pick an option, add a note explaining your choice, or write something else entirely. Some questions allow several answers at once; the card says which.
Declining a question is not denying it. Claude is told you chose not to answer and carries on with its own judgement.
Once answered, the card becomes a row in the transcript showing the question and what you said, so the decision stays visible when you scroll back.
Plan mode
In plan mode Claude researches and writes a plan, and runs no tools that change anything. You get to read the plan before any of it happens.
Set it from the mode chip beside the message box, or let Claude enter it itself when a task warrants it.
Reviewing a plan
When Claude presents a plan, the card offers:
- Approve — go ahead and do it.
- Approve, and accept edits — go ahead, and stop asking about each file change.
- Edit the plan first — change the text, then approve what you edited. Claude works from your version.
- Send back — keep planning, with feedback on what to change.
- Stop — end the turn.
The plan is Markdown and is shown as such. Editing it edits the real thing: what you approve is what Claude is given.
Afterwards the plan stays in the transcript, collapsed, recording how it was answered — approved, approved as you edited it, or sent back.
Why these block
A question or a plan that scrolled away would be worse than useless: Claude would sit waiting while you read on, wondering why nothing was happening. Both stay pinned at the tail until answered, for the same reason permission cards do.