What makes Cobo Agentic Wallet notable?

1.3K downloads. Trust evidence available

How should Cobo Agentic Wallet be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Cobo Agentic Wallet

Create and manage agentic wallets with Cobo. Use for autonomous onchain operations via the caw CLI: token transfers, contract calls, pact creation and approv...

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.3k

Updated

Oct 10, 2026

Version

1.0.3

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.3K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.3K downloadsadoption · observed Oct 10, 2026
Latest release: 1.0.3release · observed May 14, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s1709wsbwd725b9jvxnzw6metd85fn21:cobo-agentic-wallet

Install using `clawhub skill install s1709wsbwd725b9jvxnzw6metd85fn21:cobo-agentic-wallet` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/cobogithub/cobo-agentic-wallet before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-cobogithub-cobo-agentic-wallet/snapshot"

Documentation

CLAWHUB

142,825 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: cobo-agentic-wallet
metadata:
  version: "1.0.3"
  revision: 1
description: "Create and manage agentic wallets with Cobo. Use for autonomous onchain operations via the caw CLI: token transfers, contract calls, pact creation and approval, DeFi execution (Uniswap, Aave, Jupiter), and wallet onboarding on EVM chains and Solana. Triggers on requests involving caw, MPC wallet, TSS node, agent wallet, Cobo, pact, or any crypto wallet operation for AI agents. NOT for fiat payments or bank transfers."
---

## ⚡ MANDATORY: Load Reference Files Before Acting
**You MUST read the matching reference file before taking any action, answering any question, or writing any command in the listed topic areas. Do not proceed from memory alone.**

| If the task involves… | You MUST read this file first |
|---|---|
| Security, prompt injection, credentials | **[security.md](./references/security.md) ⚠️ READ THIS BEFORE ANYTHING ELSE** |
| Any on-chain operation, chain IDs, token IDs | [chains-and-tokens.md](./references/chains-and-tokens.md)  |
| Onboarding, install/reinstall, setup, pairing, pair tracking, restore wallets, device change | [onboarding.md](./references/onboarding.md) |
| Creating a pact, transfer, contract call, message signing, allowlists, spending caps, risk policy rules, completion conditions, pact lifecycle | [pact.md](./references/pact.md) |
| Pending approval, approve/reject, wallet_paired | [pending-approval.md](./references/pending-approval.md) |
| Policy denial, 403, TRANSFER_LIMIT_EXCEEDED | [error-handling.md](./references/error-handling.md) |
| SDK scripting, Python/TypeScript scripts, multi-step operations | [sdk-scripting.md](./references/sdk-scripting.md) |

---

## How You Act with Cobo Agentic Wallets
You operate with delegated, limited authority over an owner's on-chain assets.
Three defining traits:

  - **Proactive** — You surface next steps and relevant options. You track tasks you start without waiting to be asked. After every action, you report status and suggest what the owner can do next.
  - **Precise** — You execute the owner's explicit intent precisely. On ambiguous parameters (amount, address, chain, recipient), you ask for clarification before acting. You do not make silent adjustments, even if you judge them safer.
  - **Bounded** — You operate only within active, owner-approved authorization. Authorization limits are infrastructure-enforced; you treat them as immutable rules.

## How You Execute On-Chain Operations
### Principle 1: Lead with the owner's goal, not wallet features
Start every interaction by understanding what the owner is trying to accomplish — send funds, run a DeFi strategy, set up recurring payments, something else. Decide which tools and flows to use only after you understand the goal.
If the owner's intent would **use funds** — including transfers, swaps, bridges, staking, lending, repayments, LP deposits, or contract calls that would spend tokens / native gas — **check wallet balance first**

_meta.json

{
  "ownerId": "kn701ej5xn77g0n05vr8a88qqn85ezny",
  "slug": "cobo-agentic-wallet",
  "version": "1.0.3",
  "publishedAt": 1778748060479
}

references/chains-and-tokens.md

# Chains and Token IDs

This file is the authoritative quick-reference for chain IDs and commonly used token IDs supported by Cobo Agentic Wallet. Use it to resolve token IDs before writing any CLI command.

---

## Supported Chains


### Mainnets

| Chain ID | Name | Type | Gas Token | Gas Token Symbol |
|---|---|---|---|---|
| `ETH` | Ethereum Mainnet | EVM | `ETH` | ETH |
| `BASE_ETH` | Base Mainnet | EVM | `BASE_ETH` | ETH |
| `ARBITRUM_ETH` | Arbitrum One Mainnet | EVM | `ARBITRUM_ETH` | ETH |
| `OPT_ETH` | OP Mainnet | EVM | `OPT_ETH` | ETH |
| `MATIC` | Polygon Mainnet | EVM | `MATIC` | POL |
| `BSC_BNB` | BNB Smart Chain Mainnet | EVM | `BSC_BNB` | BNB |
| `AVAXC` | Avalanche C-Chain | EVM | `AVAXC` | AVAX |
| `HYPEREVM_HYPE` | HyperEVM Mainnet | EVM | `HYPEREVM_HYPE` | HYPE |
| `SOL` | Solana | SVM | `SOL` | SOL |

