Repository navigation
fix: prevent Claude prompts from getting stranded before Enter - #532
Merged
Merged
Conversation
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.
What changed
prompt + CRatomic PTY write;Why
Claude Code 2.1.209 can leave text visibly inserted in a long-lived PTY composer while swallowing the Enter coalesced into the same write. Paste journals showed repeated 20-second acceptance timeouts after
prompt-and-enter-written, with the prompt still editable on screen.Fresh PTY probes confirmed CR/LF remain valid key bytes, including while busy. The broken invariant was relying on an atomic text+Enter write without first proving that Claude had processed the text.
Verification
Closes #531