Skip to main content

​
Session Commands

The genie command is the primary entry point. Running it from any folder creates or attaches a tmux session named after that folder.

​
genie

Start or attach to a Genie session for the current directory.
Architecture: Each folder gets its own tmux session. Running genie from ~/projects/myapp creates a session named myapp.
Terminal

​
Options

--reset kills the existing tmux session and drops any unsaved pane state. It does not touch the persistent Claude sessions stored in PostgreSQL, but in-flight agents will be terminated. Use genie stop <name> if you only want to pause an agent.

​
Session Naming

Sessions are named after basename(cwd). When multiple folders share the same basename, a 4-character hash is appended for disambiguation:
Terminal
The hash suffix is deterministic — running genie from the same path always yields the same session name, so reconnecting from a new terminal attaches to the original session rather than starting a second one.
Prefer short, lowercase session names (auth, docs, sprint12) with --session <name> when you want to share the session across teammates or scripts. Avoid spaces and special characters — tmux treats them as argument boundaries, which breaks genie send and tmux attach -t round-trips.

​
Session with Teams

When a team is active, the session integrates with Claude Code’s native team features:
Terminal

​
genie --version

Print the installed Genie version.
Terminal

​
See also

Team

Pin a team to a shared tmux session with --tmux-session.

Spawn & Lifecycle

Spawn agents into the current session.

Messaging

Send messages between agents running in the session.

Observability

Inspect Claude sessions stored in PostgreSQL.