[docs] Add troubleshooting for unauthorized messages in tmux (#61962)#61966
Open
giruuuuj wants to merge 1 commit into
Open
[docs] Add troubleshooting for unauthorized messages in tmux (#61962)#61966giruuuuj wants to merge 1 commit into
giruuuuj wants to merge 1 commit into
Conversation
This was referenced May 25, 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
Adds a troubleshooting entry for unauthorized phantom messages appearing in tmux sessions. Documents the likely root cause (tmux forwarding control sequences interpreted as keypresses) and workaround (disable focus-events or run outside tmux).
Closes #61962
Problem
In v2.1.150 on macOS with tmux, messages may appear to be sent on the user's behalf without their input. The TUI input reader interprets terminal control sequences (focus events, bracketed paste) forwarded by tmux as actual keypresses or text input.
Workaround
Run outside tmux to confirm the trigger. In tmux, disable focus events:
set -g focus-events offRelated