Coinbase Wallet plans AI agent features for self-custody users

By Nathan Brooks

Coinbase Wallet plans to add AI agent capabilities in 2026, according to Oxxbid, a Coinbase product manager focused on trading. The company has not specified which functions will ship, in what order or on what date.

The roadmap matters less as a single feature than as a consolidation of Coinbase’s agent products. Coinbase already offers self-custody wallets for agent-driven onchain activity, plain-language trading software and a machine-payment protocol. A wallet-level agent could combine those layers in one customer surface, but the permission model remains the central operational question.

Coinbase’s existing agent stack

Coinbase launched Agentic Wallets on February 11, 2026. They let AI agents handle onchain activity, including spending, token trading and yield generation. Users define a spending limit, while onchain trades and transactions rely on user-approved actions.

Beneath Agentic Wallets sits x402, a payments protocol designed for machine-to-machine transactions. By early November 2026, x402 had processed more than 50 million transactions. The figure counts processed transactions rather than dollars moved, so it signals machine-payment usage without establishing the value carried through the protocol.

Coinbase for Agents has been operational since mid-2026. Users provide trading instructions in plain language, and an agent executes them within limits the user sets. Around November 2-3, 2026, Coinbase expanded the tool’s reach through integrations with Hermes and third-party platforms, including bankrbot.

Coinbase Wallet itself added prediction markets powered by Polymarket in September 2026. That gives the wallet another market function, although the source does not identify prediction-market activity as part of the forthcoming agent feature set.

What changes for wallet users?

If Wallet inherits the existing tools, users could submit an instruction in plain language and have an agent initiate permitted actions across connected services rather than assemble each transaction manually. Coinbase has not established whether the feature set will include trading, payments, yield, prediction markets or a narrower combination.

The practical distinction is autonomy with constraints, not unrestricted delegation. Spending caps set the maximum amount an agent may spend, and user-approved actions govern onchain trades and transactions. For an account holder, those controls determine how much authority an agent receives. They describe the existing products; Coinbase has not said whether the Wallet agent will inherit the same settings.

Coinbase’s build history also matters. The company introduced AgentKit, a developer toolkit, in 2024. Its 2026 products made that concept usable for regular customers and added safety rails. A Wallet rollout would extend the progression from developer infrastructure to standalone products and then to a broader wallet surface.

The execution test

The main gap is specification. Coinbase has stated the Wallet’s direction but has not said which agent features will ship or when. The available information leaves two questions material to users and builders: which capabilities arrive first, and whether they share one permission framework or operate as separate routes.

That distinction affects implementation. If the Wallet reuses established controls, users may manage limits and approvals across automated financial functions in one place. If it creates separate controls, they would need to test each route rather than rely on a common policy. For developers, integration depth will determine whether agents can combine payment, trading and yield functions under consistent constraints.

Polymarket-backed prediction markets broaden the range of actions a wallet may eventually support, but Coinbase has not connected that September addition to the agent plan. Treating the two as one launch would go beyond the available evidence.

The next checkpoint is operational: Coinbase must name the first Wallet features, specify their permission model and provide a release timetable before users and developers can judge whether its agent stack has become a unified wallet layer rather than a collection of separate tools.