Docs
Agents and maintenance

Approvals and staying in control

Respond to questions, review approvals and stop a run

The conversation shows when the agent needs information or an action requires your review. Questions, approvals and the Stop control serve different purposes.

Answer a question

A request for input explains the decision and can offer choices or a written answer. Supply the missing information in the displayed control. If the agent is waiting on that answer, it can continue after your response is accepted.

Clear requirements reduce avoidable questions. State the desired outcome, relevant accounts and any constraints early.

Review an approval

An approval is permission for the action described in its card. Read the target, scope and effect before accepting. Approval for one action does not silently authorize unrelated actions or a different environment.

Connected services, chat access and the current execution mode also constrain what tools can do. A prompt alone cannot grant access to someone else's project or connection.

Stop work

Use Stop to interrupt a running request. Stopping does not undo files already written or external actions already completed. Review the resulting state and ask for a specific correction or recovery if needed.

Standing goals have their own status and pause/clear controls. Check those controls when managing background work; closing the conversation is not the same as pausing a goal.

See Agents, shared codebases and MCP scope.