maddada/ghostex/ghostex-cli

ghostex-cli

Use Ghostex's CLI help as the source of truth instead of relying on remembered command names or flags.

Core Workflow

1. Read the current command catalog:

``bash ghostex --help ``

1. Read focused help when the catalog points to it:

``bash ghostex automations --help ghostex quick-actions --help ghostex browser --help ghostex server --help ``

1. Inspect current state before choosing a target. Prefer JSON where offered:

``bash ghostex sessions --json ghostex state ``

1. Act on an exact project, session, group, automation, or run id. Prefer ids

from JSON output over titles, aliases, or whichever project is focused.

1. Re-read the relevant state or use the command's assertion/wait operation to

verify the requested result.

Routing

Everyday Ghostex work — sessions, orchestration, automations, quick actions, chat queues, prompt history, server, diagnostics — is covered by the CLI help above. Route to a specialized skill only when its domain applies:

• Use $ghostex-embedded-browser-use for browser panes inside Ghostex.
• Use $ghostex-browser-use for supported external browser page content.
• Use $ghostex-computer-use for native desktop application control.
• Use $ghostex-spaceo to drive Mac apps on SpaceO's hidden virtual displays,

out of the user's way.

• Use $ghostex-manage-beads for Project Board bead workflows through the

machine-installed bd CLI.

• Use $ghostex-agents when launching, messaging, reading,

and verifying other agents (start from ghostex agents --help), when reading or searching another session's thread, and when a session can't start or is stuck (ghostex accounts, ghostex agents switch-account, ghostex agents reload; releases newer than 10.23.0, so 10.24.0 or later).

• Use $ghostex-auto-rename-session when asked to generate a session title.
• Use $ghostex-move-codex-session to fork a Codex session into another

folder.

• Use $ghostex-help to explain how a Ghostex feature works or to change an

app setting for the user.

Keep using this skill's inspect, act, and verify loop alongside the specialized workflow.

Safety

• Do not guess a command, selector, flag, or JSON shape when current help can

provide it.

• Inspect exact targets before delete, kill, archive, replacement, or bulk

operations.

• Use --token-stdin for temporary remote tokens; do not put secrets in argv.
• Do not use raw zmx or tmux commands when Ghostex exposes the operation.
• Do not treat a successful process exit as verification when state can be

checked directly.