dispatch

Spawn, list, resume, and kill Claude or Codex sessions in tmux windows.

1|Updated Oct 25, 2020
One-click install
npx skills add https://github.com/bfairkun/dotfiles --skill dispatch-bfairkun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dispatch
Source: https://github.com/bfairkun/dotfiles/tree/main/agents/.agents/skills/dispatch
Command: npx skills add https://github.com/bfairkun/dotfiles --skill dispatch-bfairkun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing multiple concurrent Claude or Codex sessions across project directories is tedious and error-prone when done by hand in tmux. This Skill automates creating two-pane tmux windows, launching sessions with tracked session IDs, resuming existing conversations, and switching between personal and enterprise Claude accounts. ## Core Features & Use Cases - Session Spawning: Creates a tmux window in a project directory, splits it into a shell pane and an agent pane, and launches Claude or Codex with a generated session UUID tagged on the window. - Session Discovery & Resume: Lists existing Claude sessions for a project via list-sessions.sh, then resumes a chosen session into a new or existing window. - Account Management: Tracks personal vs. enterprise Claude accounts per window using tmux window options, supports a work-mode default file, and switches accounts in place with switch-account.sh. - Use Case: You ask to open Claude in your RNA-seq analysis project; the Skill lists prior sessions for that directory, creates a named tmux window, launches Claude in the bottom pane, and shows you the captured output. ## Quick Start Ask the assistant to open a new Claude session in a specific project directory, for example by saying to start Claude in /project2/yangili1/bjf79/202503_bo_rnaseq.

Frequently Asked Questions about dispatch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I open a Claude session in a tmux window for a project?▼

List existing sessions for the project directory first, then create a named tmux window with new-window, split it vertically, and launch claude in the bottom pane with a generated session UUID. Tag the window with the session ID and account for later resuming.

How do I resume an existing Claude session in tmux?▼

Run list-sessions.sh with the project path to show prior sessions sorted newest-first, pick one, then launch claude -r with that session ID in the window's bottom pane. If the window already exists with a live session, the Skill reports that instead of duplicating it.

Can I switch a tmux Claude session between personal and enterprise accounts?▼

Yes, switch-account.sh kills the claude process gracefully and relaunches it with claude --resume under the target CLAUDE_CONFIG_DIR. History is preserved because both config dirs share a symlinked projects tree; only credentials differ.

Why does tmux send-keys target the wrong window by name?▼

tmux parses a bare window name as a session name, so targeting by name fails or hits the wrong window. Always use the integer window index from list-windows, and remember pane indices start at 1 in this environment.

What are the limitations of dispatching Codex versus Claude in tmux?▼

Codex sessions are stateless with no session resume, so only fresh launches are supported and no account tagging applies. Claude sessions support resume by ID, account switching, and attention markers in the tmux status bar.