About aio-ade-cli
aio-ade-cli is a skill that guides agents in using the AIO-ADE CLI when the app's managed worktrees, terminals, automations, or embedded browser are authoritative. It directs users to load a version-matched command guide from the selected binary rather than relying on stale command details.
Key features
- 01Resolve the CLI executable for a session
- 02Load the binary-matched CLI guide
- 03Manage AIO-ADE worktree and terminal tasks
- 04Use JSON output for agent-driven calls
- 05Bounded fallback for older binaries
Use cases
- 01Working with AIO-ADE-managed worktrees
- 02Reading or controlling AIO-ADE terminals
- 03Handing work to another agent
- 04Controlling the app's embedded browser
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ keepmeside/ aio-ade-platform --skill aio-ade-cliAfter installing, type/aio-ade-cliin Claude Code to confirm it loaded.
Details
From the project READMEAIO-ADE CLI
This file is a discovery stub, not the usage guide. The full, version-matched AIO-ADE CLI
reference is served by the aio-ade binary itself — kept out of this file on purpose so it
can never drift from the binary that will actually run your commands.
Engage AIO-ADE whenever its running editor/runtime is the source of truth: AIO-ADE-managed worktrees, folder contexts, terminals, repos, automations, worktree comments, and the browser embedded inside the AIO-ADE app. Triggers include "$aio-ade-cli", "AIO-ADE worktree", "child worktree", "spawn codex/claude in a worktree", "read/wait/send AIO-ADE terminal", "full handoff" / "handover" / "give this to another agent", and "control the browser inside AIO-ADE". Use plain shell tools when AIO-ADE state does not matter.
Resolve the CLI for this session
Choose the executable once and reuse it for every later command:
- If the
AIO_ADE_CLI_COMMANDenvironment variable is set, use its value. AIO-ADE exports this for managed WSL sessions. - Otherwise, in a dev checkout whose session exposes
AIO_ADE_DEV_REPO_ROOT, useaio-ade-dev. - Otherwise, use
aio-ade. It is the same name on every platform: the pre-rebrand CLI needed a separate Linux name because a bareorcacollided with the GNOME Orca screen reader (/usr/bin/orca), andaio-adedoes not. - Otherwise, use
aio-ade.
Below, AIO_ADE is a placeholder for the executable you resolved. Substitute it before
running anything; do not create a shell variable or run AIO_ADE 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 AIO-ADE build.
Load the full guide before running AIO-ADE commands
AIO_ADE skills get aio-ade-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 AIO-ADE releases, and this file deliberately no longer lists them. Confirm the
app is up with AIO_ADE status --json (start it with AIO_ADE open --json if needed), and
prefer --json for agent-driven calls.
If an older AIO-ADE 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:
AIO_ADE status --json
AIO_ADE worktree ps --json
AIO_ADE terminal list --json
Then tell the user that updating AIO-ADE restores the full, version-matched guide via
AIO_ADE skills get aio-ade-cli. Beyond these commands, ask the user rather than guessing a
command surface this older binary may not support.