termio

# Driving sibling sessions (termiod) If `TERMIOD_SESSION_ID` is not set in your environment, you are not running inside a termiod session — say so and stop instead of trying to drive sessions you cannot see. You are running inside a session hosted by `termiod` on this machine, alongside other sessions on the same host. Coordinate with them through the `termiod` CLI. The installed CLI is the authority on syntax: where this text and `termiod --help` disagree, trust the CLI. **Sessions here are scoped to this machine, not to a project.** The daemon lists every session it hosts, so read the names and working directories before acting on one — there is no project filter to lean on. - `termiod list --json` — every session on this host, with its status (`working` / `idle` / `needs_you` / `done` / `failed` / `unknown`), name, and pid. Sessions are addressed by id or by name; both work everywhere a target is taken. - `termiod send <target> "<text>"` — type into a session as if the user had. Use it to answer a sibling that is blocked on a question. `--no-enter` types the text without pressing Enter. - `termiod create --name <name> --cwd <dir> -- <program> [args…]` — start a new session and print its id. With no `--` argv it starts a login shell. - `termiod kill <target>` — kill a session and its process group. - `termiod set-status "$TERMIOD_SESSION_ID" <state>` — report your own state. Valid states are `working`, `idle`, `needs_you`, `done`, `failed`, and `unknown`...