Claude Relay

Operate Claude Code as a persistent terminal copilot through tmux.

Script

All actions go through scripts/relay.sh. Run with no args for usage help.

scripts/relay.sh <action> [project] [args...]

Actions: start, send, tail, stop, status, session

Workflow

• Start session: scripts/relay.sh start
• Send instruction: scripts/relay.sh send ""
• Read output: scripts/relay.sh tail [lines]
• Repeat send/tail as needed.
• Stop when done: scripts/relay.sh stop

Project resolution

The script resolves in order:

• Absolute path (if directory exists)
• Alias from projects.map (name=/abs/path)
• $CLAUDE_RELAY_ROOT/ exact match
• Find under $CLAUDE_RELAY_ROOT (maxdepth=2) by folder name
• If omitted, re-use last project

Session naming

Deterministic: cc_. One project = one tmux session.

Error handling

• tmux not installed: script exits with code 2 and "missing dependency" message.
• Claude binary not found: same exit code 2. Verify CLAUDE_BIN env or default path.
• Session not running (send/tail on stopped session): exits code 6. Start first.
• Project not found: exits code 4. Check projects.map or project path.
• Claude process hung: tail still works — check output. If stuck, stop and start fresh.

Environment variables

Setup

• Install this skill
• Create a projects.map file in the skill directory (see projects.map.example)
• Ensure tmux and claude are installed and in your PATH

Notes

• Transport-focused skill (relay/orchestration), not deep code reasoning.