Skip to main content
A connected assistant (Grok, Muse, a scheduled Claude Code task) reads your account and proposes changes. It never confirms, trades or moves funds: every proposal waits for you in Circuit, and confirming uses your passkey.

Connect

The CLI opens the same browser handoff as circuit auth login. Approve with your passkey, name the connection, choose which wallets it may propose changes for, and whether it may build new agents, propose agent actions, or propose swaps and transfers. The permit lasts one year and is saved under the assistant’s name, separate from your own sign-in and from other assistants. Commands use your own sign-in when one is saved, otherwise the only assistant sign-in on the machine; when several sign-ins share a machine, the assistant sets CIRCUIT_ASSISTANT="Muse" (or passes --assistant "Muse") for every command. Change access or remove it under Connected apps in your profile menu, beside Settings and Passkeys; every request re-reads the connection’s access, so changes apply to the existing permit at once and a removed connection’s permit is refused. The permit carries only account.read, which reads the whole account: every wallet, agent source, Builder workspace and Ask chat. The wallet choice limits proposals, not reads. Routes that need account.write, such as uploading code, confirming a proposal, signing and account settings, refuse it; the one exception is dismissing a proposal the assistant itself submitted. Free-text requests to Circuit are refused too: an assistant submits reviews and builds.

Workflow

  1. Read the account first. circuit ask context prints the snapshot Circuit reasons from: wallets (id, name, address, VM family), indexed holdings, running sessions with their account (wallet for Real money, simulated for Paper trading), status, P&L and newest logs, agents with their startingAsset (including minimumAmount), pending operations, backtests, workspaces, supported networks with their native asset, and reviews: the proposals this assistant submitted that still wait for the user (under your own sign-in, those of every assistant). Use only ids and assets from this output.
  2. Look closer. circuit agent sessions lists the running sessions with P&L and ROI, and circuit agent session <session-id> shows one session’s positions with P&L, inventory and settings. circuit agent get <agent-id> shows one published agent’s description, schedule, TVL and ROI. circuit wallet holdings shows every wallet’s holdings as Home does, each with agentHoldings: how much of it each of your agents holds. Each prints the document the web app reads, as JSON; --json puts it on one line under a named field.
  3. Build through Builder. circuit ask --build "<strategy in plain words>" --wait builds a new agent and waits for the build to finish; it needs a connection allowed to build. Assistants never edit existing agents; the user does. Never write agent files or run circuit new or circuit upload; an assistant cannot upload.
  4. Propose changes. Write a JSON file matching circuit capabilities --resource ask/review and submit it with circuit ask --review <file> "<reason>" (- reads stdin). The request text is recorded as the reason for the proposal.
  5. Withdraw what no longer applies. Take the ids from reviews: circuit ask action <action-id> --dismiss dismisses a session proposal, and circuit operations cancel <operation-id> dismisses a swap or transfer the user has not approved. An assistant withdraws only what it proposed and only while it still waits for the user: once the user approves, the work is theirs to cancel.

Rules Circuit enforces

A refused proposal returns the reason, for example Assistants may only propose transfers between your own wallets.