manta-cli

Manta CLI

This file is a discovery stub, not the usage guide. The full, version-matched Manta CLI reference is served by the manta binary itself — kept out of this file on purpose so it can never drift from the binary that will actually run your commands.

Engage Manta whenever its running editor/runtime is the source of truth: Manta-managed worktrees, folder contexts, terminals, repos, automations, worktree comments, and the browser embedded inside the Manta app. Triggers include "$manta-cli", "Manta worktree", "child worktree", "spawn codex/claude in a worktree", "read/wait/send Manta terminal", "full handoff" / "handover" / "give this to another agent", and "control the browser inside Manta". Use plain shell tools when Manta state does not matter.

Resolve the CLI for this session

Choose the executable once and reuse it for every later command:

• If the MANTA_CLI_COMMAND environment variable is set, use its value. Manta exports this

for managed WSL sessions.

• Otherwise, in a dev checkout whose session exposes MANTA_DEV_REPO_ROOT, use manta-dev.
• Otherwise, on Linux outside a Manta-managed terminal, use manta-ide. The Linux package installs the executable as manta-ide, so bare

manta is not on PATH outside Manta's terminals.

• Otherwise, use manta.

Below, MANTA is a placeholder for the executable you resolved. Substitute it before running anything; do not create a shell variable or run MANTA 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 Manta build.

Load the full guide before running Manta commands

MANTA skills get manta-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 Manta releases, and this file deliberately no longer lists them. Confirm the app is up with MANTA status --json (start it with MANTA open --json if needed), and prefer --json for agent-driven calls.

If an older Manta 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:

MANTA status --json
MANTA worktree ps --json
MANTA terminal list --json

Then tell the user that updating Manta restores the full, version-matched guide via MANTA skills get manta-cli. Beyond these commands, ask the user rather than guessing a command surface this older binary may not support.