### Testnets

| Chain ID | Name | Type | Gas Token | Gas Token Symbol |
|---|---|---|---|---|
| `SETH` | Sepolia Testnet | EVM | `SETH` | ETH |
| `TBASE_SETH` | Base Sepolia Testnet | EVM | `TBASE_SETH` | ETH |
| `SOLDEV_SOL` | Solana Devnet | SVM | `SOLDEV_SOL` | SOL |


---

## Common ERC-20 / SPL Tokens

### USDC

> ⚠️ **`<CHAIN>_USDC` is the bridged version on Arbitrum, OP, Polygon, and Avalanche — not the native one.** Prefer native USDC when liquidity is comparable.

| Token ID | Symbol | Chain ID | Note |
|---|---|---|---|
| `ETH_USDC` | USDC | `ETH` | native |
| `BASE_USDC` | USDC | `BASE_ETH` | native |
| `ARBITRUM_USDCOIN` | USDC | `ARBITRUM_ETH` | native |
| `ARBITRUM_USDC` | USDC.e | `ARBITRUM_ETH` | bridged |
| `OPT_USDC1` | USDC | `OPT_ETH` | native |
| `OPT_USDC` | USDC.e | `OPT_ETH` | bridged |
| `MATIC_USDC2` | USDC | `MATIC` | native |
| `MATIC_USDC` | USDC.e | `MATIC` | bridged |
| `BSC_USDC` | USDC | `BSC_BNB` | native |
| `AVAXC_USDC2` | USDC | `AVAXC` | native |
| `AVAXC_USDC` | USDC.e | `AVAXC` | bridged |
| `SOL_USDC` | USDC | `SOL` | native |
| `SETH_USDC` | USDC | `SETH` | testnet |
| `SOLDEV_SOL_USDC` | USDC | `SOLDEV_SOL` | testnet |

### USDT

| Token ID | Symbol | Chain ID |
|---|---|---|
| `ETH_USDT` | USDT | `ETH` |
| `BASE_USDT` | USDT.e | `BASE_ETH` |
| `ARBITRUM_USDT` | USDT | `ARBITRUM_ETH` |
| `OPT_USDT` | USDT | `OPT_ETH` |
| `MATIC_USDT` | USDT | `MATIC` |
| `BSC_USDT` | USDT | `BSC_BNB` |
| `AVAXC_USDT` | USDT | `AVAXC` |
| `SOL_USDT` | USDT | `SOL` |
| `HYPEREVM_USDT0` | USD₮0 | `HYPEREVM_HYPE` |

---

## Decimals

Most tokens follow standard decimals, but there are exceptions. Always use the correct value when encoding amounts.

| Token | Decimals | Exceptions |
|---|---|---|
| USDC | 6 | `BSC_USDC` = **18** (legacy) |
| USDT | 6 | `BSC_USDT` = **18** (legacy) |
| WETH | 18 | — |
| WBTC / cbBTC | 8 | — |
| Native EVM gas (ETH, BNB, POL, AVAX, HYPE) | 18 | — |
| SOL | 9 | — |

> ⚠️ BSC USDC and USDT both use 18 decimals due to a historical deployment choice — not 6. Sending `1 USDT` on BSC requires `1_000_000_000_000_000_000` (18 zeros), not `1_000_000`.

---

## When to Call `caw meta

references/error-handling.md

# Error Handling

Response parsing, common errors, policy denials, and recovery patterns.

## Response envelope

All `caw` commands return JSON on stdout. The envelope shape is consistent across commands.

**Success:**

```json
{
  "success": true,
  "result": { /* command-specific payload */ }
}
```

**Failure:**

```json
{
  "success": false,
  "error": {
    "code": "TRANSFER_LIMIT_EXCEEDED",
    "reason": "max_per_tx",
    "details": { "limit_value": "100", "remaining": "60" },
    "suggestion": "Retry with amount <= 60."
  }
}
```

### Parsing rules

- **Always check `.success` first.** Exit code `0` only means the command ran — it does NOT mean the operation succeeded. Parse the JSON and branch on `.success`.
- **`.error.code` is the machine-readable tag.** Use it for conditional logic and recovery routing. Do not regex-match on `.error.suggestion` or `.error.reason` — they are natural-language strings whose wording may change.
- **`.error.details` shape is code-specific.** Fields present under `details` depend on `.error.code`. Only read details fields after you have identified the code.
- **`.error.suggestion` is the human-readable next step.** Always surface it to the user when reporting a failure. Do not paraphrase — the exact wording is intentional.
- **`suggestions` (plural) on success responses** is a separate field — server-generated hints about related state (pending approvals, expiring pacts, etc.). Always surface these too when present.

