feat: compute commands

[andrew-virtuals]

Note

Medium Risk
Adds a new on-chain USDC transfer flow for compute top-up, which increases risk due to chain/asset handling and fee calculation, but changes are localized to a new command and API wrapper methods.

Overview
Adds a new acp compute command group with status (fetches compute balance/limit/usage) and top-up (validates amount/chain, computes a fee, sends an on-chain USDC transfer, then notifies the backend with the tx hash).

Extends the Agent API client with compute types and endpoints (/agents/:id/compute/account, /common/compute-fee, /agents/:id/compute/top-up), wires the command into the CLI entrypoint, and updates README.md/SKILL.md docs to include the new compute workflow.

^{Reviewed by Cursor Bugbot for commit ae12288. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ae12288. Configure here.}

[cursor]

agentAddress parameter silently dropped from API request body

High Severity

The computeTopUp method accepts an agentAddress parameter but never includes it in the POST body ({ amount, txnHash }). The caller in compute.ts explicitly fetches the wallet address via getWalletAddress() and passes it in, but the value is silently discarded. Other similar methods in the same file (e.g., getCoinbaseUrl, initCrossmintOrder) consistently include walletAddress in their request bodies, confirming this is an accidental omission.

Additional Locations (1)

• src/commands/compute.ts#L127-L134

 

^{Reviewed by Cursor Bugbot for commit ae12288. Configure here.}

[cursor]

Option description claims dynamic default but uses hardcoded value

Low Severity

The --chain-id option description claims it "defaults to the account's preferred billing chain," but the actual default is the hardcoded string "8453". The ComputeAccount type defines a preferredBillingChainId field that is never read or used for this default. Users may omit --chain-id believing the CLI will auto-detect their preferred chain, potentially sending USDC on an unintended chain.

 

^{Reviewed by Cursor Bugbot for commit ae12288. Configure here.}