Skip to content
Arashi logoArashi

Kitty

Requirements

Section titled “Requirements”
  • Kitty 0.43 or newer
  • the kitten executable
  • Kitty remote control

Choose the narrowest allow_remote_control and password policy that works. Arashi does not edit kitty.conf.

Verify access without printing Kitty’s process data:

Terminal window
kitten @ ls >/dev/null

Use Kitty

Section titled “Use Kitty”
Terminal window
aw switch feature-auth
aw create feature-auth --launch

Managed Kitty reuses the exact Arashi worktree identity while keeping a readable <repo-name>: <branch-name> label. It focuses and validates an existing tab before creating another.

Kitty is detected automatically after integrated IDE detection and before parent-shell cd. There is no --kitty flag, and Kitty is not added to persistent launch configuration.

In managed Kitty, --tab uses the exact worktree tab. See Launching.

Ownership

Section titled “Ownership”

Kitty sessions are live only. Arashi does not write .kitty-session files or restore tabs after Kitty exits.

aw remove does not close Kitty windows or sessions. Close stale Kitty windows manually.

If launch fails after create, created worktrees remain available. Kitty returns LAUNCH_FAILED and does not fall back to another launcher.

Troubleshoot

Section titled “Troubleshoot”
  • Confirm kitten --version reports Kitty 0.43 or newer.
  • Run kitten @ ls >/dev/null in the same window.
  • Check remote-control, socket, and password settings.
  • Close duplicate exact worktree windows manually.
  • For lock contention and recovery, see Kitty identity lock.
Section titled “Related”