Control the Kitty terminal emulator directly from Raycast via its remote control protocol.
Opens a new OS-level Kitty window. If Kitty is not running, it launches it automatically.
Opens a new tab in the currently active Kitty window. If Kitty is not running, it launches it automatically.
Browse all open tabs across every Kitty window and jump to any of them instantly.
⌘RDefine and launch multi-window, multi-tab, multi-pane Kitty sessions from YAML configurations stored in Raycast.
Configurations are written in YAML and support:
cwd) per tab or paneexec)Example configuration:
name: My Project
windows:
- tabs:
- title: Editor
layout:
cwd: ~/projects/myapp
commands:
- exec: nvim .
- title: Dev Server
layout:
cwd: ~/projects/myapp
commands:
- exec: npm run dev
- title: Logs
layout:
cwd: ~/projects/myapp
split_direction: vertical
panes:
- cwd: ~/projects/myapp
commands:
- exec: tail -f logs/app.log
- cwd: ~/projects/myapp
commands:
- exec: tail -f logs/error.log
Opens the folder currently shown in Finder in a new Kitty window, with its working directory set to that folder.
Most commands rely on Kitty's remote control socket. Add the following lines to your kitty.conf:
allow_remote_control socket-only
listen_on unix:/tmp/kitty-socket-{kitty_pid}
Then restart Kitty. The extension will auto-detect the socket, or you can set a custom path in the extension preferences.
The extension automatically detects the kitten binary by searching:
PATH (which kitten)/Applications/kitty.app/Contents/MacOS/kitten~/Applications/kitty.app/Contents/MacOS/kitten/opt/homebrew/bin/kitten (Homebrew on Apple Silicon)/usr/local/bin/kitten (Homebrew on Intel)If none of these match, you can set the path manually in the Kitten Path preference.
| Preference | Description |
|---|---|
| Socket Path | Path to the Kitty remote control socket. Leave empty to auto-detect /tmp/kitty-socket-{pid}. |
| Kitten Path | Path to the kitten binary. Leave empty to auto-detect from PATH and standard locations. |