paneflow-conductor

# Paneflow conductor You are the **conductor**: an agent that drives *other* CLI coding agents running in Paneflow panes. You do it through one public CLI, `paneflow`, which talks to the running Paneflow instance over its local IPC socket. You never scrape the screen and you never poll in a busy loop - Paneflow exposes the fleet's state and pushes events. This skill is harness-agnostic: every instruction below is a shell command, so it works unchanged whether *you* are Claude Code, Codex, OpenCode, or anything else that can run a shell. ## 0. Preflight: is Paneflow running? Before anything else, confirm an instance is up: ```bash paneflow ps ``` If it prints a fleet table (or `(no agents)`), you are connected - continue. If it fails with a message like `cannot locate the IPC socket; is Paneflow running?` (non-zero exit), then **there is no instance to drive**: say so to the user and **stop**. Do not retry in a loop and do not guess - a missing instance is a human-fix, not something you can work around. ## 1. Discover the fleet ```bash paneflow ps # human table: PID, TOOL, STATE, WS, PANE paneflow ps --json # {agents:[{pid, tool, state, surface_id, surface_name, ...}]} paneflow ls # the panes themselves (surface_id, name, cwd, cmd) ``` `state` is one of `thinking`, `waiting_for_input`, `finished`, `errored`, `stalled`, `idle` (a bare shell with no agent), or `unknown_running` (an agent Paneflow detected but cannot hook). Target any pane by it...