Aomi On-Chain Agent

Build and execute EVM transactions through a conversational AI agent.

Setup

Before running any commands, verify the CLI is available:

which aomi || npm install -g @aomi-labs/client

For signing transactions, viem must be installed:

node -e "require('viem')" 2>/dev/null || npm install viem

Core Workflow

The aomi CLI is not a long-running process. Each command starts, runs, and exits. Conversation history lives on the backend. Local state (session ID, pending/signed txs) is persisted to $TMPDIR/aomi-session.json.

The typical flow is:

1. Chat — send a message, the agent responds (and may queue transactions)
2. Review — list pending transactions
3. Sign — sign and broadcast a pending transaction
4. Verify — check signed transactions or continue chatting

Commands

Chat with the agent

aomi chat "<message>"
aomi chat "<message>" --verbose        # stream tool calls + responses live

Always quote the message. Use --verbose (or -v) to see real-time tool calls, agent reasoning, and intermediate results.

If the agent builds a transaction, it prints a wallet request notice:

⚡ Wallet request queued: tx-1
   to:    0x3fC91A3afd70395Cd496C647d5a6CC9D4B2b7FAD
   value: 1000000000000000000
   chain: 1
Run `aomi tx` to see pending transactions, `aomi sign <id>` to sign.

Connect a wallet

Pass --public-key on the first chat so the agent knows the user's wallet address. It is persisted — subsequent commands in the same session don't need it.

aomi chat "swap 1 ETH for USDC" --public-key 0xYourAddress

List transactions

aomi tx

Shows pending (unsigned) and signed (completed) transactions with IDs, targets, values, and timestamps.

Sign a transaction

aomi sign <tx-id> --private-key <hex-key> --rpc-url <rpc-url>

Signs the pending transaction, broadcasts it on-chain, and notifies the backend. Supports both regular transactions and EIP-712 typed data signatures (e.g. for CoW Protocol orders, permit approvals).

View conversation log

aomi log

Replays all messages with timestamps, tool results, and agent responses.

Session management

aomi status    # session info (ID, message count, pending/signed tx counts)
aomi events    # system events from the backend
aomi close     # wipe local state, start fresh on next chat

Configuration

All config can be passed as flags (priority) or env vars (fallback):

Important Behavior

• Session continuity: After the first aomi chat, the session ID is saved. All subsequent commands operate on the same conversation until aomi close.
• Transaction IDs: Each wallet request gets a unique ID (tx-1, tx-2, ...). Use the exact ID shown in aomi tx when signing.
• EIP-712: The agent may request typed data signatures (e.g. kind: eip712_sign) for gasless swaps or permit approvals. aomi sign handles both kinds automatically.
• Non-blocking: aomi chat exits as soon as the agent finishes responding or a wallet request arrives. It does not wait for signing.
• Verbose mode: Always use --verbose when you need to see what tools the agent is calling or debug unexpected behavior.

Example: Full Swap Flow

# 1. Start a session with wallet connected
aomi chat "swap 1 ETH for USDC on Uniswap" \
  --public-key 0xYourAddress

# 2. Agent builds the tx — check what's pending
aomi tx

# 3. Sign and broadcast
aomi sign tx-1 \
  --private-key 0xYourPrivateKey \
  --rpc-url https://eth.llamarpc.com

# 4. Verify
aomi tx          # should show tx-1 under "Signed" with hash
aomi log         # full conversation replay

# 5. Clean up when done
aomi close

Error Handling

• If aomi sign fails with "viem is required", install it: npm install viem
• If aomi chat returns "(no response)", the agent may still be processing. Wait a moment and run aomi status to check.
• If a transaction fails on-chain, the error message from the RPC is printed. Check the RPC URL, gas, and account balance.
• Run aomi close to reset if the session gets into a bad state.