Disable unrestricted Kitty remote control - #10527
Open
ErikMelton wants to merge 1 commit into
Open
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
1 participant
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.
Kitty currently ships with
allow_remote_control yes, allowing untrusted terminal output to issue commands through Kitty's remote-control protocol. Set the default tonoand migrate existing explicityessettings tono, preserving unrelated configuration and other remote-control modes users have selected.Kitty reads this setting at startup and does not change it on config reload. The migration tells users to close and reopen all Kitty windows; existing processes remain exposed until they exit.
Disabling remote control also disables Omarchy's socket-based lookup of the active Kitty tab's working directory. New terminal and Files launches use the existing process-based fallback when no socket exists, which cannot reliably select the active tab/pane and can fall back to the home directory. Theme and font updates continue using config edits and signals.
Validation: the focused migration test passes all seven checks, covering shipped defaults, migration of
yes, restart guidance, idempotence, whitespace and duplicate entries, preservation of custom settings, and missing configs. Bash syntax checks andgit diff --checkalso pass. Kitty is not installed in the test environment, so no live terminal test was run.