Run persistent multi-agent terminal workspaces with TUIOS
Use TUIOS to keep coding agents in persistent tiled terminal sessions, monitor their state, route Inbox items, and coordinate work across local or remote panes.
npx skills add agentskillexchange/skills --skill run-persistent-multi-agent-terminal-workspaces-with-tuios
Use TUIOS when an operator is running several CLI coding agents and needs a persistent terminal workspace that understands agent state. The workflow is concrete: create tiled sessions and workspaces, start Claude Code, Codex, Gemini CLI, opencode, or other agent CLIs in panes, watch which agents are working or waiting, answer approvals and questions from a shared Inbox, pass messages between agents, and resume or reconnect sessions after restarts. Invoke this instead of using the agent products normally when separate terminal windows or plain tmux panes have become hard to supervise, especially for multi-agent coding runs, remote sessions, or fan-out experiments. The scope boundary is terminal workspace, pane, session, Inbox, agent-state, and MCP control for local operator workflows; it is not a generic terminal emulator listing, a hosted agent platform, or a broad SDK.
What this skill actually does
Inputs and prerequisites: TUIOS CLI, supported terminal, one or more CLI coding agents such as Claude Code, Codex, Gemini CLI, or opencode; optional SSH, Tailscale, and MCP-compatible client.
Setup notes: Install with Homebrew using brew install tuios, Nix using nix run github:Gaurav-Gosain/tuios#tuios, Go using go install github.com/Gaurav-Gosain/tuios/cmd/tuios@latest, the upstream install script, or a GitHub release binary. Then run tuios integration install for supported agent harnesses and start or attach to a session before launching agent panes.
Source and verification boundary: use https://tuios.dev as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.