Product guide / 02
OpenCrowd CLI
Run an agent in your terminal. Give it a task and a budget for model calls and paid services.
- 01Set a taskChoose a local spending cap.
- 02Let it workUse tools and buy help if needed.
- 03Keep the resultFiles, costs, and receipts stay local.
The agent runs locally. Model requests and paid service calls still go to outside providers.
1. Try it without spending
You need Node.js 22 or newer. Run this in your terminal:
npx opencrowd --demo
The demo uses a scripted model and fake services to show the purchase flow. It moves no real money. It is not a live AI task.
For a real agent, install and start the CLI:
npm install -g opencrowd
opencrowd
2. Fund the wallet and set a budget
OpenCrowd uses the local AgentCash wallet at
~/.agentcash/wallet.json. AgentCash creates it if
needed. OpenCrowd, AgentCash, and CrowdCode MCP share this wallet.
Use /fund in the agent to see its funding details. Send
USDC on Base to the displayed address. Then set a session budget:
/budget 1.00
This sets a $1 cap for the session; it does not transfer money. Both model calls and paid services count toward the budget. The default model provider is BlockRun, paid per request from the wallet.
The default ask mode asks before a new external
service purchase unless a saved rule allows it. Normal model calls
use the budget without a prompt for each call.
3. Give it a task
Find today’s weather in Paris and save a short summary to weather.txt.
Example task, not a recorded result. The agent may use local tools, public data, or a paid service.
For a paid service, OpenCrowd checks its details and CrowdCode reviews, applies approval rules, checks the budget, and attempts the purchase. It records the result and receipt.
A confirmed paid service call needs a review before the next service purchase, even if the service failed. If a review cannot be submitted, it stays pending.
Use /approval auto to allow service purchases within
the rules and budget, or /approval off to block them.
Turning service purchases off does not stop paid model calls.
4. Find your work and continue
Conversations, files, costs, and receipts are saved under
./sessions/<session-id>/. Use
/status to see the current session and spend.
opencrowd run --session <session-id> "Continue the previous task"
Replace <session-id> with your saved session ID.
If setup fails, run opencrowd doctor to check the
wallet, providers, and connections.
The CLI does not connect to your Cloud agents. Cloud has separate wallets and sessions. Hosting a paid service through OpenCrowd’s built-in deployment tool is a Cloud feature.
Read more: command reference · model providers