Repository navigation
refactor(claude-tty): drop the steer fallback now that Paseo 0.12 replaces the turn itself - #161
Merged
Merged
Conversation
sleeyax
force-pushed
the
refactor/claude-tty-drop-steer-fallback
branch
from
October 22, 2026 22:33
a5be96a to
aec3497
Compare
sleeyax
changed the base branch from
refactor/claude-tty-drop-cancelled-tool-call-repair
to
main
October 22, 2026 22:33
…laces the turn itself Without `prompt.steer`, a 0.11 daemon threw on a message sent mid-turn and lost it, so `withSteerFallback` offered the capability and declined every steer to make the daemon replace the turn. Since Paseo 0.12.0, `PluginAgentSession.steerActiveTurn` returns `unavailable` when the connection never negotiated `prompt.steer`, and the daemon interrupts the turn and sends the message as the next one (getpaseo/paseo#7270). That is the behaviour the wrapper faked, so it goes, along with its `CLAUDE.md` trap. Refs #155 Co-Authored-By: Claude Opus 5.5 <[email protected]>
sleeyax
force-pushed
the
refactor/claude-tty-drop-steer-fallback
branch
from
October 22, 2026 22:34
aec3497 to
4f8359f
Compare
This was referenced Oct 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Part 2 of #155.
Builds on #160, which made the Paseo 0.12.0 bump.
On 0.11, a mid-turn message to a session without
prompt.steerthrew and was lost, so the wrapper offered the capability and declined every steer.Since 0.12.0,
PluginAgentSession.steerActiveTurnreturnsunavailablewhenprompt.steerwas never negotiated (getpaseo/paseo#7270).The daemon then interrupts the turn and sends the message as the next one, which is what the wrapper faked.
The
steering.test.tscanary, "the bridge on its own refuses a steer", would have stayed green, since the fix is in the daemon and not the bridge.Evidence
withSteerFallbackofferedprompt.steerand declined every steer.After: live, on a
claude-tty-devcopy on a 0.12.0 daemon with the wrapper gone:paseo send --behavior steerduring a running shell call cancelled the call. The message ran as the next turn and was answered, with no "does not support prompt.steer" error.Merge Danger
Door: two-way
Blast Radius: claude-tty mid-turn messages
The plugin already requires 0.12.0 from #160, so no daemon that would lose the message can load it.
Steering into the running turn instead of replacing it stays out of scope (#36, #111).