Answer prompts from the board
When Claude Code stops to ask you something, the board shows the ask. You can answer it on the board or in the terminal. This works for every session the board sees, including sessions you started outside Claude Code Kanban.
The board handles three kinds of ask:
- A permission ask, such as a request to run a command.
- A question from the
AskUserQuestiontool. - A plan that waits for approval (
ExitPlanMode).
This feature needs the Claude Code Kanban plugin. See Getting started to install them.
What you see
Section titled “What you see”A session that waits for you gets an amber highlight in the sidebar. The “N waiting” chip at the top of the sidebar counts these sessions. Click it to list only them. The ask shows in three places:
- The last entry of the session log. It shows the tool name and a key hint, such as Ctrl+Enter allow. The sidebar already marks the session as waiting, so the entry has no pill.
- A badge in the agent footer under the board. Click it to open the ask.
- The detail modal, which opens when you click the log entry or the badge.
For a permission ask, the title of the detail modal names the tool. The modal shows a card with the full command, or the diff of an edit, the folder it runs in and how long Claude has waited. The full tool input is in a collapsible “Raw tool input” section. A plan shows in full Markdown.
Answer an ask
Section titled “Answer an ask”The buttons depend on the kind of ask:
- Permission ask. Click Allow or Deny. The buttons are on the log entry and in the detail modal.
- Plan. Click Approve or Reject. You can type feedback before you reject, on the log entry or in the detail modal. Claude Code gets the feedback as the reason.
- Question. Open the detail modal. With more than one question, each question has a tab, and a Review tab lists your answers. Pick an option for each question, or type text in “Or type your own answer”. Questions that allow more than one choice let you pick several options. You can send before you answer all questions. The button then reads Answer (n/m), where n is the number of questions you answered.
Keys in the detail modal:
- Ctrl+Enter allows a permission ask, approves a plan, or sends the answers to a question.
- 1 to 9 pick an option of the question on screen.
- ← and → move between the question tabs.
On macOS, use Cmd+Enter. The same Ctrl+Enter allows the ask from the log entry when no window is open.
The x on the log entry removes the ask from the board. It does not answer the ask. Claude Code still waits for your answer in the terminal.
The terminal stays live
Section titled “The terminal stays live”The prompt in the terminal stays open while the board waits. The first answer wins. If you answer in the terminal first, the ask leaves the board within about a second. If you then click a button on an old card, the board drops the card, and Claude Code gets no answer from the board.
If you allow an ask on the board, the tool runs while the terminal prompt is still on screen, and the status line shows “Approved from the board — running”. Do not answer the terminal prompt then. If you choose “Yes” there before the tool finishes, the tool runs twice.
When the buttons do not show
Section titled “When the buttons do not show”The board shows buttons only when it can answer the ask. That is true when the plugin’s mod sent the ask and still waits for a decision. In other cases the entry says “answer in the terminal”. This happens when:
- The mod stopped waiting after
waitSeconds. - You turned UI approvals off.
- The ask is a question and
modeis"permission".
The board hides an ask 30 minutes after it starts.
In auto mode, the board does not show permission asks, because the auto-mode classifier answers most of them. Asks from an ask rule in your settings, questions and plans still show. The board reads the mode from the session transcript, so a mode change with Shift+Tab applies after the next tool call.
Auto-open
Section titled “Auto-open”When a new ask that the board can answer arrives in the selected session, the detail modal opens by itself. Each ask opens one time. If you close the modal, it does not open again for the same ask. The modal does not open when another modal is open, or when the embedded terminal is on screen, because the terminal already shows the ask.
Configure
Section titled “Configure”UI approvals are on by default. Each Claude config dir has its own settings, in the approvals section of <config-dir>/.cck/config.json. <config-dir> is CLAUDE_CONFIG_DIR, or ~/.claude when that is not set. Create the file only if you want to change the defaults.
To turn UI approvals off:
{ "approvals": { "enabled": false }}Set mode to "permission" to leave questions to the terminal. waitSeconds sets how long the plugin waits for a board decision, up to 1800 (30 minutes). For all fields and defaults, see UI approvals config.
With UI approvals off, the board still shows each ask and its amber highlight. You answer it in the terminal.
When the board cannot answer
Section titled “When the board cannot answer”The terminal prompt stays open while the plugin waits for the board, so a problem with the board never blocks a session. You answer in the terminal when:
- The Claude Code Kanban server is not running.
- UI approvals are off, or the ask is a question in
"permission"mode. - No one answered on the board within
waitSeconds.
If the server restarts while an ask waits, the plugin keeps waiting, and the board can answer once it is back.
See Configuration for other settings and Keyboard shortcuts for all keys.