Agent-Q

Development status: Agent-Q is an active development project with hardware-tested Sui signing paths for CLI, MCP, and supported provider flows. The current StackChan CoreS3 Firmware path uses DEV_PROFILE material intended for development and demos, not real-asset custody. See Current Status for storage and profile limitations.

Concept

Agent-Q separates execution surfaces from signing authority.

Execution capability is not signing authority. Agent-Q keeps that boundary explicit for agent-driven and local Sui signing flows.

This README describes the Agent-Q authority-boundary architecture for local Sui signing flows. Current implementation status and profile limitations are tracked in docs/IMPLEMENTATION_STATUS.md.

MCP clients, Sui CLI, and supported Sui app adapters submit bounded requests through the local agent-q host process. AI agent runtimes usually reach Agent-Q through MCP clients. The host relays requests; it does not store signing material, decide policy, or approve signing.

Agent-Q Firmware runs on a separate signing device. It holds signing material and policy for the implemented material profile, checks device state and request contents, applies the implemented policy or device-local approval gate, and returns signed results or explicit failures.

Signing request transport stays local. Signing authority stays on the device. Requesters can ask for signatures, but they cannot hold signing material, choose the authorization mode, or approve their own requests.

Structure

Agent-Q has three roles:

• requesters create signing, account, policy read, policy proposal submission, or status requests. MCP clients, Sui CLI, Sui app adapters, and the Admin Page are request surfaces, not signing authorities.
• the host process is the local agent-q process. It exposes MCP stdio tools, the local HTTP API, the Admin Page, and adapter-facing request surfaces, then relays bounded requests to Firmware.
• Agent-Q Firmware is the software running on the signing device. Firmware owns policy checks, device-local approval gates, signing, persistence, and cleanup, and holds signing material for the implemented material profile.

Agent-Q uses a simple authority model:

• requesters create requests;
• the host process relays requests;
• Firmware handles each implemented request type according to device-local state.

For signing requests, Firmware decides whether the implemented policy or device-local approval gate permits signing.

Unsupported chains and methods fail explicitly.

Use Agent-Q

• Sui users can register agent-q-sui-signer as a Sui CLI external signer. See packages/agent-q/README.md.
• MCP clients can run the local server and call Agent-Q MCP tools. See packages/agent-q/README.md.
• Sui app developers can use the Sui provider package for supported Wallet Standard adapter flows. See packages/provider-sui/README.md and packages/sample-sui-dapp-kit/README.md.
• Sui zkLogin browser setup and sign-only transaction checks live in the non-production test web sample. See packages/sample-zklogin-test-web/README.md.
• Firmware and hardware developers working on device-owned signing policy, local approval, and bounded signing flows should start with firmware/README.md.

Packages

Current Implementation Highlights

The current implementation includes these device-owned paths. They are development/demo capabilities; Current Status below defines the DEV_PROFILE and product-active limits.

• Device-local BIP-39 setup: Firmware can generate a new 12-word BIP-39 backup phrase on the device, display it for backup, and store DEV_PROFILE root entropy only after local backup confirmation and repeated local PIN entry.
• Device-local mnemonic restore: Firmware can accept a 12-word BIP-39 import through the device UI, verify the checksum, and enter the same local PIN setup path. USB, host process, and MCP mnemonic import are not implemented.
• Sui zkLogin active identity: the browser test flow can prepare and propose bounded zkLogin proof material through the provider/Web Serial path. Firmware reviews the proposal on device, requires local PIN approval, stores one bounded proof record, and projects the active zkLogin Sui account. When zkLogin is active, the same signing request path produces a zkLogin signature envelope after the normal Firmware authorization gate. Firmware stores no raw JWT.
• Large Sui transaction payloads: sign_transaction supports inline txBytes and same-session staged payload delivery for larger Sui transaction bytes, up to the Sui serialized transaction maximum. This is a payload and adapter input capacity, not a claim that every Sui transaction shape is semantically signable; unsupported or unbindable shapes fail before signing.
• Sui sponsored transaction receive path: Firmware has a device-local Sui account setting that controls whether it accepts transactions where the parsed sender is the active account and the parsed gas owner is a different sponsor. When accepted, Agent-Q still returns only the active sender's signature; sponsor signature collection and transaction execution assembly are outside Agent-Q.

Request Flow

flowchart LR
  Agent[AI agent] --> MCP[MCP API]
  Admin[Admin Page] --> HTTP[HTTP API]
  SuiCLI[Sui CLI] --> Signer[agent-q-sui-signer]
  App[Sui app] --> Provider[Sui provider]

  MCP --> Server[agent-q local server]
  HTTP --> Server
  Signer --> Server
  Provider --> Server

  Server --> Core[Agent-Q core]
  Core --> Firmware[Firmware]

Current signing routes are summarized below. In this README, product-active means the matching source, docs, tests, build, current-tree target hardware evidence, and visual evidence are complete in docs/IMPLEMENTATION_STATUS.md. A route can be implemented and hardware-tested while product-active evidence is still being completed.

The current implementation contains Sui zkLogin active identity paths, but docs/IMPLEMENTATION_STATUS.md does not mark them product-active. The sample test web exercises browser-to-device proof setup and sign-only transaction checks over Web Serial. Enoki, OAuth, prover work, and Google OAuth testnet setup stay in the browser test layer; Agent-Q receives only bounded proof proposals. The sample does not display JWTs or proof JSON and does not write them to browser storage.

Unsupported chains and unsupported methods fail explicitly. Chains are exposed through the shared protocol; Agent-Q does not create separate chain-specific product APIs.

Authority Boundary Basics

This section explains who may request work and who may decide. DEV_PROFILE storage and product-active status are covered in Current Status.

• The host process, MCP, Sui CLI tools, providers, apps, and agents are requesters, not signing authority.
• The host process does not store signing material and does not make signing or policy decisions.
• Firmware holds signing material and policy for the implemented material profile and owns signing decisions.
• Firmware chooses the signing authorization gate from device-local state. Requests cannot choose policy authorization mode or user authorization mode.
• Agent-Q cannot verify what happened inside an agent, app, wallet UI, or host process before a signing request was created.
• All external requests are untrusted input. Firmware must parse bounded request contents before signing.

Current Status

Detailed status lives in docs/IMPLEMENTATION_STATUS.md.

Current implementation includes the Sui signing routes listed above, MCP tools, provider-sui, and StackChan CoreS3 Firmware paths. Hardware smoke coverage is recorded in docs/IMPLEMENTATION_STATUS.md; product-active signing support is claimed only when the matching status row says the source, docs, tests, build, hardware, and visual evidence are complete.

Current limitations: