ToolsXpo Code CLI

The CLI is the same agent as the extension, driven from a terminal. Same account, same models, same rules and skills.

Installing

Download the build for your platform and put its bin directory on your PATH:

Bash
toolsxpo --version

It is a single self-contained binary. No Node, no runtime to install.

Signing in

Bash
toolsxpo login

It prints a code and a URL. Open the URL anywhere — the CLI does not assume it can launch a browser, because it may be running over SSH, in a container, or in CI.

If you have already signed in from the extension, you are already signed in here. The credential lives in ~/.toolsxpo and every ToolsXpo app reads it. toolsxpo logout signs out everywhere.

Running a task

Bash
toolsxpo "add a --dry-run flag to the deploy script"

Quote the prompt as a single argument. Without quotes the shell splits it and the CLI cannot tell a prompt from a command.

Run toolsxpo with no arguments for the interactive interface.

Slash commands

The same ones as the editor:

Bash
toolsxpo "/review"
toolsxpo "/fix"
toolsxpo "/test the rate limiter"

Useful flags

Shared configuration

Rules, skills, hooks and MCP servers are shared with the editor. A rule you wrote for your project applies here without being copied.

Logs are not shared — the CLI writes to ~/.toolsxpo/cli/logs/, the extension to ~/.toolsxpo/vscode/logs/. Both can run at once without interleaving into one file.

Environment variables

TOOLSXPO_* is the namespace. The older CLINE_* names still work; where both are set, the branded one wins.

See also

• Signing in
• Slash commands