AgentTab v2 is 2.0.0-rc.1 source and is not publicly published. The commands below describe the current agenttab CLI source. A command that starts with npx agenttab is a future public-package command and must not be treated as available today.
Commands intended to be copied contain no user-controlled paths, shell interpolation, token, or quoting. They have the same shape in POSIX shells, PowerShell, and cmd.exe. Uppercase values in the reference, such as PATH, are metavariables that must be supplied through the relevant client's configuration rather than copied as a command.
agenttab --help
agenttab --version
agenttab install [--version X.Y.Z] [--verify-readiness] [--development --manifest-url URL --signature-url URL]
agenttab status
agenttab doctor [--layer ipc|extension]
agenttab mcp
agenttab proxy --token-file PATH [--port 9224]
There is no agenttab uninstall, no Standard-mode --port, no Standard-mode token command, no Python-host command, and no legacy task or lease command.
The CLI rejects unknown commands, unknown or duplicate options, missing option values, and positional arguments after a command. Boolean options do not accept values: use --dry-run to enable a dry run and omit it otherwise. In particular, --dry-run false and --dry-run=false are errors rather than real-install requests.
The intended post-launch install command is:
npx agenttab install
It is not usable until the package and signed release artifacts are public. The installer always resolves an exact version rather than latest, verifies the signed artifact manifest, requires the matching immutable vX.Y.Z asset, verifies the asset hash and platform signature, installs transactionally, writes an install receipt, registers dev.agenttab.host, and plans supported local client configuration updates. See Setup for current source, prerelease, and future stable state.
| Option | Current behavior |
|---|---|
--version X.Y.Z |
Selects the exact semantic version. The default is the CLI package version, currently 2.0.0-rc.1. Prerelease suffixes are accepted. |
--development |
Enables an approved development-artifact flow. It is required for file: artifact URLs and for an explicit public key. It does not turn an arbitrary local build into a supported install. |
--manifest-url URL |
Overrides the exact versioned artifact-manifest URL. Non-development URLs must use HTTPS and cannot be a latest URL. |
--signature-url URL |
Overrides the manifest signature URL. Without it, the CLI uses the manifest URL plus .sig. |
--public-key PATH |
Reads the manifest verification key from a local file. This is accepted only with --development. |
--state-dir PATH |
Overrides the installer staging, version, receipt, extension, and wrapper directory. This is distinct from the Rust host default on Windows. |
--home PATH |
Overrides the home root used to locate per-user browser registration and supported client configuration files. |
--dry-run |
Renders the proposed transaction and returns a planned extension state without applying the file transaction. |
--verify-readiness |
After installation, connects through the local IPC path, creates a disposable background task tab, captures an accessibility snapshot, and closes the tab. |
--no-open-browser |
With readiness verification, prevents the installer from launching Chrome before it waits for IPC. |
The CLI prints a semantic diff before changing files, skips malformed supported client configuration instead of mutating it, backs up prior changed files, and rolls back touched files if the multi-file transaction fails. It does not silently enable a browser extension. When an extension must be loaded manually, the result includes its directory and instructions.
The current source contains the stable Ed25519 verification public key, but no matching signed release artifacts or public package have been verified or published. Therefore the default command cannot complete a live installation yet.
agenttab status
Connects to local AgentTab IPC and prints the Core agenttab.status result as JSON. The status response reports the host lifecycle state, protocol version, and the current connection's task identifier when one exists.
Use this only after the extension and native host are installed. It does not start a browser, create a task, use a port, or authenticate with a token.
agenttab doctor --layer ipc
agenttab doctor --layer extension
--layer accepts only ipc or extension; it defaults to ipc. The command runs the same status request and prints JSON. On failure, it returns a layer-specific recovery message:
ipc: open Chrome with AgentTab enabled, then rerunagenttab doctor --layer ipc.extension: reload AgentTab inchrome://extensions, then rerunagenttab doctor --layer extension.
The extension layer is a diagnostic label around the status check. It does not reload Chrome for you.
agenttab mcp
Starts the AgentTab MCP server over stdin and stdout. It accepts no CLI options. The packaged agenttab-mcp binary starts the same server and also accepts no CLI options. Both expose ten Standard tools by default, including browser_profile for the Chrome profile's bookmarks, history, sessions, and downloads (see Profile operations). Use the configured agenttab wrapper after a local installation, or the agenttab-mcp package binary only after that package is published.
The installer writes supported MCP client entries as an absolute local AgentTab wrapper plus mcp. For a manual configuration, use agenttab mcp only when that wrapper is on the client's PATH. The exact stdio configuration and protocol behavior are in MCP.
| Variable | Current adapter behavior |
|---|---|
AGENTTAB_DEVELOPER=1 |
Adds browser_developer to MCP and OMP discovery. The extension still rejects it unless the user has enabled persistent Developer mode in the AgentTab popup. |
AGENTTAB_CONVERSATION_ID |
Overrides the durable resume-capability scope. OMP and Pi otherwise use their stable harness session ID automatically; stdio MCP can use this variable when its client has a stable conversation scope across process restarts. It is metadata, not authorization. |
AGENTTAB_STATE_DIR |
Overrides the adapter capability-store root and the Unix socket fallback. The Rust host also honors it as its state root. |
AGENTTAB_SOCKET |
Overrides the local endpoint used by an adapter. |
AGENTTAB_PIPE_NAME |
Overrides the local Windows named-pipe endpoint used by an adapter. |
OMP_AGENT_HOME |
Selects the OMP config root that the installer checks for config.yml. |
Endpoint overrides are for a configured local runtime. They do not enable remote access and should not be used to recreate a Standard-mode TCP setup.
agenttab proxy --token-file PATH [--port 9224]
This is the only TCP listener in the CLI, and it is deliberately outside normal AgentTab setup. It binds loopback only, defaulting to 127.0.0.1:9224; --port 0 requests an ephemeral loopback port. It requires --token-file and reads a token of 32 to 1024 characters. On Unix the file must be a current-user regular file with mode 0600.
The proxy speaks its own agenttab.proxy/1 authentication frame before forwarding bytes to local AgentTab IPC. It is not an MCP transport, is not used by Standard mode, cannot bind an external interface, and must not be presented as a replacement for the OS-native IPC boundary.
When present and structurally valid, the installer adds mcpServers.agenttab with the local AgentTab wrapper and mcp argument to these per-user configurations:
- Claude Desktop
- Cursor
- Windsurf
- a standard
~/.config/mcp/mcp.jsonfile - OMP
config.yml, as the local AgentTab OMP extension path
Malformed JSON or YAML is reported and left untouched. The installer does not install a global MCP server, create a registry token, or take ownership of unrelated client entries.