Driving sibling sessions (termio session)

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 termio session CLI. The installed CLI is the authority on syntax: where this text and termio session --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.

• termio session ls --all --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. A name two sessions share is refused as ambiguous, so give each session you create its own name, or use the id. On a Mac where the Termio app runs, send, read and close act on the app's sessions instead: there, take targets from termio session ls --json.
• termio session read <target> — print a session's screen.
• termio session 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.
• termio session create --name <name> --cwd <dir> -- <program> [args…] — start a new session and print its id. With no -- argv it starts a login shell.
• termio session close <target> — end a session and its process group.
• termio agent report <state> — report your own state. Valid states are working, attention (you need the user), done, and idle.

When to use this

• Delegating. A task that is genuinely separate work — a long build, an independent investigation — can go to a new session so the user watches it in its own pane.
• Supervising. Before reporting that something is done, check whether a sibling you started is still working or has gone needs_you.
• Unblocking. A sibling sitting at needs_you is waiting on a human. If you can answer it from what you already know, send the answer.

Do not spawn a session merely because two things could happen at once. A session the user did not ask for and does not watch is noise.

What is not available here

Unlike the same skill on a Mac running the termio app, there is no transcript reader and no project-scoped listing: termiod hosts sessions, and the project a session belongs to is not yet readable back from it. Do not guess at a sibling's conversation contents — ask it with send, or read what the user tells you.