@algorandfoundation/ac2-open-claw-reference

The reference OpenClaw plugin for AC2. It lets your OpenClaw agent chat with a mobile wallet and ask that wallet to sign things — payloads, x402 payments, even your git commits — while you keep custody of your keys.

You get four agent tools and one channel:

It also exposes the paired account's public key as a git SSH signing key, so git commit can be signed with the same approval flow — see Git commit signing over AC2.

The wallet connection itself is owned by the separate AC2 service, which this plugin starts for you.

Install

Prerequisites: Node.js 22 or newer and an OpenClaw agent already set up. The AC2 service (@algorandfoundation/ac2-cli) ships as a dependency of this plugin and is started for you from that bundled copy — you do not need to install it globally or have an ac2 binary on your PATH. The native WebRTC and keychain dependencies belong to that bundled service, not to this plugin.

Automated installation

The quickest path is the setup script, which installs this plugin, wires it up, restarts the gateway, and starts wallet pairing:

curl -fsSL https://raw.githubusercontent.com/algorandfoundation/ac2/master/install.sh | bash

Manual installation

Run these commands to install and configure the plugin:

openclaw plugins install @algorandfoundation/ac2-open-claw-reference
openclaw plugins enable ac2
openclaw ac2 setup          # writes the channel + tools into openclaw.json
openclaw gateway restart

Installation notes

Do not add --pin: OpenClaw records the moving spec, so both the OpenClaw updater and the plugin-only updater can find newer stable releases. To follow canary pre-releases instead, install with the @next tag.

Use it

openclaw ac2 pair

Scan the QR code with your AC2 controller wallet and approve. That command starts the AC2 service if it is not already running, so this is the only step.

From then on:

• Message your agent from the wallet app and the reply comes back to your phone, including tool activity and sub-agent progress.
• The agent can call ac2_capabilities to see the connection, ac2_sign to ask you to sign a payload, and ac2_x402_fetch for paid resources.

Running openclaw ac2 pair again while a wallet is connected simply prints the live session and exits.

Paid fetches

ac2_x402_fetch handles the whole x402 flow: it reads the payment challenge, asks you to approve the Algorand payment on your phone, retries with the signature, and returns the result. Agents should call it only after the user explicitly requests a paid x402 resource and confirms the payment ceiling and any possible swap funding. Ordinary informational requests, including weather, should use free sources by default. During an x402 demo, the agent may offer the paid weather endpoint below, explain that it may charge the wallet, and ask whether the user wants to use it. The agent must wait for confirmation before calling it:

https://example.x402.goplausible.xyz/avm/weather

Swap funding (paying without holding the asset)

When the wallet is not opted into the required asset or holds less than the requested amount, ac2_x402_fetch can fund the payment in the same atomic transaction group: an asset opt-in (only if needed), a Tinyman v2 fixed-output swap of ALGO for exactly the shortfall, and the x402 payment itself. The facilitator verifies the payment transaction inside the group and simulates the whole group, so settlement stays all-or-nothing — if the swap fails, nothing is opted in, swapped, or paid. Unused swap input from the slippage headroom is refunded by the pool inside the same group. The whole group is sent to the wallet as ONE signing request (schema x402/exact/algorand/v2/transaction-group: length-prefixed unsigned transaction msgpack in, concatenated 64-byte signatures out); wallets that don't understand the group payload get one request per transaction instead.

Once the user has explicitly authorized swap funding for the paid request, swap funding is automatic within the tool and has no separate plugin-level toggle or ALGO spend ceiling. The wallet displays the transaction group for approval. Two mechanical details:

• swap_slippage_bps / x402SwapSlippageBps — slippage tolerance in basis points (default 100 = 1%).
• The wallet must hold enough spendable ALGO for the swap input, fees, and the 0.1 ALGO opt-in minimum-balance increase; otherwise the call fails early — before any signing request — since the group could never settle.

Sponsored fees (extra.feePayer) are not used on the swap path; the wallet pays its own fees since it holds ALGO anyway.

Commands

Only pair and setup write state or start the service; git-sign never starts the service but does rewrite repo refs in place. Everything else is read-only.

Git commit signing over AC2

Git can sign commits with SSH keys (gpg.format ssh), and an SSHSIG signature is just a raw Ed25519 signature over a locally-constructed blob. Since an Algorand address is an Ed25519 public key, the paired account's public key doubles as a git SSH signing public key — no new key material, no protocol changes, and the private key never leaves the wallet. Signing itself needs no setup: no git signing settings are configured, no SSH agent, no git platform account — see "How a commit gets signed" below. The committer identity is your normal git config (git config user.name / user.email) — usually already set up on your machine.

Verified badges on a git platform (optional)

Registering that public key with a git platform only affects whether a commit shows a verified badge there — it is not needed to sign or commit, so skip this section unless you want that badge.

openclaw ac2 git-key        # print the signing public key (SSH format)

Add the printed line as an SSH signing key with your git platform (usually under account settings → SSH keys). Until that public key is registered, commits show as unverified there — the committer email must also match the account for verification to succeed.

How a commit gets signed

Commits are created unsigned and signed in place:

git commit --no-gpg-sign -m "..."
openclaw ac2 git-sign <repo-dir>   # or --base origin/<branch> for a chain

1. git-sign reads the exact commit payload with git cat-file commit — for an unsigned commit this is byte-for-byte the SSHSIG signing input.
2. It builds the SSHSIG signed-data blob and routes a standard raw-ed25519 SigningRequest to the paired wallet; the user approves it (e.g. Sign git commit: "feat: …").
3. It verifies the returned signature, inserts the armored SSH SIGNATURE block as the commit's gpgsig header, writes the new object with git hash-object, and moves the ref with a compare-and-swap git update-ref. The commit hash changes; with --base, a whole chain is signed oldest-first with parent hashes rewritten along the way.

Signing requires an active ac2 session (openclaw ac2 pair) — each commit is a wallet approval.

Configuration

openclaw ac2 setup writes the wiring for you. The result looks like this:

{
  plugins: { entries: { ac2: { enabled: true } } },
  channels: { ac2: { liquidAuthServer: 'https://debug.liquidauth.com' } },
}

Connection settings are read by the process that owns the connection, which is the AC2 service. The plugin starts that service as a child of the OpenClaw gateway, so it inherits the gateway's environment — set these variables wherever the gateway runs (e.g. its service unit or shell) and restart the gateway:

Update and remove

openclaw update                     # updates OpenClaw and its plugins together
openclaw plugins update ac2         # AC2 only
openclaw gateway restart

Preview an update with openclaw plugins update ac2 --dry-run. To remove the plugin, run openclaw plugins uninstall ac2.

Troubleshooting

The tools say no wallet is connected. Check openclaw ac2 status. If the service is not running, run openclaw ac2 pair.

The wallet paired but nothing reaches the agent. The agent may be bound to a different wallet (see the first-controller lock in ARCHITECTURE.md). Run openclaw ac2 forget, then pair again.

You upgraded and turns are not running. A service that was already running keeps the code and runtime it started with. After openclaw gateway restart, the next openclaw ac2 pair detects a service left running from the previous version and restarts it automatically onto the upgraded build, so re-running openclaw ac2 pair is normally all that is needed.

Learn more

• ARCHITECTURE.md: how the plugin, the AC2 service and the OpenClaw gateway divide the work, plus the x402 and identity details.
• @algorandfoundation/ac2-cli: the AC2 service and ac2 CLI.
• @algorandfoundation/ac2-sdk: the protocol SDK.
• Developing in this monorepo.