overseerlisted

Read or drive ANOTHER live agent process from outside it — a running Claude Code or Codex session, or a plain shell — in a local or remote Linux tmux pane, or in a console window on a remote WINDOWS machine over SSH. Use when the user wants to see the latest conversation of a claude or codex they are watching, send a message / reply on their behalf to it, run a command turn-based in a shell they are watching, list which tmux panes are running what agent, create or tear down a Linux tmux session running a shell/claude/codex (start/stop), or start/drive/stop a claude, codex or pwsh on a Windows PC's visible desktop (win <host> start/chat/sh/read/stop). read/chat/send/wait/list auto-detect the harness (Claude Code or Codex). Overseer itself runs on a Linux controller; its targets are Linux tmux panes (local or over ssh) and remote native Windows console brokers. Local pane discovery is Linux + tmux only; a plain non-tmux Linux terminal cannot be driven.
saigonbaddielover/sgbl-overseer · ★ 2 · AI & Automation · score 69

Install: claude install-skill saigonbaddielover/sgbl-overseer

# overseer — read and drive a live tmux pane (Claude Code, Codex, or a plain shell) A running agent TUI (Claude Code, Codex) cannot be talked to programmatically — the only input channel is the keyboard. This skill wraps a deterministic, self-verifying `tmux send-keys` / `capture-pane` procedure plus transcript reading, so you can read and drive another agent session — or run commands turn-based in a plain shell — that the user is watching in a tmux pane. It works the same whether the pane is on this box or displayed on the user's machine over VSCode Remote-SSH, because tmux is server-side here. **Harnesses.** `list`, `read`, `chat`, `send`, `wait`, `quit`, `slash`, `fleet` **auto-detect** whether a pane runs Claude Code or Codex and adapt (right transcript, right completion signal, right exit keys), so you use the same commands for both. `peek`, `keys`, `menu`, `sh`, `list --all` are harness-agnostic — in particular `menu` drives *any* pane by looking at what is highlighted on screen, which is why you pass it `Down` for a vertical Codex popup. Codex specifics you may need: **quitting** takes a single Ctrl-C (the script handles it); to **interrupt a running Codex turn** use `keys <t> Escape` — NOT Ctrl-C, which would quit Codex when it is idle; a Codex **approval prompt** is answered with a letter key via `keys` (`y` approve once, `a` approve for session, `d` deny). Support for more harnesses is added behind these same commands. All work goes through one bundled script: `