Pimp My IDE / Garage dispatch
Back to garage
September 28, 2026 | agent interaction / control flow

A status question should not pull the handbrake.

Agent chat boxes accept questions, corrections, approvals, and stop commands through one slot. The runner must classify the message before it changes the task.

Work the interruption clutchRead the sources

One text box carries different kinds of authority.

"What are you doing?" asks for a report. "Use the smaller parser" changes the plan. "Approve this command" grants narrow authority. "Stop now" ends the run. They may look identical in a transcript, but a runner should not apply them the same way.

Codex 0.158 fixes one concrete version of this mistake. Its release notes say an approval review now retries when new user input arrives, so a status question does not cancel the pending action. The same release enables terminal-input approval by default for commands that run with elevated permissions.[1]

Conversation is the transport. It is not the control model.

A progress report is not a completion receipt.

Anthropic's Opus 5.5 prompting guide documents a related boundary. A long task can emit a text-only progress update with an end-of-turn reason. An unattended loop that equates that event with task completion can stop while checklist items remain open. Anthropic recommends checking explicit task state, limiting automatic continuations, and keeping confirmation for risky or irreversible actions.[2]

The same guide says progress updates may arrive in a distinct thinking-block form. A client that renders only ordinary text blocks can look silent. That is a display bug with operational consequences. The user cannot tell whether the agent is working, blocked, or done.

The editor is becoming a traffic controller.

VS Code 1.139 makes session rows expand when a session needs input or approval. It also summarizes progress from hidden chats on the parent row.[3] Zed 1.21 adds a setting that keeps the system awake while agent threads run.[4]

Those features improve visibility and continuity. They do not define what a new message means. The runner still needs a durable task state, a named pending action, and an explicit rule for each input type.

Wire four routes.

  1. A status query returns a report and preserves the pending action.
  2. A correction updates the plan, invalidates affected work, and resumes from a named checkpoint.
  3. An approval answer applies only to the action and environment shown to the operator.
  4. A stop command cancels active work, records what ended, and leaves recovery instructions.

Do not infer these routes from tone. Give the interface visible controls or parse the message into a typed event that the user can inspect before it changes execution.

Interactive makeover / control routing

Operator interruption clutch

Traditional purpose replaced: one chat box where every new message can disturb the run. Better version: choose the message type, close the state-preservation interlocks, and copy a routing contract.

Select the operator event

The native radio owns the state. The carriage mirrors that value and does not replace it.

Incoming message type
Status route selected. One interlock remains open.The pending action stays visible while the runner prepares a progress report.
Copyable runner contract

Do not hide the pending action

Selections define fields to collect. They do not prove that a runner implements this contract.

What this bench proves. It keeps message type, active state, authority scope, and route outcome in one review card. It does not intercept an editor message, control a process, grant approval, or cancel work.

Sources and limits

Open the source log
  1. OpenAI Codex 0.158.0 release notes, read September 28, 2026. The release adds default terminal-input approval for elevated commands and fixes approval reviews that were aborted by new user input.
  2. Anthropic, "Prompting Claude Opus 5.5", read September 28, 2026. The guide documents text-only progress turns, explicit task-state checks, bounded continuations, progress-update blocks, and confirmation boundaries.
  3. Visual Studio Code 1.139 release notes, read September 28, 2026. Microsoft documents compact session rows that reveal input and approval needs and summarize hidden-chat progress.
  4. Zed 1.21.0 release notes, read September 28, 2026. Zed documents its default setting that prevents idle system sleep during running agent threads.

Source boundary. Each vendor documents its own product behavior. None claims the four-route control model on this page. The Operator Interruption Clutch is Pimp My IDE editorial synthesis and a planning tool. Test the actual runner before relying on it.