Live now · Get your API key

Network client

Ambient Desktop is growing into a first-party client for the Ambient network, with wallet, balances, programs, and transaction evidence. This surface is in active development.

Ambient Desktop is growing into a first-party client for the Ambient network: embedded keys, balances, programs, and transaction evidence, with the same inspect-everything posture as the rest of the app.

Ambient Desktop settings and workspace.
Desktop is the human-scale client for balances, program work, transactions, and network evidence.

Why the desktop is the client#

Network operations have the same shape as the agentic work the app already does: authorize a capability, perform an action, observe the result, and keep durable evidence of what happened. Rather than ship a separate tool, Ambient is extending the workstation so a developer can move from code work to network work without changing mental models: inspect state, approve the action, capture the receipt.

NETWORK OPERATIONpermissioned · reviewable · durable evidence1Authorizea capabilityDescriptor reviewPermission policy2Performthe actionWallet · programsAmbient L1 CLI3Observethe resultTransaction observationLogs + receipts4Evidencekept durableReceiptsRollback plan

A four-stage chain for a network operation, bounded as permissioned, reviewable, with durable evidence. Stage one, Authorize a capability: descriptor review and a permission policy. Stage two, Perform the action: wallet and programs, via the Ambient L1 CLI. Stage three, Observe the result: transaction observation with logs and receipts. Stage four, Evidence kept durable: receipts and a rollback plan.

Network operations have the same shape as the agentic work the app already does, so the desktop runs them the same way: authorize a capability, perform the action, observe the result, and keep durable evidence at each step.

What the client is being built to do#

  • Wallet workbench: embedded key flow, balances, and approvals, presented through the same permissioned, reviewable surfaces as other capabilities.
  • Programs: deploy, observe, and update programs with the agent assisting, and evidence captured at each step.
  • Ambient L1 CLI: an Ambient blockchain CLI package descriptor and skill provide the building blocks for network operations, exposed as a permissioned capability.
  • Receipts and rollback: transaction observation, receipts, logs, and a rollback plan, consistent with how the app treats all high-impact actions.

Desktop integration of the Tool Oracle and of x402 payments is roadmap direction. x402 is live on the network today: the API accepts pay-per-use payments in USDC on Solana and Base.

Frequently asked#

Can I do on-chain transactions in the app today? Not yet. The Ambient L1 CLI package descriptor and skill are available today as building blocks, but live wallet and transaction flows are still in active development.

Will network operations be sandboxed like other capabilities? Yes. The intent is that network capabilities run through the same descriptor review, permission policy, and audit-artifact model as the rest of the app, with keys and approvals kept in managed, reviewable surfaces. See the security model.

Keep going#