Answering an agent's question
When an agent can’t continue without something from you — a decision it isn’t allowed to make, a missing detail, anything it needs to keep going — it stops and moves to Stuck. This parks the whole agent: every card it holds waits, not just the one it was working when it asked.
Where to answer
Open the agent from its card in the Stuck column. Select the card that raised the question and read it in the conversation on the agent’s page.
If the question offers choices, select one and press Send answer. Questions that allow more than one choice let you select several before sending. Selecting a choice alone doesn’t send it.
You can also choose Write my own answer, type a reply and press Send answer or Enter. Shift+Enter adds a line. A question without choices opens the text field directly.
Skip question sends a request to continue with a provisional default where possible. The agent must state that assumption in its progress and summary. Skipping doesn’t supply an essential input, such as a credential or a decision the agent cannot make; it may still need to stop and explain that dependency.
What happens after
Your choice, typed reply or skip is queued as the agent’s next prompt. The page moves from Stuck to Working immediately when you send it; that records your intent, not a measurement that the CLI has started. The queued message shows its delivery state while it waits for the machine to pick it up.
Answering also lifts the agent’s pause or hold, but the machine may still be offline or waiting on its CLI’s account limit. Read the waiting reason beside the message. If sending fails or is refused, the question becomes answerable again with your reply or selection retained.
An agent asks one question at a time. If you don’t answer or skip, it remains in Stuck until you answer or stop it.
See Columns and what they mean for how Stuck fits with the rest of the Board.