Claude Relay
VerifiedRelay operator for Claude Code via tmux across multiple projects. Use when the user wants to start/continue a Claude Code terminal session, send prompts, rea...
$ Add to .claude/skills/ About This Skill
# 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.
```bash scripts/relay.sh <action> [project] [args...] ```
Actions: `start`, `send`, `tail`, `stop`, `status`, `session`
Workflow
- Start session: `scripts/relay.sh start <project>`
- Send instruction: `scripts/relay.sh send <project> "<text>"`
- Read output: `scripts/relay.sh tail <project> [lines]`
- Repeat send/tail as needed.
- Stop when done: `scripts/relay.sh stop <project>`
Project resolution
The script resolves `<project>` in order:
- Absolute path (if directory exists)
- Alias from `projects.map` (`name=/abs/path`)
- `$CLAUDE_RELAY_ROOT/<name>` exact match
- Find under `$CLAUDE_RELAY_ROOT` (maxdepth=2) by folder name
- If omitted, re-use last project
Multiple matches → script exits with candidates; ask user to clarify.
Session naming
Deterministic: `cc_<basename_sanitized>`. 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
| Variable | Default | Description | |----------|---------|-------------| | `CLAUDE_RELAY_ROOT` | `$HOME/projects` | Root directory for project discovery | | `CLAUDE_RELAY_MAP` | `<skill-dir>/projects.map` | Path to project alias map file | | `CLAUDE_BIN` | `claude` (from PATH) | Path to Claude Code CLI binary | | `RELAY_WAIT` | `6` | Seconds to wait after send before tailing output |
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.
Use Cases
- Run Claude Code as a persistent terminal copilot across multiple projects via tmux
- Send prompts to a background Claude session and tail output without blocking the terminal
- Manage project aliases so teams can switch contexts with short names instead of paths
- Operate multiple parallel Claude sessions in different project worktrees
- Resume an interrupted Claude session without losing conversation context
Pros & Cons
Pros
- +Deterministic session naming prevents accidental session collisions
- +Project alias map allows quick switching between codebases
- +All actions go through a single relay.sh script with clear error codes
Cons
- -Requires tmux — not usable in environments without terminal multiplexer support
- -Transport-focused only — does not add reasoning or code intelligence capabilities
- -Only available on claude-code and openclaw platforms
FAQ
What does Claude Relay do?
What platforms support Claude Relay?
What are the use cases for Claude Relay?
100+ free AI tools
Writing, PDF, image, and developer tools — all in your browser.
Next Step
Use the skill detail page to evaluate fit and install steps. For a direct browser workflow, move into a focused tool route instead of staying in broader support surfaces.