Agent setup
How ABX gives coding agents the right commands and guardrails.
The CLI works without an agent. The skill teaches agents the commands, risks, and approval points.
Install the matching skill
abx skill installThe skill version is stamped when the CLI ships. abx doctor warns when the installed copy no longer
matches. Run the install command again after each CLI upgrade.
When ABX reports a newer CLI, the agent recommends upgrading before planning a deployment or write. Updating local tooling does not change deployed projects, and the current release continues to support earlier canonical project generations unless one is explicitly quarantined.
The default install covers Claude Code, Cursor, Codex CLI, Gemini CLI, and GitHub Copilot. To limit the install, use one of these:
abx skill install --agent codex
abx skill install --agent cursor
abx skill install --globalRestart the agent after installation. If the current agent is a one-shot session and cannot restart,
run abx skill path and have it read the printed SKILL.md directly; the installed copy will be
discovered automatically by the next session.
Choose the signer deliberately
The agent checks the live ABX Services descriptor before asking you to set up a wallet. If the
network and transaction group qualify, it recommends --sponsor, especially on testnet.
You can bring your own signer. --sign opens a browser wallet. --send uses an environment key.
--unsigned prepares transactions for another signer. If the signer changes, run the dry run again.
See signing modes.
What the skill does not do
The skill does not choose your edition size, storage, royalties, or sale price. It asks, shows the plan, and waits for approval.