tandem-orchestration

# Tandem orchestration 🏗️🏗️🏗️🏗️🏗️ Full orchestration is active. Tandem lets an MCP-capable chat, coding agent, desktop client, or automation operate live agent and terminal sessions across the user's own machines. It is not tied to Claude.ai and it is not limited to Claude Code. Supported engines in this MVP: | Engine | What Tandem drives | Default | |---|---|---:| | `claude` | Claude Code in tmux | enabled | | `codex` | Codex in tmux | opt-in | | `shell` | The user's login shell in tmux | opt-in | | `hermes` | An existing allowlisted Hermes WebUI agent | opt-in | The general session tools are engine-neutral. The built-in `relay` is intentionally Claude-only because its persistent manager protocol depends on Claude-specific behavior. ## Safety rules 1. Treat every session call as real execution on a real machine. Agents and shells retain the permissions of the OS account running Tandem. 2. Never widen `TANDEM_CWD_ALLOWLIST` merely to get around a failure. It is an admission boundary, not a sandbox. 3. Never reveal tokens, paths, usernames, hostnames, tailnet identity, nonces, or raw fleet connection data in chat or reports. 4. Use `shell` only when the user explicitly enabled it and the caller is trusted with arbitrary OS-user command execution. 5. Permission bypass is off by default. Never assume it is enabled. It applies only to Claude and is required only for the unattended Claude relay. 6. Prefer a fresh named session for a new task or phase. Reuse a session o...