# Stopping and steering a running agent (`ui.interrupt_steer`)

Feedback Bench, coding agents, built 2026-10-01, window 2026-08-31 to 2026-09-27. Web page: https://feedbackbench.com/#/criterion/ui.interrupt_steer

Area: [Interface and sessions](https://feedbackbench.com/criteria/interface.md)

**Definition.** Whether the user can stop, interrupt or send guidance mid-run and have the agent respect it and continue.

**Boundary.** Not this: see [Stops mid-task or answers instead of acting](https://feedbackbench.com/criteria/work.premature_stop.md) for the agent stopping on its own.

Rated author-weeks, all agents: 160. Complaint share: 61%.

## The brief

Written by Claude Opus 5.5 from 46 labelled posts and the numbers on this page. Interpretation, not measurement: every quote is verbatim and links to its post.

**Steering works when it exists. Stop buttons and queues still misfire.**

TL;DR:

- Complaints outnumber praise for most agents, and the core failure is a stop that does not stop.
- Queue versus steer semantics confuse users. Messages interrupt, derail goals, or wait when they should redirect.
- Where mid-run steering works, users report saved tokens and earlier kills of runs going sideways.

In plain terms: You watch an agent drift and try to correct it. Sometimes a mid-task message lands cleanly. Often the stop is ignored, a queued note derails the run, or a reflexive key press kills more than you meant.

### How it breaks

- **The stop button that does not stop** ([Stopping and steering a running agent](https://feedbackbench.com/criteria/ui.interrupt_steer.md)). The worst reports describe agents that keep running after repeated stop commands, with users left worrying about the usage they burn.
  Posts describe pressing stop repeatedly overnight with no effect, agents stuck in a working state that cannot be halted, and one runaway agent that survived prompts, restarts and new sessions before reporting success. Softer versions show up too. Users say the agent obeys a stop for a few turns and then resumes. A steering error on Windows left one task running anyway. The pattern spans several vendors, so it reads as a category gap more than one product's bug.
  Evidence:
  - Complaint, OpenAI Codex, r/codex, 2026-09-07: “i was trying to stop this session since last night i hit stop multiple times but it just won't stop. i hope this isn't draining out my usage. anyone facing this issue or know any remediation?” [source](https://www.reddit.com/r/codex/comments/1wa1fir/session_doesnt_stop_when_i_hit_stop_in_the_new/)
  - Complaint, Google Antigravity, r/google_antigravity, 2026-09-26: “<strict_link> i am facing an issue (and its not first time), where the agent gets stuck in working and i can't stop it second problem is when its running cli commands it gets stuck” [source](https://www.reddit.com/r/google_antigravity/comments/1wqjig3/failed_to_stop_agent/)
  - Complaint, Kiro, r/kiroIDE, 2026-09-16: “i had a runaway agent once. it took all tasks, went into the background and continued for a couple of hours. no stopping of the thing. it survived prompts, commands, sessions and restarts. 100+ tokens on haiku and ~30 tasks later it happily reported in a newly opened session that it finished. micro-skynet experience. good it was a small private project.” [source](https://www.reddit.com/r/kiroIDE/comments/1whrobc/in_less_than_30_secs_kiro_uses_almost_100_credits/pa4s07y/)
  - Complaint, Claude Code, r/ClaudeCode, 2026-09-17: “yep, and it's annoying as hell. i've told mine to stop and it stopped for about three answers then keep going.” [source](https://www.reddit.com/r/ClaudeCode/comments/1we1nn0/anyone_seeing_claude_say_privately_a_lot_recently/pab91my/)

- **Queued messages land at the wrong time** ([Stopping and steering a running agent](https://feedbackbench.com/criteria/ui.interrupt_steer.md)). Users cannot predict whether a follow-up message will queue, steer or interrupt, and the wrong outcome derails the run.
  One user's queued QA prompts started steering an active long-running goal, even with follow-up behaviour set to queue. Another sent two quick unrelated messages, and the second silently replaced the first. Pi users say multiple steering messages go out one by one instead of as a single body, and a shortcut aborts the agent when it should only recall the queued text. Users want delivery after a tool call or after the task, chosen explicitly.
  Evidence:
  - Complaint, Amp, @AmpCode, 2026-09-12: “@sqs @ampcode @thorstenball if i run into the same thing i’ll report it. but it was like: i sent a message to do something and shortly after sent another message to do something else (unrelated to the former). i think it was with such short time in between that it just interrupted the first and forgot it” [source](https://twitter.com/872962356/status/2098703694615261199)
  - Complaint, OpenAI Codex, r/codex, 2026-09-06: “my workflow was to start a long running goal and submit several follow up prompts that were mostly different forms of qa, performance checks, complexity checks, bloat, etc. seemed to work better than ultra and concurrent agents for my code base. not sure if it's an astra thing or just a chatgpt desktop app update but ever since astra came out what will happen is that after working on the goal for a while it'll pull a message off of the queue. the goal is still active and didn't get blocked. the queued messages end up steering things which derails the goal. follow-up behavior is set to queue. anyone else seeing this?” [source](https://www.reddit.com/r/codex/comments/1w8lnsf/queue_bug/)
  - Complaint, Pi, @pidotdev, 2026-09-23: “@pidotdev steering is broken. multiple messages are sent one by one - they should be sent as one body. option+up aborts the agent, it should only bring the queued steering text back into editor. only esc should abort, and when text is queued, it should only interrupt the model and auto-submit the text.” [source](https://twitter.com/15266830/status/2102579401221099934)
  - Praise, OpenAI Codex, X search: OpenAI Codex, Codex CLI, Codex app, 2026-09-16: “@maria_rcks the message queue should be tow options send after tool call ends, or send after completing the task, like how codex cli handle it, as now in t3code it just send it after the of the running tool call” [source](https://twitter.com/2037599670050955264/status/2100324551829729753)

- **Escape and ctrl+c carry too much weight** ([Stopping and steering a running agent](https://feedbackbench.com/criteria/ui.interrupt_steer.md)). The same keys that clear input or copy text also kill agents and subagents, so reflexive presses cause damage.
  Users describe stopping a session just before a bad commit and having to remember which key does what in that second. Others say ctrl+c is too deeply wired into terminal habit to double as a subagent kill switch. They propose clearing the input first and stopping agents only when the input is empty. In Codex CLI with computer use, pressing escape to send a queued message closes every tab. Safer escape and ctrl+c priority is a recurring request.
  Evidence:
  - Complaint, Claude Code, r/ClaudeCode, 2026-09-15: “agreed. had to stop a session mid-action yesterday because it was about to commit to the wrong branch, and pausing to remember which key does what is not what you want in that second.” [source](https://www.reddit.com/r/ClaudeCode/comments/1wh0dqn/having_ctrlc_for_both_clearing_input_and_stopping/pa0bwep/)
  - Complaint, Claude Code, r/ClaudeCode, 2026-09-15: “yeah this seems like a really easy thing to do by accident. ctrl+c is so deeply wired into terminal habits that using the same key to kill running subagents feels risky. making it clear the input first and only stop subagents when the input is empty would make way more sense imo” [source](https://www.reddit.com/r/ClaudeCode/comments/1wh0dqn/having_ctrlc_for_both_clearing_input_and_stopping/pa0b5ur/)
  - Complaint, OpenAI Codex, X search: OpenAI Codex, Codex CLI, Codex app, 2026-09-22: “@thsottiaux in codex cli w/ computer use, if i press esc all the tabs get closed. often all i'm trying to do is send the next queued message to tell it to do somethign slightly different.” [source](https://twitter.com/16219198/status/2102299560962072706)

- **Steer mode missing, only queue or kill** ([Stopping and steering a running agent](https://feedbackbench.com/criteria/ui.interrupt_steer.md)). Several agents offer queue and hard interrupt but nothing in between, which is the mode users say they want most.
  A Devin user explains that interrupt terminates every subagent, when almost always they just want to redirect. Antigravity users ask for steering ahead of other features, and mid-run steering is the most requested change on this page. An OpenCode user lists message steering among features missed from another CLI. A Pi user wants to inject an answer into a looping reasoning block instead of restarting it or waiting out tens of thousands of tokens.
  Evidence:
  - Complaint, Google Antigravity, @antigravity, 2026-09-27: “@antigravity i suggest you implement missing features that are still needed (like steering), rather than redundant features that went out of style more than 6 months ago.” [source](https://twitter.com/14228971/status/2104137839525126361)
  - Complaint, Devin, @cognition, 2026-09-18: “@devindesktop @cognition @russelljkaplan can you please add steering for sessions, in addition to queueing messages, allow us to choose the default for new messages during an active session. currently, it queues by default, and the only other option is interupt, which terminates all subagents working, when 99% of the time, users want to steer the session, and not interupt. if we wanted to interupt, we would hit the stop button.” [source](https://twitter.com/43418580/status/2101040791330369835)
  - Complaint, OpenCode, @opencode, 2026-09-10: “finally gave a serious try to @opencode for personal project and suddenly missed the following ( compared to @githubcopilot cli ) message steering, branch /diff ( from main even after pushing ), /btw , ctrl+c protection, plan however still impressed with tui, free zen models” [source](https://twitter.com/15468471/status/2098084461204390142)
  - Complaint, Pi, r/PiCodingAgent, 2026-09-10: “many models (namely qwens 3.8) think a lot, and i find myself wanting to interrupt it to answer a question it's been asking itself, quite repetitively, during it's reasoning. i can `esc` and send a prompt, but then pi would restart the whole reasoning tg from the beginning. i'd like to *inject* (for lack of better word) info to its thought block. i may also `steer` it by queuing a message, but that means i'd need to watch it going in loops for 20-50k tokens, until it's done responding, which is pure pain. am i missing a clear command?” [source](https://www.reddit.com/r/PiCodingAgent/comments/1wcwsya/noob_question_how_to_interrupt_an_agent_during/)

- **When steering works, it saves the run** ([Stopping and steering a running agent](https://feedbackbench.com/criteria/ui.interrupt_steer.md)). Users who get clean mid-run steering credit it with lower token spend and catching drift early instead of after the damage.
  Users praise redirecting an agent without interrupting the prompt, and sending messages mid-task while work continues normally. A Pi user reports a locked harness test where steering roughly halved cost. Claude Code users value attaching to a live session to kill a run at step 3 instead of step 30. The value is clearest on long tool loops, and one Cline post notes it matters little for one-shot prompts.
  Evidence:
  - Praise, Cursor, @cursor_ai, 2026-09-24: “the ability to redirect @cursor_ai without interupting the prompt is a great time and token saver <strict_link>” [source](https://twitter.com/1226630083/status/2102912927166783905)
  - Praise, OpenAI Codex, r/codex, 2026-09-22: “i also noticed that i can send messages mid tasks and it continues to work normally!” [source](https://www.reddit.com/r/codex/comments/1wnp2lb/can_we_change_6sol_and_6luna_reasoning_level_mid/pbgtm4x/)
  - Praise, Pi, @pidotdev, 2026-09-11: “@ryanteoyx @pidotdev 100%. the harness is the product surface. in our locked harness test, the same task was $0.43 vs $0.88 and 149k vs 439k tokens. steering mid-run is the point.” [source](https://twitter.com/2074942490466033664/status/2098431008878051435)
  - Praise, Claude Code, @ClaudeDevs, 2026-09-10: “@claudedevs reading logs after a long unattended run means you learn the agent went sideways once the tokens are already spent. attaching to a live session turns that into killing it at step 3 instead of step 30. the `--web` localhost viewer is the part i'd actually use.” [source](https://twitter.com/1722852991194255360/status/2098143597761806381)

### Who stands out

- **OpenAI Codex (mixed)**. Codex sets the reference for queue and steer UX, and other tools get measured against it, yet its stop and queue reliability draws pointed complaints.
  Users call the Codex app really good at queue and steer and cite Codex CLI's delivery options as the model to copy. One OpenCode contributor says steering is still nicer in Codex. A blunt interrupt reportedly snaps it out of tangents. The flip side is a stop that would not stop and queued prompts that began steering an active goal. Reliable prompt queue and steering delivery is the top Codex-specific ask.
  Evidence:
  - Praise, OpenAI Codex, X search: OpenAI Codex, Codex CLI, Codex app, 2026-09-13: “@maria_rcks -auto-archive settled threads? or a much seamless way to archive. currently it's very "settle-only". -queue and steer (codex app is really good with this) -default model+reasoning+provider (something like profiles?), and with quick-switch b/w them.” [source](https://twitter.com/1662060989175549952/status/2098997578243195387)
  - Praise, OpenAI Codex, r/opencodeCLI, 2026-09-11: “i fixed the steering yesterday with <strict_link> it’s still nicer in codex, but i didn’t want to make big ui changes which then get rejected by the maintainers haha” [source](https://www.reddit.com/r/opencodeCLI/comments/1wadfq4/what_do_you_think_about_opencode_v2/p96xcaf/)
  - Complaint, OpenAI Codex, r/codex, 2026-09-06: “my workflow was to start a long running goal and submit several follow up prompts that were mostly different forms of qa, performance checks, complexity checks, bloat, etc. seemed to work better than ultra and concurrent agents for my code base. not sure if it's an astra thing or just a chatgpt desktop app update but ever since astra came out what will happen is that after working on the goal for a while it'll pull a message off of the queue. the goal is still active and didn't get blocked. the queued messages end up steering things which derails the goal. follow-up behavior is set to queue. anyone else seeing this?” [source](https://www.reddit.com/r/codex/comments/1w8lnsf/queue_bug/)
  - Complaint, OpenAI Codex, r/codex, 2026-09-07: “i was trying to stop this session since last night i hit stop multiple times but it just won't stop. i hope this isn't draining out my usage. anyone facing this issue or know any remediation?” [source](https://www.reddit.com/r/codex/comments/1wa1fir/session_doesnt_stop_when_i_hit_stop_in_the_new/)

- **Claude Code (weaker)**. Complaints dominate. Users report Claude Code ignoring stop and check-in messages, plus key bindings that make interrupts risky.
  Posts describe the agent running wild for an hour and ignoring the user, or stopping briefly and then carrying on. Key handling is a second sore point, with escape and ctrl+c doing too much at once. On the praise side, users credit Claude Code's chat interface and steering with closing the gap on Codex for remote work, and value live-session viewing to kill runs early.
  Evidence:
  - Complaint, Claude Code, r/ClaudeCode, 2026-09-03: “yes absolutely hate when it runs wild for an hour and fucking ignores you when you check on it” [source](https://www.reddit.com/r/ClaudeCode/comments/1w6j804/its_been_a_couple_of_days_since_fable_51_was/p7nziex/)
  - Praise, Claude Code, r/ClaudeCode, 2026-09-21: “i used claude code (ios web) exclusively, no computer, and it really closed the gap from using codex. it could do so much! getting the results to non claude was usually manual but claude code (ios web) could hit github direct or use my published site when that was rate limited, to see ci results and run on a windows env to get real answers that it couldn’t in linux sandbox. so amazing. did this all while i was nap trapped. really the game changer was the chat interface and steering ability that codex didn’t have, and giving it a goal was excellent! also, have another bot auto review the prs was really the final loop. still needs a human in the loop though, as always. [<strict_link>” [source](https://www.reddit.com/r/ClaudeCode/comments/1wls9ul/would_you_actually_use_claude_code_from_your/pb2pg49/)
  - Praise, Claude Code, @ClaudeDevs, 2026-09-10: “@claudedevs reading logs after a long unattended run means you learn the agent went sideways once the tokens are already spent. attaching to a live session turns that into killing it at step 3 instead of step 30. the `--web` localhost viewer is the part i'd actually use.” [source](https://twitter.com/1722852991194255360/status/2098143597761806381)
  - Complaint, Claude Code, r/ClaudeCode, 2026-09-15: “yeah this seems like a really easy thing to do by accident. ctrl+c is so deeply wired into terminal habits that using the same key to kill running subagents feels risky. making it clear the input first and only stop subagents when the input is empty would make way more sense imo” [source](https://www.reddit.com/r/ClaudeCode/comments/1wh0dqn/having_ctrlc_for_both_clearing_input_and_stopping/pa0b5ur/)

- **Google Antigravity (mixed)**. Antigravity draws the most requests for mid-run steering, even as its agent team design earns praise for keeping a main session open for corrections.
  Users like that the main session stays available for course corrections while a team preview runs. They also welcome a new shortcut for quickly raising questions about responses. Complaints describe agents stuck in a working state that cannot be stopped, and blunt requests to ship steering before anything else. Pause and resume, plus clearer guidance on how to steer, also appear among its asks.
  Evidence:
  - Praise, Google Antigravity, r/google_antigravity, 2026-09-05: “i started using antigravity cli myself recently. really like the agent team design there. once you start the teamwork-preview, the main session is still available to communicate and update and do proper course corrections.” [source](https://www.reddit.com/r/google_antigravity/comments/1w6h936/google_claims_are_correct_guys/p7vrf8s/)
  - Complaint, Google Antigravity, @antigravity, 2026-09-27: “@antigravity i suggest you implement missing features that are still needed (like steering), rather than redundant features that went out of style more than 6 months ago.” [source](https://twitter.com/14228971/status/2104137839525126361)
  - Complaint, Google Antigravity, r/google_antigravity, 2026-09-26: “<strict_link> i am facing an issue (and its not first time), where the agent gets stuck in working and i can't stop it second problem is when its running cli commands it gets stuck” [source](https://www.reddit.com/r/google_antigravity/comments/1wqjig3/failed_to_stop_agent/)
  - Praise, Google Antigravity, @antigravity, 2026-09-03: “it's indeed an important capability to complain about antigravity early on, and now it's added, very impressive!!! @antigravity however, there still seem to be some minor issues: 1. for cautious work like ours used in production, multi-turn dialogue is very important, being able to quickly raise questions about ai responses and add them to the input box is crucial. now it finally exists, and there's even a shortcut cmd+l. 2. a shortcoming is that when selecting long segments of text, this button shifts to a far position, which i really hope can be optimized!!! 3. i hope to add the functionality of a side dialogue box and include a shortcut to select context to add to the side dialogue box; this feature is much more useful than /btw.” [source](https://twitter.com/2031285494081007620/status/2095416077484478632)

- **Cursor (mixed)**. Cursor's steering and side chat earn praise, but users struggle to simply queue a message for after the current task.
  Users say redirecting Cursor without interrupting saves time and tokens. They describe side chat as where the real steering happens, keeping the main thread on the long plan. The friction is queueing. One user could not find a way to send a message for after the task finishes, and the steer mode guesses whether input is a redirect or a next task. Queue messages instead of interrupting is Cursor's leading request.
  Evidence:
  - Praise, Cursor, @cursor_ai, 2026-09-02: “@dev2o @cursor_ai yeah sidechat is where the real steering happens for me too. main thread stays the long plan, sidechat is "try this one thing without polluting the context". cloud agents especially.” [source](https://twitter.com/2093464934143447040/status/2094955618440237548)
  - Praise, Cursor, @cursor_ai, 2026-09-24: “the ability to redirect @cursor_ai without interupting the prompt is a great time and token saver <strict_link>” [source](https://twitter.com/1226630083/status/2102912927166783905)
  - Complaint, Cursor, r/cursor, 2026-09-15: “i can't tell if i'm taking crazy pills or remembering a different tool. can i send a message to the queue in agent mode so that it'll be sent once the current task is done? i tried switching the new message mode to "steer" which does seem to try and decide if the user is redirecting the agent or providing the next task.” [source](https://www.reddit.com/r/cursor/comments/1whanho/can_i_queue_a_message_to_be_sent_after_the/)

### Fine print

- Most agents have too few posts here to separate from the pack. Treat leader calls beyond Codex and Claude Code as directional.
- Evidence covers one month of public posts. Some quotes come from third-party tools comparing themselves to these agents.

## Top requests

What users ask to add or change, most asked first. 64 author-weeks ask for something. Requests do not change the Feedback Score. Rule: A separate pass by Claude Sonnet 5 reads every counted post and extracts what the author asks the agent or its vendor to add or change, with the criteria it maps to and a short normalised wording; it does not touch the labels or the Feedback Score. Claude Opus 5.5 groups the wordings within each criterion (the first criterion the request maps to) into themes; code counts them. A theme counts distinct author-weeks that ask for it, per agent; across agents, one author-week per agent. Themes asked in fewer than 2 author-weeks, and requests that share no theme, are not shown. Examples: up to 3 posts per theme from different authors, without slurs, preferring posts of 60 to 450 characters, most recent first.

| Rank | Request | Author-weeks | Posts | Agents (author-weeks) |
|---|---|---|---|---|
| 1 | Mid-run steering of a running agent | 14 | 14 | Google Antigravity 5, Claude Code 2, OpenAI Codex 2, OpenCode 2, GitHub Copilot 1, Devin 1, Pi 1 |
| 2 | Queue messages instead of interrupting | 9 | 9 | Cursor 5, OpenCode 2, Google Antigravity 1, OpenAI Codex 1 |
| 3 | Reliable prompt queue and steering delivery | 7 | 7 | OpenAI Codex 3, Pi 2, Cursor 1, OpenCode 1 |
| 4 | Safer escape and ctrl+c key priority | 7 | 7 | Claude Code 3, Pi 2, OpenAI Codex 1, OpenCode 1 |
| 5 | Configurable steer vs queue vs interrupt behavior | 5 | 5 | OpenAI Codex 2, Devin 2, Claude Code 1 |
| 6 | Auto-resume after usage limit or outage | 4 | 4 | Claude Code 2, OpenAI Codex 2 |
| 7 | Pause and resume running sessions | 4 | 4 | Google Antigravity 2, Claude Code 1, OpenCode 1 |
| 8 | Clear indication of how to steer or interrupt | 2 | 2 | Google Antigravity 1, OpenAI Codex 1 |
| 9 | Edit and retract last prompt | 2 | 2 | Google Antigravity 1, Devin 1 |
| 10 | Interrupt voice mode mid-speech | 2 | 2 | Claude Code 1, OpenCode 1 |
| 11 | Steer agent from external chat bridge | 2 | 2 | OpenAI Codex 2 |

### 1. Mid-run steering of a running agent

- Google Antigravity, 2026-09-27, @antigravity (X): “@antigravity i suggest you implement missing features that are still needed (like steering), rather than redundant features that went out of style more than 6 months ago.” [source](https://twitter.com/14228971/status/2104137839525126361)
- Google Antigravity, 2026-09-24, @antigravity (X): “ctrl+enter to send the message while the agent is still running in @claudeai code, after recent update !!! glad that at least @grok cli and @antigravity have already done these optimizations for user interaction with coding agents. just waiting for their better and cheaper models now. grok 4.7 and 4.6 are too expensive… and ngl, gemini 4 is still a myth at this point. 😂” [source](https://twitter.com/1500117043391397894/status/2103200620379537819)
- Claude Code, 2026-09-18, r/ClaudeCode (Reddit): “it only works after the output. claude has no real way of steering itself in the moment, no matter what you specify in any doc or hook.” [source](https://www.reddit.com/r/ClaudeCode/comments/1wjt3kc/whats_the_most_boring_thing_you_use_claude_for/pamojz5/)

### 2. Queue messages instead of interrupting

- OpenCode, 2026-09-20, r/opencode (Reddit): “yeah bro i also find several features missing : 1. plan mode 2. queue messages and many more” [source](https://www.reddit.com/r/opencode/comments/1wlkq6c/windows_app_has_no_plan_mode/pazcvae/)
- Google Antigravity, 2026-09-16, @antigravity (X): “@antigravity if i queue multiple prompts/instructions in antigravity cli, they should execute one at a time. for example, if i have 4 prompts in the queue, once the current task completes, only the next prompt should start. right now, all 4 start executing simultaneously. please fix this queue behavior.” [source](https://twitter.com/2087900731345182721/status/2100222357088665715)
- Cursor, 2026-09-15, @cursor_ai (X): “i wish all agent interfaces would adopt message queuing as a default instead of interruption, but then let me interrupt as a second step if desired. (thanks, @cursor_ai &amp; looking at you for an update @chatgpt)” [source](https://twitter.com/9580792/status/2099849750635778253)

### 3. Reliable prompt queue and steering delivery

- OpenAI Codex, 2026-09-27, X search: OpenAI Codex, Codex CLI, Codex app (X): “@thsottiaux dude, please, can you fix steering in the codex app? it literally like doesn't reply to my earlier messages when steered. this seems like a ui bug, not a model bug” [source](https://twitter.com/1473468965313814530/status/2104244788677554626)
- Pi, 2026-09-23, @pidotdev (X): “@pidotdev steering is broken. multiple messages are sent one by one - they should be sent as one body. option+up aborts the agent, it should only bring the queued steering text back into editor. only esc should abort, and when text is queued, it should only interrupt the model and auto-submit the text.” [source](https://twitter.com/15266830/status/2102579401221099934)
- Pi, 2026-09-22, @pidotdev (X): “@pidotdev allow enter on an empty input to force-send the next scheduled message when one is queued.” [source](https://twitter.com/1077764990/status/2102391128217813462)

### 4. Safer escape and ctrl+c key priority

- OpenAI Codex, 2026-09-22, X search: OpenAI Codex, Codex CLI, Codex app (X): “@thsottiaux in codex cli w/ computer use, if i press esc all the tabs get closed. often all i'm trying to do is send the next queued message to tell it to do somethign slightly different.” [source](https://twitter.com/16219198/status/2102299560962072706)
- Claude Code, 2026-09-15, r/ClaudeCode (Reddit): “yeah this seems like a really easy thing to do by accident. ctrl+c is so deeply wired into terminal habits that using the same key to kill running subagents feels risky. making it clear the input first and only stop subagents when the input is empty would make way more sense imo” [source](https://www.reddit.com/r/ClaudeCode/comments/1wh0dqn/having_ctrlc_for_both_clearing_input_and_stopping/pa0b5ur/)
- Pi, 2026-09-13, r/PiCodingAgent (Reddit): “yup, preserve thinking should do the trick. a full prefill on esc would drive me insane.” [source](https://www.reddit.com/r/PiCodingAgent/comments/1wcwsya/noob_question_how_to_interrupt_an_agent_during/p9nc0sp/)

### 5. Configurable steer vs queue vs interrupt behavior

- OpenAI Codex, 2026-09-26, X search: OpenAI Codex, Codex CLI, Codex app (X): “feature suggestion for @claudeai / @openai codex: when i send a new prompt while the agent is working on something, use a model to decide whether to queue the message or interrupt the current task with it” [source](https://twitter.com/1672561884954763265/status/2103859702354309486)
- Devin, 2026-09-18, @cognition (X): “@devindesktop @cognition @russelljkaplan can you please add steering for sessions, in addition to queueing messages, allow us to choose the default for new messages during an active session. currently, it queues by default, and the only other option is interupt, which terminates all subagents working, when 99% of the time, users want to steer the session, and not interupt. if we wanted to interupt, we would hit the stop button.” [source](https://twitter.com/43418580/status/2101040791330369835)
- OpenAI Codex, 2026-09-16, X search: OpenAI Codex, Codex CLI, Codex app (X): “@maria_rcks the message queue should be tow options send after tool call ends, or send after completing the task, like how codex cli handle it, as now in t3code it just send it after the of the running tool call” [source](https://twitter.com/2037599670050955264/status/2100324551829729753)

### 6. Auto-resume after usage limit or outage

- OpenAI Codex, 2026-09-05, X search: OpenAI Codex, Codex CLI, Codex app (X): “3. in codex app - when usage drains i need to prompt "continue". instead you should have a "continue the session" button appear after usage is reset (that also continues all subagents if needed).” [source](https://twitter.com/1957013124088815616/status/2096192539543966127)
- Claude Code, 2026-09-03, @ClaudeDevs (X): “why not auto continue when the services comes back online so we don't have to sit around waiting and constantly checking? same feature as the 5hr session limit at 100% and it automatically continues on reset. but it needs to also work on mobile app! @claudedevs @claudeai <strict_link>” [source](https://twitter.com/1694316723623882752/status/2095518833289437235)
- Claude Code, 2026-09-01, r/ClaudeCode (Reddit): “<strict_link> i was pretty fed up with having to remember to go tell my sessions "retry" or "continue" after my usage renewed. so i got claude to build me a stylised wake up tool which i can select which sessions to watch and then restart when my usage renews after my 5 hour limit or weekly limit. [it has a nice animation at the top too. the gym bot goes and pokes the claude bot.](<strict_link>) and yes it has dark mode: <strict_link> if you woul” [source](https://www.reddit.com/r/ClaudeCode/comments/1w45r06/i_made_a_claude_kicker_program_to_wake_cowork_or/)

### 7. Pause and resume running sessions

- OpenCode, 2026-09-17, @opencode (X): “@opseclo @kaushikgopal @opencode that's the boundary i want too. let the foreground tool finish, then pause before the agent's own final answer so i can inspect and steer. queueing is not control. recovery only counts if i can see the time and spend to get back on track.” [source](https://twitter.com/2074942490466033664/status/2100698112545247258)
- Claude Code, 2026-09-10, @ClaudeDevs (X): “@claudedevs the next step is making the viewer an intervention surface: pause, branch from the last good checkpoint, and attach with the agent's current plan plus context budget visible. observability after a bad branch is useful; reversible execution is what saves the run.” [source](https://twitter.com/796459536265539584/status/2098136179920998548)
- Google Antigravity, 2026-09-01, r/google_antigravity (Reddit): “pausing and unpausing in general is a missing feature imo. maybe because of the memory requirements of holding the network activation state for indefinite lengths of time it’s unworkable. probably it takes a big architectural solution like compressing and decompressing activations.” [source](https://www.reddit.com/r/google_antigravity/comments/1w4lqi9/teamwork_aborting_and_resuming_work_how_to_do_it/p78tref/)

### 8. Clear indication of how to steer or interrupt

- Google Antigravity, 2026-09-16, r/google_antigravity (Reddit): “they responded in the same tone as the post. i think it’s reasonable in this case. the original poster doesn’t understand how to use the tool and is claiming agy and the model doesn’t work. while i see issues with both on occasion, one can’t blame the tool when they don’t know how to use it. the only valid feedback is that agy should make it more clear how to interrupt or steer it on startup. that’s the takeaway from this post for google.” [source](https://www.reddit.com/r/google_antigravity/comments/1whsyhq/i_will_keep_posting_to_show_how_incapable_gemini/pa5vsr0/)
- OpenAI Codex, 2026-09-21, r/codex (Reddit): “thanks a ton for reaching out .. i really appreciate this, and my apologies for a casual dismissal of letta while discussing codex. initially, the letta tutor agent said it didn't have web access, and it was using curl commands. i then had it use the pi web access extension. i found out now that letta has a mods feature where the agent modifies the harness to include extensions for web search and more. i had the gpt luna model write a mod based” [source](https://www.reddit.com/r/codex/comments/1wkosz1/is_the_astra_as_a_subagent_workflow_valid/pb808uz/)

### 9. Edit and retract last prompt

- Devin, 2026-09-13, r/windsurf (Reddit): “is there anywhere to report these missing features that make devin's acp server a bit lacking? * ability to fork a thread * ability to edit the last sent prompt (stop the active turn and replace the old prompt and any agent work after it) having just these features would be huge, so i'd like to make sure the devin team is aware of them.” [source](https://www.reddit.com/r/windsurf/comments/1wfi8l4/devin_acp_missing_features/)
- Google Antigravity, 2026-09-14, @antigravity (X): “@antigravity i urgently hope to optimize the withdrawal function. as it is now, the user's operation circuit is too long and the efficiency is very low. i hope the undo function can learn from codex and cursor. antigravity: click to withdraw → then you have to click the 'confirm' on the confirmation pop-up again → and that message goes back to the bottom message input box. codex/cursor: after clicking to withdraw, there is a second confirmation,” [source](https://twitter.com/1728671180230647808/status/2099646145735930247)

### 10. Interrupt voice mode mid-speech

- OpenCode, 2026-09-23, r/opencode (Reddit): “i stand to this. many times i found myself wanting to verbally give instructions or interact, but unable. you made a good point” [source](https://www.reddit.com/r/opencode/comments/1wnstna/im_building_native_local_voice_input_for_opencode/pbnirb9/)
- Claude Code, 2026-09-09, r/ClaudeCode (Reddit): “i might be in a minority here but i'm with the op. in voice conversation mode there are frustrating moments where it misunderstands me or it continues talking while i'm trying to rudely interrupt it etc. it's the same as when we use a computer and excel randomly freezes, we don't sit there and say "oh dear, i suppose that is rather annoying". i really don't want claude to be "more human". i just want it to stop god damn saying "absolutely"” [source](https://www.reddit.com/r/ClaudeCode/comments/1wbaxjh/im_sick_of_claude_acting_like_its_a_person/p8uffwb/)

### 11. Steer agent from external chat bridge

- OpenAI Codex, 2026-09-07, r/codex (Reddit): “and when app is built: connector via chat for mid-sessions/reviews. you could use desktop sol/astra i suppose but honestly i have no clue how expensive that might be. i don't really 'chat' with codex - for that i use chatgpt browser.” [source](https://www.reddit.com/r/codex/comments/1w9l5rd/do_i_need_the_pro/p8bgnw7/)
- OpenAI Codex, 2026-09-05, X search: OpenAI Codex, Codex CLI, Codex app (X): “@thsottiaux help me cancel my claude subscription. codex app server with a telegram bridge seems rough, agent does not drive tasks to completion, stops often. claude code is able to inject my telegram messages right into a session, is there an equivalent in codex?” [source](https://twitter.com/2267844098/status/2096383921424396751)

## Every agent

| Agent | Overall rank | Reading | Customer love | 95% interval | n | Praise | Complaint |
|---|---|---|---|---|---|---|---|
| [OpenAI Codex](https://feedbackbench.com/agents/codex.md) | 2 | Typical | 0.506 | 0.485–0.528 | 54 | 21 | 33 |
| [Claude Code](https://feedbackbench.com/agents/claude-code.md) | 1 | Typical | 0.490 | 0.469–0.511 | 40 | 12 | 28 |
| [Google Antigravity](https://feedbackbench.com/agents/antigravity.md) | =5 | Too few posts | – | – | 20 | 9 | 11 |
| [Cursor](https://feedbackbench.com/agents/cursor.md) | 4 | Too few posts | – | – | 18 | 6 | 12 |
| [OpenCode](https://feedbackbench.com/agents/opencode.md) | 3 | Too few posts | – | – | 10 | 5 | 5 |
| [Devin](https://feedbackbench.com/agents/devin.md) | =5 | Too few posts | – | – | 6 | 3 | 3 |
| [Pi](https://feedbackbench.com/agents/pi.md) | 7 | Too few posts | – | – | 5 | 3 | 2 |
| [Cline](https://feedbackbench.com/agents/cline.md) | =8 | Too few posts | – | – | 2 | 1 | 1 |
| [Amp](https://feedbackbench.com/agents/amp.md) | =11 | Too few posts | – | – | 2 | 0 | 2 |
| [GitHub Copilot](https://feedbackbench.com/agents/copilot.md) | =8 | Too few posts | – | – | 1 | 1 | 0 |
| [Factory](https://feedbackbench.com/agents/factory.md) | =11 | Too few posts | – | – | 1 | 1 | 0 |
| [Kiro](https://feedbackbench.com/agents/kiro.md) | 13 | Too few posts | – | – | 1 | 0 | 1 |
| [Zed](https://feedbackbench.com/agents/zed.md) | =8 | Too few posts | – | – | 0 | 0 | 0 |
| [Conductor](https://feedbackbench.com/agents/conductor.md) | 14 | Too few posts | – | – | 0 | 0 | 0 |
| [Warp](https://feedbackbench.com/agents/warp.md) | 15 | Too few posts | – | – | 0 | 0 | 0 |
| [Grok Build](https://feedbackbench.com/agents/grok-build.md) | 16 | Too few posts | – | – | 0 | 0 | 0 |
| [Augment Code](https://feedbackbench.com/agents/augment.md) | 17 | Too few posts | – | – | 0 | 0 | 0 |

## Posts

Receipts rule: The 5 most recent praise and complaint posts per area (first 700 characters) and 3 per criterion (first 450 characters).

### OpenAI Codex

- Praise, 2026-09-27, r/codex (Reddit): “the interrupt queuing thing is actually pretty clever since most scheduled tasks sit idle anyway, but does it mean you lose the execution if you close the cli entirely before sending another message?” [source](https://www.reddit.com/r/codex/comments/1wrp1co/yet_another_cron_for_codex_cli/pceb521/)
- Praise, 2026-09-22, r/codex (Reddit): “i also noticed that i can send messages mid tasks and it continues to work normally!” [source](https://www.reddit.com/r/codex/comments/1wnp2lb/can_we_change_6sol_and_6luna_reasoning_level_mid/pbgtm4x/)
- Praise, 2026-09-21, r/codex (Reddit): “claude for a while there at least when i used opus 4.6 would respond to frustration and anger quite well. i switched to codex and codex does seem to some, it seems to get the picture more but not quite like claude. it does seem to pop its bubble though. if codex goes on these long tangents trying to fix a code problem that could just be adjusted by changing the server port in the spec or something i’ll interrupt it with “what the fuck are you do” [source](https://www.reddit.com/r/codex/comments/1wlq5uk/make_me_proud_is_the_best_prompt_ive_ever_written/pb6hp00/)
- Complaint, 2026-09-27, X search: OpenAI Codex, Codex CLI, Codex app (X): “@thsottiaux dude, please, can you fix steering in the codex app? it literally like doesn't reply to my earlier messages when steered. this seems like a ui bug, not a model bug” [source](https://twitter.com/1473468965313814530/status/2104244788677554626)
- Complaint, 2026-09-22, X search: OpenAI Codex, Codex CLI, Codex app (X): “@thsottiaux in codex cli w/ computer use, if i press esc all the tabs get closed. often all i'm trying to do is send the next queued message to tell it to do somethign slightly different.” [source](https://twitter.com/16219198/status/2102299560962072706)
- Complaint, 2026-09-21, r/codex (Reddit): “trying out your system as in burning entire week in a day or so. main thing i suggest is fixes to not have every task try to use this as it’s a bit much, i will send you a pr if you want on the skill fixes. also wondering thoughts on token use by polling or keeping a goal running with this. i found it annoying that when i would chat to astra mid-task, it would then stop its watching of the flash subagent, so no steering during runs which i like t” [source](https://www.reddit.com/r/codex/comments/1wmlu4x/i_reduced_my_astra_usage_by_94_on_a_23hour_build/pb9gxtu/)

### Claude Code

- Praise, 2026-09-25, r/ClaudeCode (Reddit): “i like to know when it's doing things like that. sometimes i interrupt it and tell it not to recheck things.” [source](https://www.reddit.com/r/ClaudeCode/comments/1wji8f7/let_me_look_at_the_documents_rather_than_guess_it/pbwbuzb/)
- Praise, 2026-09-25, r/ClaudeCode (Reddit): “i think codex already has this feature and glad to see this in claude as well. nice little improvement and it really helps when you are in middle of important task.” [source](https://www.reddit.com/r/ClaudeCode/comments/1wqagzu/claude_added_graceful_stopping_point_in_new_update/)
- Praise, 2026-09-24, r/ClaudeAI (Reddit): “how a menu-bar app drives a real claude code session: a message mid-turn, permission prompts answered in a bubble, and claude --resume to pick it up in terminal i built a macos menu-bar app that talks to claude code, and the interesting part turned out to be the plumbing rather than the app itself. writing it down because most of it is reusable by anyone driving the cli from their own program. <strict_link> the setup: you hold a key and speak,” [source](https://www.reddit.com/r/ClaudeAI/comments/1wonh3k/how_a_menubar_app_drives_a_real_claude_code/)
- Complaint, 2026-09-26, @ClaudeDevs (X): “@claudedevs not sure why but this didnt happen on the last session... he picked up where he left off after reviewing the cache but yeah not graceful stop or halt” [source](https://twitter.com/1732237892041179136/status/2103794600083116095)
- Complaint, 2026-09-25, r/codex (Reddit): “"stop" is exactly what i don't have. i can guarantee the question: when the session asks, the answer will be there. but stopping it if it can't answer? no. this is an agreement of intent, not a lock; a session that hasn't asked passes right through. i deliberately chose not to build the guard. to stop a session, you have to stand between it and its own tools — that means wrapping the client, and then you're no longer working in claude code or cod” [source](https://www.reddit.com/r/codex/comments/1wgzaqd/has_anyone_made_existing_claude_code_codex/pbw56ev/)
- Complaint, 2026-09-25, r/codex (Reddit): “i'm building a hermes plugin for running coding agents and want to see how other people are doing this before i go further. would like to hear what works for you and what doesn't. my setup right now: hermes only orchestrates, it doesn't write code. everything goes to claude code, codex or pi. hermes is on a vps and the workers run on my mac. * all the harnesses run in their normal interactive tui, no -p or exec. partly billing, partly because i w” [source](https://www.reddit.com/r/codex/comments/1wpj1y8/how_are_you_guys_running_claude_code_codex_and_pi/)

### Google Antigravity

- Praise, 2026-09-24, @antigravity (X): “ctrl+enter to send the message while the agent is still running in @claudeai code, after recent update !!! glad that at least @grok cli and @antigravity have already done these optimizations for user interaction with coding agents. just waiting for their better and cheaper models now. grok 4.7 and 4.6 are too expensive… and ngl, gemini 4 is still a myth at this point. 😂” [source](https://twitter.com/1500117043391397894/status/2103200620379537819)
- Praise, 2026-09-24, r/LocalLLaMA (Reddit): “i've been using vs code and the qwen code harness lately, but back in the olden times (~6 months ago) i was using antigravity and it had one feature i miss - the ability to "interject" while the model was doing stuff. it would insert your prompt into the flow of its execution at the appropriate moment and tag it up as an interjection so the llm would know. with qwen code there doesn't seem to be this function so i do the big-red-button interrupt” [source](https://www.reddit.com/r/LocalLLaMA/comments/1wp0z3i/qwen3827b_is_good_enough_that_i_stopped_using_api/pbs2dlo/)
- Praise, 2026-09-18, r/google_antigravity (Reddit): “when this starts to happen, i interrupt (steer) it telling it to move on. that usually helps.” [source](https://www.reddit.com/r/google_antigravity/comments/1w9574o/gemini_flash_38_is_wasting_all_my_tokens/pamg8ex/)
- Complaint, 2026-09-27, @antigravity (X): “@antigravity i suggest you implement missing features that are still needed (like steering), rather than redundant features that went out of style more than 6 months ago.” [source](https://twitter.com/14228971/status/2104137839525126361)
- Complaint, 2026-09-26, r/google_antigravity (Reddit): “<strict_link> i am facing an issue (and its not first time), where the agent gets stuck in working and i can't stop it second problem is when its running cli commands it gets stuck” [source](https://www.reddit.com/r/google_antigravity/comments/1wqjig3/failed_to_stop_agent/)
- Complaint, 2026-09-22, r/google_antigravity (Reddit): “yeah, it just reads and reads... sometimes when i tell it to stop it actually does but i'm lucky to have that happen” [source](https://www.reddit.com/r/google_antigravity/comments/1wni05g/we_need_a_usage_reset_now/pbf7wzo/)

### Cursor

- Praise, 2026-09-24, @cursor_ai (X): “the ability to redirect @cursor_ai without interupting the prompt is a great time and token saver <strict_link>” [source](https://twitter.com/1226630083/status/2102912927166783905)
- Praise, 2026-09-15, @cursor_ai (X): “i wish all agent interfaces would adopt message queuing as a default instead of interruption, but then let me interrupt as a second step if desired. (thanks, @cursor_ai &amp; looking at you for an update @chatgpt)” [source](https://twitter.com/9580792/status/2099849750635778253)
- Praise, 2026-09-14, @cursor_ai (X): “love this copy in @cursor_ai - when it's working on something, the input placeholder says 'steer without interrupting'. it just removes the confusion. 📍captured with @snapit_space <strict_link>” [source](https://twitter.com/786612789012029440/status/2099332921752711412)
- Complaint, 2026-09-19, @cursor_ai (X): “@cursor_ai's cli really isn't very good... so many things could be improved: - better steer/queue management, - bring in "compact" output feature from gui to tui. in an ideal world, i don't want to see really any of the tool calling at all. i'd like to see input ...thinking... output. - many other qol features, i need to start making a list as i go. recommendation: pretty much replace it with grok build cli.” [source](https://twitter.com/1603778112038264837/status/2101204729573601482)
- Complaint, 2026-09-18, @cursor_ai (X): “@cursor_ai i had to steer it manually! 😐🫠 <strict_link>” [source](https://twitter.com/1553011876811907072/status/2100748942371663961)
- Complaint, 2026-09-17, @cursor_ai (X): “@manlymarshall @cursor_ai @bot telling it to stop and still getting charged would pmo. this is why we have hard budget limits in merge gateway - the next request gets blocked” [source](https://twitter.com/2038722862786162689/status/2100592823171269095)

### OpenCode

- Praise, 2026-09-25, r/opencode (Reddit): “the separate backend means it's easy to connect to the same session from several clients. it's now possible to post a prompt and then cancel it before the model picks it up (seeing it becoming irrelevant from the cot) and the ui is much less laggy.” [source](https://www.reddit.com/r/opencode/comments/1wppj69/is_opencode_v2_officially_in_a_stable_release/pbxmjma/)
- Praise, 2026-09-18, r/opencodeCLI (Reddit): “it lets you ask a quick question without interrupting the current session 🔥” [source](https://www.reddit.com/r/opencodeCLI/comments/1wjixz4/new_btw_command_is_coming_in_the_new_version_of/)
- Praise, 2026-09-18, @opencode (X): “@opseclo @kaushikgopal @opencode shipping a skill instead of a plugin is such a clean move that steer vs queue detail is seriously useful” [source](https://twitter.com/1675906158304038912/status/2100867321975775684)
- Complaint, 2026-09-20, r/opencode (Reddit): “yeah bro i also find several features missing : 1. plan mode 2. queue messages and many more” [source](https://www.reddit.com/r/opencode/comments/1wlkq6c/windows_app_has_no_plan_mode/pazcvae/)
- Complaint, 2026-09-20, @opencode (X): “when are we getting the option to force send the next message instead of it getting stuck? or edit the same one? i can help you implement it at the end of the day, it's about saving us time 😅😅 @opencode @thdxr” [source](https://twitter.com/2089312053269864449/status/2101519232563286217)
- Complaint, 2026-09-17, @opencode (X): “@opseclo @kaushikgopal @opencode that's the boundary i want too. let the foreground tool finish, then pause before the agent's own final answer so i can inspect and steer. queueing is not control. recovery only counts if i can see the time and spend to get back on track.” [source](https://twitter.com/2074942490466033664/status/2100698112545247258)

### Devin

- Praise, 2026-09-21, @cognition (X): “@cognition ssh into the agent’s vm finally makes cloud agents feel native — real work happens where the code and terminal are. /handoff is the interesting primitive: bidirectional collaboration beats one-shot delegation for anything beyond toy tasks.” [source](https://twitter.com/2050639391991934976/status/2102141144796893432)
- Praise, 2026-09-21, @cognition (X): “@cognition cloud vm is table stakes. the sharp bit is ssh mid run plus /handoff. treat the agent's box as a shared workspace you can poke (ports, logs, fix), then give back. thats coworker ux, not chat and pray.” [source](https://twitter.com/1357553617935425536/status/2102153627439673799)
- Praise, 2026-09-11, @cognition (X): “@zicojzc @agoraio @tegnike @openai @cognition turned devin into something you can actually talk to — interrupt, redirect, and keep the work moving by voice. <strict_link>” [source](https://twitter.com/1846589514510462976/status/2098270880728228073)
- Complaint, 2026-09-18, @cognition (X): “@devindesktop @cognition @russelljkaplan can you please add steering for sessions, in addition to queueing messages, allow us to choose the default for new messages during an active session. currently, it queues by default, and the only other option is interupt, which terminates all subagents working, when 99% of the time, users want to steer the session, and not interupt. if we wanted to interupt, we would hit the stop button.” [source](https://twitter.com/43418580/status/2101040791330369835)
- Complaint, 2026-09-03, @DevinAI (X): “@santtiagom_ @devinai i prefer to be interrupted with two options rather than finishing a milestone on a decision i never made. that's where the time savings can completely go away.” [source](https://twitter.com/65982082/status/2095496059044667745)
- Complaint, 2026-09-01, @cognition (X): “@cognition steering in devin cli needed <strict_link>” [source](https://twitter.com/1617493632025776131/status/2094841693506048183)

### Pi

- Praise, 2026-09-20, @pidotdev (X): “@pidotdev the sleeper in this list is mid-conversation system messages. dynamic tools get the headlines, but re-issuing instructions mid-run is what keeps long agent runs steerable when the plan changes.” [source](https://twitter.com/1776789774919229440/status/2101577136918384841)
- Praise, 2026-09-20, @pidotdev (X): “@pidotdev mid-conversation messages are the unlock” [source](https://twitter.com/1513567206352764929/status/2101579172220981552)
- Praise, 2026-09-11, @pidotdev (X): “@ryanteoyx @pidotdev 100%. the harness is the product surface. in our locked harness test, the same task was $0.43 vs $0.88 and 149k vs 439k tokens. steering mid-run is the point.” [source](https://twitter.com/2074942490466033664/status/2098431008878051435)
- Complaint, 2026-09-23, @pidotdev (X): “@pidotdev steering is broken. multiple messages are sent one by one - they should be sent as one body. option+up aborts the agent, it should only bring the queued steering text back into editor. only esc should abort, and when text is queued, it should only interrupt the model and auto-submit the text.” [source](https://twitter.com/15266830/status/2102579401221099934)
- Complaint, 2026-09-10, r/PiCodingAgent (Reddit): “many models (namely qwens 3.8) think a lot, and i find myself wanting to interrupt it to answer a question it's been asking itself, quite repetitively, during it's reasoning. i can `esc` and send a prompt, but then pi would restart the whole reasoning tg from the beginning. i'd like to *inject* (for lack of better word) info to its thought block. i may also `steer` it by queuing a message, but that means i'd need to watch it going in loops for 20” [source](https://www.reddit.com/r/PiCodingAgent/comments/1wcwsya/noob_question_how_to_interrupt_an_agent_during/)

### Cline

- Praise, 2026-09-06, @cline (X): “@cline @openai mid-turn steering over websocket means you can course-correct a live response. useful when a long tool loop starts drifting, not for one-shot prompts.” [source](https://twitter.com/1110468810589593600/status/2096514959119155709)
- Complaint, 2026-09-23, @cline (X): “@cline when i do a steering message, i got this error in windows (latest cline version) , but the task dont stop it continue, and the red message keeps appearing; error 👇” [source](https://twitter.com/1760047654027796481/status/2102823548062421417)

### Amp

- Complaint, 2026-09-12, @AmpCode (X): “@sqs @ampcode @thorstenball if i run into the same thing i’ll report it. but it was like: i sent a message to do something and shortly after sent another message to do something else (unrelated to the former). i think it was with such short time in between that it just interrupted the first and forgot it” [source](https://twitter.com/872962356/status/2098703694615261199)
- Complaint, 2026-09-04, @AmpCode (X): “i think the thing with "orbs" right now is the marketing makes a big deal about it, but that noun is nowhere to be found in the actual app experience, except for the selector when creating a thread (which i don't even use, i have puck create all my threads). the first thing you see in onboarding is "setup your app for orbs" to modify your repo, for a thing you don't even understand yet. maybe the vision is for an orb to go beyond "one computer pe” [source](https://twitter.com/109443773/status/2095682609703706997)

### GitHub Copilot

- Praise, 2026-09-10, @GitHubCopilot (X): “finally gave a serious try to @opencode for personal project and suddenly missed the following ( compared to @githubcopilot cli ) message steering, branch /diff ( from main even after pushing ), /btw , ctrl+c protection, plan however still impressed with tui, free zen models” [source](https://twitter.com/15468471/status/2098084461204390142)

### Factory

- Praise, 2026-09-07, @FactoryAI (X): “okay, these /missions outputs from @factoryai prior to kicking off the build are exactly what i want. product and architecture choices - including reiterating trade-offs we discussed together, clear mile-stoning (w/ a change to interject/steer differently), straightforward structure. the one thing i changed for self: asked it to generate as html to review in browser - i like the formatting/layout options there, and memorializing this initial deci” [source](https://twitter.com/1449604717038825477/status/2097107494833422793)

### Kiro

- Complaint, 2026-09-16, r/kiroIDE (Reddit): “i had a runaway agent once. it took all tasks, went into the background and continued for a couple of hours. no stopping of the thing. it survived prompts, commands, sessions and restarts. 100+ tokens on haiku and ~30 tasks later it happily reported in a newly opened session that it finished. micro-skynet experience. good it was a small private project.” [source](https://www.reddit.com/r/kiroIDE/comments/1whrobc/in_less_than_30_secs_kiro_uses_almost_100_credits/pa4s07y/)