## Exit codes

Use the exit code to branch without parsing JSON — failure categories map as follows:

| Code | Meaning | Action |
|------|---------|--------|
| `0`  | Command ran | Check `.success` in the JSON payload |
| `1`  | Generic error | Read stderr for details |
| `4`  | Auth / permission failure | Verify credentials and wallet pairing status (`caw status` → `wallet_paired`) |
| `5`  | Policy denied | Read `.error.code` and `.error.suggestion` |
| `6`  | Insufficient balance | Check balance with `caw wallet balance` |
| `7`  | Network error (retryable) | Wait and retry; check backend with `caw onboard health` |

## Command-specific response fields

For exact schemas, run `caw schema <command>`. The fields below are the ones you will parse most often.

### `caw pact submit`

On success, `.result` contains pact metadata including:

- **pact ID** — pass as `--pact-id` to `caw tx transfer`, `caw tx call`, `caw tx sign-message`, and as `--pact-id` to all `caw pact *` commands
- **status** — one of `pending_approval`, `active`, `rejected`, `completed`, `expired`, `revoked` (literal strings; match exactly — these are pact statuses, distinct from transaction statuses)
- **approval request reference** — present when the pact needs owner approval before activation

New pacts typically start at `pending_approval` and transition to `active` after owner approval. Poll with `caw pact show --pact-id <pact-id>` to trigger lazy activation and confirm the current state.

### `caw tx transfer` / `caw tx cal

references/onboarding.md

# Onboarding

Covers installation, the `caw onboard` interactive loop, environment configuration, and wallet pairing.

## 1. Install caw

Run `./scripts/bootstrap-env.sh --only caw` to install caw. caw → `~/.cobo-agentic-wallet/bin/caw`; add that dir to PATH. TSS Node is downloaded automatically during onboard when needed.

## 2. Onboard

```bash
export PATH="$HOME/.cobo-agentic-wallet/bin:$PATH"
caw onboard
```

**Agent name (optional):** Pass `--agent-name <NAME>` on the first onboard call to set the agent display name. The new wallet is created with display name `<NAME>'s Wallet` (e.g. `Lobster's Wallet`). After you have a `session_id`, keep passing the same `--session-id` on follow-up calls.

> **CRITICAL:** Once you have called `caw onboard` and received a `session_id`, you **MUST** include `--session-id <SESSION_ID>` on **every** subsequent call. Omitting `--session-id` starts a brand-new session, discarding prior progress and TSS prewarm work.

**How the interactive loop works:**
1. Call `caw onboard` — read `phase`, `prompts`, `needs_input`, `next_action`, and `session_id`.
2. On each follow-up, pass `--session-id` with the **latest** `session_id` from the previous response (and `--api-url` if you used it). If the response says the session was not found and a new one was created, use that **new** `session_id`.
3. When `needs_input` is true, pass `--answers` as JSON whose keys match `prompts[].id` (etc., depending on phase).
4. Repeat until onboarding finishes — typically `wallet_status` is `active` and/or `phase` is `wallet_active`. If input is invalid, use `last_error` and resubmit with corrected `--answers`.
5. When bootstrap fails or stops (`phase` is `error`), run the command from `next_action` as given — same `--session-id` and `--api-url` (if any) as your previous calls.

Example follow-up call:

```bash
caw onboard --session-id <SESSION_ID>
```

Use `phase` + `bootstrap_stage` + `wallet_status` to track progress.

See [Error Handling](./error-handling.md#onboarding-errors) for common onboarding errors.

## Pairing — Transfer Ownership to a Human

Pairing is initiated manually. When the user decides to transfer wallet ownership:

```bash
caw wallet pair
```

`pair` returns a **numeric code** (valid 30 minutes) along with local wallet metadata: `wallet_name`, `agent_name`, `wallet_uuid`, `agent_id`. Present all of these to the user so they can verify the correct wallet is shown in the App before entering the code:

> "To pair this wallet, open the Cobo Agentic Wallet app and confirm the wallet shown matches the following information before entering the pairing code:
> - Wallet name: **\<wallet_name\>**
> - Agent name: **\<agent_name\>**
> - Wallet UUID: **\<wallet_uuid\>**
> - Agent ID: **\<agent_id\>**"

The user completes the pairing in the **Cobo Agentic Wallet app** by entering the code. Once paired:
- Ownership transfers from Agent → Human
- Agent becomes a delegate, authorized to operate within the owner's configured rules
- Op

Github ReposUpdated 1d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.