@agentlayer.tech/wallet 0.1.89 → 0.1.91

package/claude-code/plugins/agent-wallet/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "agent-wallet",
   "displayName": "Agent Wallet",
-  "version": "0.1.89",
+  "version": "0.1.91",
   "description": "Claude Code bridge for the existing AgentLayer wallet runtime. Connects to Solana, Bitcoin, and EVM wallets without creating a new one.",
   "author": {
     "name": "AgentLayer"

package/claude-code/plugins/agent-wallet/README.md

@@ -54,7 +54,9 @@ no-op once the backend is healthy.
 - `/wallet-sol` — print the current Solana wallet overview directly in chat.
 - `/wallet-evm` — print the wallet overview for the current/default EVM network
   directly in chat.
-- `/wallet-base` — print the Base EVM wallet overview directly in chat.
+- `/wallet-base` — print the Base EVM wallet overview directly in chat and
+  switch the session's active wallet backend to Base so follow-up wallet
+  requests default to it.
 - `/wallet-ethereum` — print the Ethereum EVM wallet overview directly in chat.
 - `/agentlayer-autonomous-approve` — enable high-trust autonomous Base swaps
   (`swap_evm_tokens` / `swap_evm_uniswap_tokens` on Base only) without

package/claude-code/plugins/agent-wallet/commands/agentlayer-autonomous-approve.md

@@ -1,5 +1,5 @@
 ---
-description: Enable AgentLayer autonomous Base swaps and EVM DeFi tools without per-transaction approvals.
+description: Enable AgentLayer autonomous wallet execution (every write tool) without per-transaction approvals.
 allowed-tools: AskUserQuestion, mcp__agent_wallet__agentlayer_autonomous_approve, mcp__agent_wallet__agentlayer_autonomous_status
 disable-model-invocation: true
 ---
@@ -13,17 +13,17 @@ If both `base_swaps` and `defi_tools` are already enabled, report that the combi
 Otherwise, use `AskUserQuestion` to confirm:
 
 - header: `Autonomy`
-- question: `Enable AgentLayer autonomous Base swaps and EVM DeFi tools without per-transaction approvals?`
+- question: `Enable AgentLayer autonomous execution for every wallet write tool (transfers, swaps, bridges, staking, x402 payments, generic contract calls, DeFi management) without per-transaction approvals, with no spend cap?`
 - options:
-  - `Enable` — `Turns on the combined autonomous permission group until revoked.`
+  - `Enable` — `Turns on unbounded autonomous execution for every wallet write tool until revoked.`
   - `Cancel` — `Leaves per-transaction approvals in place and does not change permissions.`
 
 Only if the user selects `Enable`, call `agentlayer_autonomous_approve` with:
 
 ```json
 {
-  "scope": "base_swaps",
-  "purpose": "User requested autonomous Base swaps and EVM DeFi tools from Claude Code.",
+  "scope": "all",
+  "purpose": "User requested autonomous wallet execution from Claude Code.",
   "user_intent": true
 }
 ```
@@ -34,7 +34,6 @@ If the user selects `Cancel`, do not call any write tool. State that autonomous
 
 Be explicit in the response:
 
-- This removes per-transaction approvals for Base Velora/Uniswap swap execute calls and supported EVM DeFi management tools.
-- The `scope=base_swaps` argument is a compatibility value; this command enables the combined autonomous permission group.
-- It does not authorize transfers, bridges, Solana swaps, or generic contract calls.
+- This removes per-transaction approvals for every wallet write tool: transfers, bridges, Solana swaps, staking, x402 payments, generic contract calls, Base Velora/Uniswap swap execute calls, and supported EVM DeFi management tools.
+- This command enables the combined autonomous permission group, which has no per-tool allow-list, spend cap, or session TTL -- it is unbounded by amount within its scope.
 - The user can run `/agentlayer-autonomous-revoke` to disable it.

package/claude-code/plugins/agent-wallet/commands/agentlayer-autonomous-revoke.md

@@ -1,5 +1,5 @@
 ---
-description: Disable AgentLayer autonomous Base swaps and EVM DeFi tools.
+description: Disable AgentLayer autonomous wallet execution (every write tool).
 allowed-tools: mcp__agent_wallet__agentlayer_autonomous_revoke, mcp__agent_wallet__agentlayer_autonomous_status
 disable-model-invocation: true
 ---
@@ -10,7 +10,7 @@ Call `agentlayer_autonomous_revoke` with:
 
 ```json
 {
-  "scope": "base_swaps"
+  "scope": "all"
 }
 ```
 

package/claude-code/plugins/agent-wallet/commands/wallet-base.md

@@ -1,37 +1,60 @@
 ---
-description: Show the connected EVM wallet overview for Base directly in chat.
-allowed-tools: mcp__agent_wallet__get_wallet_overview
+description: Show the connected Base EVM wallet portfolio directly in chat and switch the active wallet backend to Base.
+allowed-tools: mcp__agent_wallet__get_wallet_overview, mcp__agent_wallet__set_wallet_backend
 disable-model-invocation: true
 ---
 
-Show the connected EVM wallet overview for Base directly in chat.
+Show the connected Base EVM wallet portfolio directly in chat, and leave the
+session's active wallet backend switched to Base so follow-up wallet calls in
+this conversation don't need the backend specified again.
 
-1. Call `get_wallet_overview` with:
+1. Call `get_wallet_overview` and `set_wallet_backend` together — they are
+   independent, so issue both in the same turn rather than sequentially:
 
 ```json
+// get_wallet_overview
 {
   "backend": "evm",
   "network": "base"
 }
 ```
 
-2. Format the response as a compact wallet report:
+```json
+// set_wallet_backend
+{
+  "backend": "base",
+  "network": "base"
+}
+```
+
+2. Format the `get_wallet_overview` response as a compact wallet report:
 
 - state the wallet as `EVM (Base)`
-- include `chain`, `network` (or `requested_network`), `address`, and `total_value_usd` when present
+- include `chain`, `network` (or `requested_network` when `network` is absent), `address`, and `total_value_usd` when present
 - render a Markdown table with columns: `Asset | Type | Amount | USD Value`
 - use `assets` when present
 - for each asset row, prefer:
-  - asset label: `symbol`, then `token_address`, then `asset_type`
+  - asset label: `symbol`, then `name`, then `token_address`, then `asset_type`
+  - when the label came from `symbol`/`name` (not the token_address itself) and a `token_address` is present, append it shortened in parentheses next to the label as `first6…last4` (e.g. `USDC (0x833589…029139)`) — keep the contract visible but compact, never show it twice
   - amount: `amount_ui`, then `balance_ui`, then `balance_native`, then `amount_raw`
   - usd value: `value_usd`, then `balance_usd`
 - omit zero-value rows only when both the amount and USD value are clearly zero
 - if no asset rows are available, still report the native balance summary in prose
-
-3. After the table, add one short metadata line with any available sources:
-
-- `source`
-- `token_discovery_source`
-- `pricing_source`
-
-4. Do not suggest transfers, swaps, or other write actions unless the user explicitly asks for them.
+- do not include source metadata lines or footer fields such as `source`, `token_discovery_source`, or `pricing_source`
+
+3. Assets with no `symbol`/`name` and no `price_usd` are unverified contracts
+   (commonly spam or airdropped tokens on Base). Do not list them individually
+   in the table — instead add one short line after the table noting how many
+   were omitted, e.g. "Plus 46 unverified ERC-20 contracts with no symbol or
+   price data (not included in the total)."
+
+4. After the table, add one short line confirming the session wallet backend
+   is now Base so the user knows follow-up wallet requests will target it by
+   default. If `set_wallet_backend` failed, add one short warning line instead
+   (e.g. a stale local EVM daemon holding its port after a plugin upgrade) —
+   note that the portfolio above is still accurate, and that the backend
+   switch can be retried. Never drop the portfolio report because the switch
+   failed.
+
+5. Do not suggest transfers, swaps, bridging, or other write actions unless
+   the user explicitly asks for them.

package/codex/plugins/agent-wallet/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-wallet",
-  "version": "0.1.89",
+  "version": "0.1.91",
   "description": "Codex plugin bridge for the AgentLayer wallet runtime.",
   "author": {
     "name": "AgentLayer"

package/codex/plugins/agent-wallet/README.md

@@ -22,7 +22,8 @@ Primary design rules:
 - EVM network selection with `set_evm_network`
 - auto-managed approval binding for `preview -> execute` write flows
 - bundled Codex skills, including `wallet-sol` for showing the Solana wallet
-  portfolio directly in chat
+  portfolio directly in chat and `wallet-base` for showing the Base EVM
+  wallet portfolio and switching the session's active backend to Base
 
 ## Runtime requirements
 
@@ -30,12 +31,16 @@ Primary design rules:
 - keep the local wallet files and `~/.openclaw/sealed_keys.json` in place
 - use `wallet codex install --yes` to install this plugin into Codex
 
-## Bundled skill
+## Bundled skills
 
-After `wallet codex install --yes` and a Codex restart, the plugin ships a
-bundled `wallet-sol` skill. In Codex you can invoke it from the slash menu or
-explicitly as `$wallet-sol` to render the connected Solana wallet portfolio as a
-compact chat table.
+After `wallet codex install --yes` and a Codex restart, the plugin ships
+bundled skills:
+
+- `wallet-sol` — invoke from the slash menu or explicitly as `$wallet-sol`
+  to render the connected Solana wallet portfolio as a compact chat table.
+- `wallet-base` — invoke from the slash menu or explicitly as `$wallet-base`
+  to render the connected Base EVM wallet portfolio as a compact chat table
+  and switch the session's active wallet backend to Base.
 
 ## Path resolution
 

package/codex/plugins/agent-wallet/skills/wallet-base/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: "wallet-base"
+description: "Show the current Base EVM wallet portfolio from the local AgentLayer wallet and switch the session's active wallet backend to Base. Use when the user asks for /wallet-base or wants their Base wallet shown directly in chat."
+---
+
+# Base EVM Wallet Portfolio
+
+Use the local AgentLayer wallet MCP tools only.
+
+Workflow:
+
+1. Call `get_wallet_overview` with `backend=evm, network=base` and
+   `set_wallet_backend` with `backend=base, network=base` — they are
+   independent, so issue both in the same turn rather than sequentially.
+2. Render the `get_wallet_overview` result directly in chat in this shape:
+   - title: `EVM (Base) Wallet Portfolio`
+   - bullets for `Chain`, `Network` (or `requested_network` when `network`
+     is absent), `Address`, and `Total Value (USD)` when available
+   - one compact Markdown table with columns: `Asset | Type | Amount | USD Value`
+
+Formatting rules:
+
+- Use `assets` when present.
+- For the asset label, prefer `symbol`, then `name`, then `token_address`,
+  then `asset_type`.
+- When the label came from `symbol`/`name` (not the token_address itself)
+  and a `token_address` is present, append it shortened in parentheses next
+  to the label as `first6…last4` (e.g. `USDC (0x833589…029139)`) — keep the
+  contract visible but compact, never show it twice.
+- For the amount, prefer `amount_ui`, then `balance_ui`, then
+  `balance_native`, then `amount_raw`.
+- For the USD value, prefer `value_usd`, then `balance_usd`.
+- Omit zero-value rows only when both the amount and USD value are clearly
+  zero. If no asset rows are available, still report the native balance
+  summary in prose.
+- Assets with no `symbol`/`name` and no `price_usd` are unverified
+  contracts (commonly spam or airdropped tokens on Base). Do not list them
+  individually in the table — instead add one short line after the table
+  noting how many were omitted, e.g. "Plus 46 unverified ERC-20 contracts
+  with no symbol or price data (not included in the total)."
+- Do not include source metadata lines or footer fields such as `source`,
+  `token_discovery_source`, or `pricing_source`.
+
+After the table:
+
+- Add one short line confirming the session wallet backend is now Base, so
+  the user knows follow-up wallet requests will target it by default. If
+  `set_wallet_backend` failed, add one short warning line instead (e.g. a
+  stale local EVM daemon holding its port after a plugin upgrade) — note
+  that the portfolio above is still accurate, and that the backend switch
+  can be retried. Never drop the portfolio report because the switch
+  failed.
+
+Keep the response concise. Do not suggest transfers, swaps, bridging, or
+other write actions unless the user explicitly asks for them. If
+`get_wallet_overview` fails, surface the tool error plainly and stop.

package/hermes/plugins/agent_wallet/plugin.yaml

@@ -1,5 +1,5 @@
 name: agent-wallet
-version: 0.1.89
+version: 0.1.91
 description: Thin Hermes Agent bridge to the existing AgentLayer/OpenClaw wallet backend
 provides_tools:
   - agent_wallet_tools

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@agentlayer.tech/wallet",
-  "version": "0.1.89",
-  "description": "NPM installer for the OpenClaw Agent Wallet local runtime.",
+  "version": "0.1.91",
+  "description": "Universal AgentLayer wallet installer for OpenClaw, Codex, Claude Code, and Hermes.",
   "type": "module",
   "repository": {
     "type": "git",
@@ -15,7 +15,7 @@
     "wallet": "./bin/openclaw-agent-wallet.mjs"
   },
   "scripts": {
-    "check": "node --check bin/openclaw-agent-wallet.mjs",
+    "check": "node --check bin/openclaw-agent-wallet.mjs && node --test bin/lib/host-detection.test.mjs",
     "build:openclaw-plugins": "node scripts/manage_openclaw_plugin_packages.mjs build",
     "check:openclaw-plugins": "node scripts/manage_openclaw_plugin_packages.mjs check",
     "check:release-version": "node scripts/check_release_version.mjs",
@@ -23,6 +23,8 @@
     "version:sync": "node scripts/sync_version.mjs",
     "release:local": "node scripts/release_local.mjs",
     "test:npm-installer": "python3 agent-wallet/tests/smoke_npm_installer.py",
+    "test:universal-installer": "node --test bin/lib/host-detection.test.mjs && python3 agent-wallet/tests/smoke_universal_installer.py",
+    "test:published-floor-upgrade": "python3 agent-wallet/tests/e2e_install_upgrade_from_published_npm.py",
     "pack:dry-run": "npm pack --dry-run"
   },
   "files": [
@@ -74,6 +76,7 @@
     "!codex/**/*.pyc",
     "!agent-wallet/.pytest_cache/**",
     "!agent-wallet/.runtime-venv/**",
+    "!bin/**/*.test.mjs",
     "!**/node_modules/**",
     "!**/*.tgz",
     "!**/.DS_Store"
@@ -81,6 +84,8 @@
   "keywords": [
     "openclaw",
     "codex",
+    "claude-code",
+    "hermes",
     "agent-wallet",
     "wallet",
     "solana",

package/wdk-btc-wallet/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wdk-btc-wallet",
-  "version": "0.1.89",
+  "version": "0.1.91",
   "private": true,
   "type": "module",
   "description": "Separate BTC-only wallet service built on Tether WDK.",

package/wdk-evm-wallet/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wdk-evm-wallet",
-  "version": "0.1.89",
+  "version": "0.1.91",
   "private": true,
   "type": "module",
   "description": "Separate EVM wallet service built on Tether WDK.",