ghostex-agents

ghostex-agents

Ghostex lets one agent launch, message, read, and close other agent sessions through the ghostex CLI (gx is the same binary). The CLI help is the source of truth for every command, flag, and JSON shape. Read it before you act, and never rely on command shapes you remember from an earlier run.

Read the help first

ghostex agents --help   # who am I, which agents exist, create, list, send, read, close
ghostex --help          # full catalog: create-agent --model/--effort, wait-for-text,
                        # read-session-chat, select-session-chat-model, queues, sleep/wake

ghostex agents --help covers identity, recipients, the sender block other agents see (after the message body in current versions, before it in older ones), delivery modes (default, interrupt, queue), reading replies, and closing. ghostex --help lists the session-level verbs around it, including the one that starts an agent with a specific model and effort for that session only, and the one that changes model or effort on a session that already exists. If a verb in this skill is missing from the help on this machine, the installed Ghostex is older than the verb: tell the user to update instead of guessing a replacement.

A pasted Copy Details block

When the user pastes a block that starts with Ghostex Session (from the sidebar's Copy Details), it describes another session: its agent, title, Global Ref, Agent Session ID, zmx name, and the project and path it works in. Use the Global Ref for every send, read, wait, and close, and treat the path as that agent's working folder when you agree on file ownership. The block does not say whether the session is running or busy: check ghostex agents list --all --json before you send.

When the user wants one agent to run the work

When the user wants an agent that keeps handing work to other agents and reporting back ("be my lead on this", "run these as parallel threads and tell me when they are done"), a Ghostex orchestrator does that with supervision built in: Ghostex sends it each thread's final message and every question a thread is stuck on, so nothing has to poll. Start one with ghostex orchestrator create. Older Ghostex releases call it a coordinator and name the same verbs ghostex coordinator … (from 2026-09-30 on), so if ghostex orchestrator --help is missing, use ghostex coordinator instead; if both are missing, the installed Ghostex is older, so use the workflow below instead. If you are an orchestrator yourself, follow ghostex orchestrator guide (older releases: ghostex coordinator guide) rather than the waiting habits below. Name a thread after its task in 3 to 6 words. If you are a thread and your orchestrator's message starts a task your title does not describe, rename yourself first with ghostex orchestrator rename-self "<3 to 6 words>" (a release newer than 10.23.0, so 10.24.0 or later); if it says the user renamed you, keep that name. Rename a thread only that way: ghostex rename-command records the user's own rename, which then locks the name, and ghostex rename-session skips the user's-rename check. Run by an orchestrator, ghostex agents create also links the new session as one of its threads. When the user wants a separate session they chat to directly, add --standalone (not linked, no reports to the orchestrator), and use ghostex orchestrator unlink <thread-ref> to turn an existing thread into one (both need 10.24.0 or later).