Coinbase is rolling out Agent Controls for its service that connects users' AI tools to their trading accounts, adding limits enforced on Coinbase's servers while leaving users responsible for the trades their agents make. The announcement, made Nov. 11, was promoted by CEO Brian Armstrong on Nov. 13 as a way to make AI use in financial accounts safer.
The controls do not mean that a pause ends exposure. Coinbase's description of auto-stop does not say it cancels outstanding orders or closes existing positions.
How the limits work
Coinbase describes a maximum dollar amount for each trade and a cap on total trading over 24 hours. Trades that exceed the volume limit will not go through. Auto-stop adds a portfolio percentage-loss trigger, after which the agent stops placing trades until the user turns trading back on in the Coinbase app.
Enforcement runs on Coinbase's servers, where the agent cannot bypass the limits or change them itself, while users manage the settings through their authenticated Coinbase account. That separates the rules governing execution from instructions given to an AI model.
Permissions by product category are not yet available. Coinbase labels the choice of whether an agent may trade crypto, equities or derivatives as coming soon.
What the announcement leaves open
The announcement gives no loss-calculation baseline or valuation frequency, and does not define how the 24-hour volume window is counted.
Coinbase's agent guide treats order management as a set of distinct operations. Its equity guidance warns that receiving an order ID is not proof of a fill and says individual cancellation results must be checked. The command reference lists canceling an order and closing a position separately, with availability depending on the product.
The practical implication is that a user cannot treat an agent's stopped status as confirmation that exposure has ended. A pause, a successful cancellation and a closed position answer different questions. The published auto-stop description supports the first of those without promising the other two.
Portfolio scoping and a futures exception
Users can fund and scope a dedicated portfolio for spot crypto. Coinbase's setup documentation recommends a dedicated portfolio funded with only what the user is willing to risk, with agent access restricted to it, making the initial allocation and permission choices part of the protection.
US derivatives, including futures, require the default portfolio. A user considering futures cannot assume the same dedicated spot-portfolio boundary applies across every supported asset class.
Supported AI apps connect through remote MCP using Coinbase OAuth, where users approve portfolios. The local command-line interface instead uses a CDP API key scoped to selected accounts, with Trade and Transfer permissions. The documented Transfer permission allows internal portfolio moves, and Coinbase maintains a client allowlist, so compatibility alone does not grant access.
The product page says crypto, stocks and futures availability depends on region and account eligibility. Approval before each trade and unattended scheduling also depend on the agent app.
Revoking access and user responsibility
Coinbase's guide points users to Account Security Connections to revoke access, but deleting a local skill or clearing a chat does not revoke it.
Coinbase also warns that AI agents can fail, trading can lose the entire investment, and users assume responsibility for agent transactions and third-party data use. Users still have to decide what exposure they accept, check what has executed and manage the resulting positions.
