h0x CLI
This file is a discovery stub, not the usage guide. The full, version-matched h0x CLI
reference is served by the h0x binary itself — kept out of this file on purpose so it
can never drift from the binary that will actually run your commands.
Engage h0x-ADE whenever its running editor/runtime is the source of truth: h0x-ADE-managed
worktrees, folder contexts, terminals, repos, automations, worktree comments, and the
browser embedded inside the h0x-ADE app. Triggers include "$orca-cli", "h0x-ADE worktree",
"child worktree", "spawn codex/claude in a worktree", "read/wait/send h0x-ADE terminal",
"full handoff" / "handover" / "give this to another agent", and "control the browser
inside h0x-ADE". Use plain shell tools when h0x-ADE state does not matter.
Resolve the CLI for this session
Choose the executable once and reuse it for every later command:
- If the
ORCA_CLI_COMMAND environment variable is set, use its value. h0x-ADE exports this
for managed WSL sessions.
- Otherwise, in a dev checkout whose session exposes
ORCA_DEV_REPO_ROOT, use h0x-dev.
- Otherwise, on Linux outside an h0x-ADE-managed terminal, use
h0x. Never run bare
orca there — outside Orca's terminals it normally resolves to the
GNOME Orca screen reader (/usr/bin/orca) and starts speech on the user's machine.
- Otherwise, use
orca.
Below, ORCA is a placeholder for the executable you resolved. Substitute it before
running anything; do not create a shell variable or run ORCA literally. This works the
same way in POSIX shells, PowerShell, and cmd.exe.
If the selected executable cannot run, report its exact error and stop. Do not fall through
to another executable, which could silently target a different h0x-ADE build.
Load the full guide before running h0x commands
ORCA skills get orca-cli
That prints the complete, version-matched guide for the exact binary that will handle your
next commands — worktrees, handoffs, terminals, automations, and the built-in browser.
Read it first, then run the specific command you need.
Don't guess subcommands or flags from memory or from a cached copy of this stub. They
change between h0x-ADE releases, and this file deliberately no longer lists them. Confirm the
app is up with ORCA status --json (start it with ORCA open --json if needed), and
prefer --json for agent-driven calls.
If an older Orca does not recognize skills get
Use this fallback only when the selected binary explicitly reports that skills get is an
unknown command. Another failure is not proof of an older binary; report it rather than
guessing or changing executables. For a confirmed pre-guide binary, use only this bounded,
read-only bootstrap to orient. Do not dead-end and do not invent commands:
ORCA status --json
ORCA worktree ps --json
ORCA terminal list --json
Then tell the user that updating h0x-ADE restores the full, version-matched guide via
ORCA skills get orca-cli. Beyond these commands, ask the user rather than guessing a
command surface this older binary may not support.
1---2name: orca-cli3description: Use the `h0x` CLI to operate h0x-ADE-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and h0x-ADE's embedded browser. Use when the user says "$orca-cli", "use h0x cli", "h0x-ADE worktree", "child worktree", "cardStatus", "spawn codex/claude in a worktree", "read/wait/send h0x-ADE terminal", "terminal send", "full handoff", "handover", "give this to another agent", "another worktree", "h0x-ADE browser", "h0x artifacts", "share HTML/Markdown", "public artifact link", "share skills", or "control the browser inside h0x-ADE". Prefer this over raw `git worktree`, ad hoc PTYs, Playwright, or Computer Use when the task touches h0x-ADE-managed state. Use Computer Use for external browser windows, webviews, or desktop UI only when the task requires OS/window-level control such as focus, menus, dialogs, coordinates, or screenshots. Use `orca-cli` for h0x-ADE's embedded pages and a page-automation tool such as Playwright or CDP for external pages.4---5
6# h0x CLI
7
8This file is a discovery stub, not the usage guide. The full, version-matched h0x CLI
9reference is served by the `h0x` binary itself — kept out of this file on purpose so it
10can never drift from the binary that will actually run your commands.
11
12Engage h0x-ADE whenever its running editor/runtime is the source of truth: h0x-ADE-managed
13worktrees, folder contexts, terminals, repos, automations, worktree comments, and the
14browser embedded inside the h0x-ADE app. Triggers include "$orca-cli", "h0x-ADE worktree",
15"child worktree", "spawn codex/claude in a worktree", "read/wait/send h0x-ADE terminal",
16"full handoff" / "handover" / "give this to another agent", and "control the browser
17inside h0x-ADE". Use plain shell tools when h0x-ADE state does not matter.
18
19## Resolve the CLI for this session
20
21Choose the executable once and reuse it for every later command:
22
23- If the `ORCA_CLI_COMMAND` environment variable is set, use its value. h0x-ADE exports this
24 for managed WSL sessions.
25- Otherwise, in a dev checkout whose session exposes `ORCA_DEV_REPO_ROOT`, use `h0x-dev`.
26- Otherwise, on Linux outside an h0x-ADE-managed terminal, use `h0x`. Never run bare
27 `orca` there — outside Orca's terminals it normally resolves to the
28 GNOME Orca screen reader (`/usr/bin/orca`) and starts speech on the user's machine.
29- Otherwise, use `orca`.
30
31Below, `ORCA` is a placeholder for the executable you resolved. Substitute it before
32running anything; do not create a shell variable or run `ORCA` literally. This works the
33same way in POSIX shells, PowerShell, and cmd.exe.
34
35If the selected executable cannot run, report its exact error and stop. Do not fall through
36to another executable, which could silently target a different h0x-ADE build.
37
38## Load the full guide before running h0x commands
39
40```text
41ORCA skills get orca-cli
42```
43
44That prints the complete, version-matched guide for the exact binary that will handle your
45next commands — worktrees, handoffs, terminals, automations, and the built-in browser.
46Read it first, then run the specific command you need.
47
48Don't guess subcommands or flags from memory or from a cached copy of this stub. They
49change between h0x-ADE releases, and this file deliberately no longer lists them. Confirm the
50app is up with `ORCA status --json` (start it with `ORCA open --json` if needed), and
51prefer `--json` for agent-driven calls.
52
53## If an older Orca does not recognize `skills get`
54
55Use this fallback only when the selected binary explicitly reports that `skills get` is an
56unknown command. Another failure is not proof of an older binary; report it rather than
57guessing or changing executables. For a confirmed pre-guide binary, use only this bounded,
58read-only bootstrap to orient. Do not dead-end and do not invent commands:
59
60```text
61ORCA status --json
62ORCA worktree ps --json
63ORCA terminal list --json
64```
65
66Then tell the user that updating h0x-ADE restores the full, version-matched guide via
67`ORCA skills get orca-cli`. Beyond these commands, ask the user rather than guessing a
68command surface this older binary may not support.
aiskillstore