Set up an agent
One command makes a folder for one agent with its key, limits, skills and hooks. You approve it with your wallet.
Run the command
In a terminal, in the folder where your agents should live:
npx binference agent-os my-agentmy-agent becomes the folder's name and the agent's name in the cockpit. The command checks for Node.js 22 or newer and for Claude Code or Codex. With both installed, it asks which one runs this agent. On Windows, run it in WSL2.
| Option | What it does |
|---|---|
--app claude, codex | Picks the app up front |
--model <id> | The model it starts on. Any id on Models |
--yes | Installs Binance's wallet command line tool without asking |
--sandbox | Turns on Claude Code's sandbox, so shell commands can't touch the folder's limits |
--no-wait, then --resume | Shows the sign-in code and stops, to approve later; --resume finishes |
Codex needs version 0.140 or newer, the first with hooks. Run codex update if yours is older. Every option is in the CLI reference.
Approve it with your wallet
Your browser opens binference.io with a code. Check that it matches the code in your terminal, sign in with your wallet, then choose:
- What pays for its AI: your account's credit, or the budget of an agent you launched.
- A spending limit for its key, per day, week or month. It starts on, at $5 a day.
Approve only a code you see in your own terminal right now. The terminal carries on by itself.
Let it finish
The command writes the folder and installs what the agent needs:
| What | Where |
|---|---|
| The agent's key | .binference/key, readable by your user only and ignored by git |
| House rules | AGENTS.md, which CLAUDE.md points to |
| Hooks | .binference/hooks, wired into .claude/settings.json or .codex/ |
| Skills | bInference, Binance Agentic Wallet and token audit |
Binance's wallet tool, baw | Installed with npm if you say yes |
Everything lives in the folder, except baw, which npm installs for your whole computer.
Connect Binance's MCP Server
For trading on the Binance exchange, run Binance's command in the folder, exactly as written:
claude mcp add binance-mcp-server --transport http https://agent.binance.com/mcp/agenticThen start the agent, open /mcp, pick binance-mcp-server and sign in to Binance.
Grant the fewest scopes you need. Binance asks people to run this themselves, so the command only prints it for you.
Start it
cd my-agent && ./startStart it this way every time. ./start points the app at bInference and hands it the key, for this launch only. npx binference start does the same, a little slower. Plain claude or codex would think with another model, and its AI spend would be missing from the cockpit.
The first time, Claude Code asks you to trust the folder. Codex asks you to trust it and to review its hooks once: they're in .binference/hooks.
Sign in the Agentic Wallet
For on-chain trading, say to the agent:
Sign in to Binance Agentic WalletThen lower the wallet's limits in the Binance App: Agentic Wallet → Settings. Binance suggests $50 a day to start. See Agentic Wallet.
What the agent knows
Each session starts with a status from the cockpit:
bInference cockpit for "my-agent" (https://binference.io/account/cockpit?id=12):
- AI budget: $41.20 to spend, about 6.5 days at the last day's pace. This key stops at $5.00 a day ($3.10 left).
- Trade limits: at most $50.00 a trade, $200.00 a day, the person confirms above $25.00. Hooks apply them before each trade.
- Agentic Wallet: signed in. Its sign-in ends in about 2 h and Binance signs it out silently: tell the person now.
- If a hook blocks an action, tell the person the reason. Never retry it another way or split it.When you pause the agent, the status says so, and it won't trade or start long work. The house rules in AGENTS.md tell it to:
- restate each trade in one line and wait for your yes, with a quote first
- audit a token before its first buy, and never buy a honeypot or a token with a sell tax above 10%
- never try another way when a limit blocks a trade
- check the AI budget before long work
- check Binance at most once a minute while it waits for an order or a transfer
- after a rate limit from Binance (HTTP
429or418), stop calling Binance until the time it names, and tell you
Check it any time
In the folder:
npx binference doctorIt checks the app, the key and the cockpit, the AI budget, the hooks and whether the last session ran them, the skills, baw, the wallet's sign-in and Binance's MCP Server, and says what to fix. npx binference doctor --fix repairs what failed and keeps your own settings. Add --dry-run to see the changes first. After a new release, update the folder with npx binference@latest doctor --fix.