Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remote controlling kitty error on MacOS #679

johnnypea opened this issue Jun 25, 2018 · 4 comments

Remote controlling kitty error on MacOS #679

johnnypea opened this issue Jun 25, 2018 · 4 comments


Copy link


I use the released .dmg version for Mac (0.11.1) with following settings.

--listen-on unix:/tmp/mykitty --single-instance


startup_session /Users/johnnypea/.config/kitty/default
allow_remote_control yes


# Set the window layout for the current tab
#layout tall

# Set the working directory for windows in the current tab
cd ~

#launch zsh
new_tab Development
cd ~/Development
launch zsh

#launch Docker monitor
new_tab Docker
title Dry
launch /usr/local/bin/dry


alias k='/Applications/ @ --to unix:/tmp/mykitty'

...and I encounter this error with every command...

λ › k new-window --title Output --keep-focus cat                                                                                                          ~
Traceback (most recent call last):
  File "Python/", line 280, in run_path
  File "Python/", line 85, in _run_code
  File "kitty/", line 96, in <module>
  File "kitty/", line 92, in main
  File "kitty/", line 21, in remote_control
  File "kitty/", line 159, in main
  File "kitty/", line 113, in do_io
  File "kitty/", line 60, in __exit__
OSError: [Errno 57] Socket is not connected

...but the command is executed in kitty.

k ls outputs nothing just the error.

What am I doing wrong?

How could I verify I'm running just the single instance? Should it be just one process?


Copy link

Likely some difference in socket semantics between macOS and linux. I've never tested the socket based remote control on macOS. Can I ask why you are using --listen-on and --to at all? They are only needed if you intend to control kitty from outside a kitty window, such as from another terminal or a cron job or similar.

As for checking if single instance works, yes there should be only a single kitty process, every invocation of kitty should just create new windows in the existing process.

Copy link

Thank you for your answer.

Regarding --listen-on and --to, I would like to control kitty from my Alfred workflows ( and map some actions to my custom keyboard shortcuts structure in Keyboard Maestro (

Copy link

Ah, OK. Well with my fix you should be fine.

Copy link

Cool, thank you ;).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

2 participants