@agentlayer.tech/wallet 0.1.89 → 0.1.91

package/.openclaw/extensions/agent-wallet/dist/index.js

@@ -724,17 +724,17 @@ const walletSessionToolDefinitions = [
   },
   {
     name: "agentlayer_autonomous_status",
-    description: "Return AgentLayer high-trust autonomous permission status for the combined base_swaps + defi_tools permission group.",
+    description: "Return AgentLayer high-trust autonomous permission status. The autonomous permission group covers every wallet write tool (transfers, bridges, Solana swaps, staking, x402 payments, generic contract calls, Base swaps, and EVM DeFi management), not just base_swaps/defi_tools.",
     parameters: { type: "object", properties: {}, additionalProperties: false },
   },
   {
     name: "agentlayer_autonomous_approve",
     description:
-      "Enable high-trust autonomous execution for the combined permission group. The scope parameter is kept for compatibility; choosing base_swaps or defi_tools enables both Base Velora/Uniswap swaps and supported EVM DeFi management tools until revoked. This does not cover transfers, bridges, Solana swaps, or generic contract calls.",
+      "Enable the high-trust autonomous permission group. The scope parameter accepts \"all\" (recommended); base_swaps and defi_tools are deprecated aliases with identical effect. This covers 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 -- until revoked.",
     parameters: {
       type: "object",
       properties: {
-        scope: { type: "string", enum: ["base_swaps", "defi_tools"], description: "Compatibility scope; either value enables the full autonomous permission group." },
+        scope: { type: "string", enum: ["all", "base_swaps", "defi_tools"], description: "Scope to enable. Use \"all\" (recommended) -- base_swaps and defi_tools are deprecated aliases that enable the exact same full autonomous permission group." },
         purpose: { type: "string" },
         user_intent: { type: "boolean" },
       },
@@ -744,11 +744,11 @@ const walletSessionToolDefinitions = [
   },
   {
     name: "agentlayer_autonomous_revoke",
-    description: "Disable the full high-trust autonomous permission group. The scope parameter is kept for compatibility; either value revokes base_swaps and defi_tools together.",
+    description: "Disable the full high-trust autonomous permission group. The scope parameter accepts \"all\" (recommended); base_swaps and defi_tools are deprecated aliases that revoke the same full group.",
     parameters: {
       type: "object",
       properties: {
-        scope: { type: "string", enum: ["base_swaps", "defi_tools"], description: "Compatibility scope; either value revokes the full autonomous permission group." },
+        scope: { type: "string", enum: ["all", "base_swaps", "defi_tools"], description: "Scope to revoke. Use \"all\" (recommended) -- base_swaps and defi_tools are deprecated aliases that revoke the exact same full autonomous permission group." },
       },
       required: ["scope"],
       additionalProperties: false,

package/.openclaw/extensions/agent-wallet/index.ts

@@ -724,17 +724,17 @@ const walletSessionToolDefinitions = [
   },
   {
     name: "agentlayer_autonomous_status",
-    description: "Return AgentLayer high-trust autonomous permission status for the combined base_swaps + defi_tools permission group.",
+    description: "Return AgentLayer high-trust autonomous permission status. The autonomous permission group covers every wallet write tool (transfers, bridges, Solana swaps, staking, x402 payments, generic contract calls, Base swaps, and EVM DeFi management), not just base_swaps/defi_tools.",
     parameters: { type: "object", properties: {}, additionalProperties: false },
   },
   {
     name: "agentlayer_autonomous_approve",
     description:
-      "Enable high-trust autonomous execution for the combined permission group. The scope parameter is kept for compatibility; choosing base_swaps or defi_tools enables both Base Velora/Uniswap swaps and supported EVM DeFi management tools until revoked. This does not cover transfers, bridges, Solana swaps, or generic contract calls.",
+      "Enable the high-trust autonomous permission group. The scope parameter accepts \"all\" (recommended); base_swaps and defi_tools are deprecated aliases with identical effect. This covers 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 -- until revoked.",
     parameters: {
       type: "object",
       properties: {
-        scope: { type: "string", enum: ["base_swaps", "defi_tools"], description: "Compatibility scope; either value enables the full autonomous permission group." },
+        scope: { type: "string", enum: ["all", "base_swaps", "defi_tools"], description: "Scope to enable. Use \"all\" (recommended) -- base_swaps and defi_tools are deprecated aliases that enable the exact same full autonomous permission group." },
         purpose: { type: "string" },
         user_intent: { type: "boolean" },
       },
@@ -744,11 +744,11 @@ const walletSessionToolDefinitions = [
   },
   {
     name: "agentlayer_autonomous_revoke",
-    description: "Disable the full high-trust autonomous permission group. The scope parameter is kept for compatibility; either value revokes base_swaps and defi_tools together.",
+    description: "Disable the full high-trust autonomous permission group. The scope parameter accepts \"all\" (recommended); base_swaps and defi_tools are deprecated aliases that revoke the same full group.",
     parameters: {
       type: "object",
       properties: {
-        scope: { type: "string", enum: ["base_swaps", "defi_tools"], description: "Compatibility scope; either value revokes the full autonomous permission group." },
+        scope: { type: "string", enum: ["all", "base_swaps", "defi_tools"], description: "Scope to revoke. Use \"all\" (recommended) -- base_swaps and defi_tools are deprecated aliases that revoke the exact same full autonomous permission group." },
       },
       required: ["scope"],
       additionalProperties: false,

package/.openclaw/extensions/agent-wallet/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "agent-wallet",
   "name": "Agent Wallet",
   "description": "Official OpenClaw plugin bridge for the agent-wallet backends, including Solana, local BTC, and local EVM.",
-  "version": "0.1.89",
+  "version": "0.1.91",
   "contracts": {
     "tools": [
       "agentlayer_autonomous_approve",

package/.openclaw/extensions/agent-wallet/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agentlayertech/agent-wallet-plugin",
-  "version": "0.1.89",
+  "version": "0.1.91",
   "description": "OpenClaw plugin bridge for the AgentLayer wallet runtime.",
   "type": "module",
   "license": "SEE LICENSE IN ../../../LICENSE",

package/CHANGELOG.md

@@ -2,6 +2,20 @@
 
 ## Unreleased
 
+- Added a universal npm installer for OpenClaw, Codex, Claude Code, and Hermes.
+  `wallet install` now detects installed agent frameworks, supports explicit
+  `--hosts`, `--exclude`, and `--runtime-only` selection, and exposes
+  `wallet detect --json`. Runtime updates remain managed-only, so discovering a
+  new framework later does not silently enroll it. OpenClaw config creation is
+  now a host-specific step; wallet files and sealed secrets remain in their
+  existing `~/.openclaw` locations and are not replaced during updates.
+
+- Confirmed the native OS keystore as the default boot-key backend. `auto`
+  prefers macOS Keychain, Windows DPAPI, or Linux Secret Service and uses the
+  local `0600` file only as a fallback. The npm installer now warns macOS users
+  that the system may request Keychain confirmation; this does not rotate or
+  migrate the boot key during ordinary updates.
+
 - Hardened Morpho EVM operations with a 30% gas-limit buffer calculated from
   the exact final calldata immediately before sending. Morpho vault and market
   writes now wait for their final on-chain receipt and report reverts instead

package/README.md

@@ -6,23 +6,32 @@
 [![Node 24.x](https://img.shields.io/badge/node-24.x-339933?logo=node.js&logoColor=white)](https://nodejs.org/)
 [![docs](https://img.shields.io/badge/docs-agent--layer.tech-blue)](https://docs.agent-layer.tech/)
 
-For Openclaw:
+Install AgentLayer for the agent frameworks already present on the machine:
 
 ```bash
 npx @agentlayer.tech/wallet install --yes
 ```
 
-For Codex:
+The installer detects OpenClaw, Codex, Claude Code, and Hermes, installs the
+shared local runtime once, and connects every detected host. Without `--yes`,
+an interactive terminal asks about each detected host.
+
+To choose hosts explicitly:
 
 ```bash
-npx @agentlayer.tech/wallet install --yes && npx @agentlayer.tech/wallet codex install --yes
+npx @agentlayer.tech/wallet install --yes --hosts codex,claude-code
+npx @agentlayer.tech/wallet install --yes --hosts detected --exclude hermes
+npx @agentlayer.tech/wallet install --yes --runtime-only
+npx @agentlayer.tech/wallet detect --json
 ```
 
-For Claude Code:
+The legacy `wallet codex install`, `wallet claude-code install`, and
+`wallet hermes install` commands remain supported as explicit repair/install
+commands.
 
-```bash
-npx @agentlayer.tech/wallet install --yes && npx @agentlayer.tech/wallet claude-code install --yes
-```
+On a machine with an existing AgentLayer runtime, a plain `wallet install`
+touches only already-managed hosts. To enroll a framework installed later, run
+`wallet install --yes --hosts detected` or name it explicitly.
 
 Or install entirely from inside the Claude Code CLI, via the plugin marketplace
 (no terminal/npx needed) — two commands, then restart:
@@ -32,13 +41,6 @@ Or install entirely from inside the Claude Code CLI, via the plugin marketplace
 /plugin install agent-wallet@agentlayer
 ```
 
-For Hermes:
-
-```bash
-npx @agentlayer.tech/wallet install --yes && npx @agentlayer.tech/wallet hermes install --yes
-```
-
-
 AgentLayer is a beta local-first wallet and finance stack for agents.
 
 The repository includes:
@@ -72,7 +74,7 @@ System prerequisites:
 - `node` `24.x`
 - `npm`
 
-Install the local runtime:
+Install the local runtime and connect detected agent frameworks:
 
 ```bash
 npx @agentlayer.tech/wallet install --yes
@@ -102,13 +104,26 @@ The CLI uses a versioned runtime layout:
 ~/.openclaw/agent-wallet-runtime/current              # symlink → active release
 ```
 
-On first install, `--yes` generates local runtime secrets. The installer stores `master_key` and `approval_secret` in `~/.openclaw/sealed_keys.json`; the boot key needed to unlock that sealed bundle stays in the prompt-free local fallback by default. macOS Keychain is opt-in (`AGENT_WALLET_KEYSTORE_BACKEND=macos-keychain`) because probing it can open a system password dialog during install or startup.
+`~/.openclaw` remains the shared AgentLayer runtime root even when OpenClaw is
+not installed. A Codex-only or Claude-only install creates the runtime there
+but does not create or patch `openclaw.json`.
+
+On first install, `--yes` generates local runtime secrets. The installer stores
+`master_key` and `approval_secret` in `~/.openclaw/sealed_keys.json`. The boot
+key needed to unlock that sealed bundle uses `AGENT_WALLET_KEYSTORE_BACKEND=auto`
+by default: it prefers the native OS keystore and falls back to a local `0600`
+file only when the native backend is unavailable. On macOS this means the login
+Keychain (`service=ai.agentlayer.wallet`, `account=boot_key`). macOS may show a
+Keychain access or password confirmation depending on the current Keychain
+state; approve it only when you initiated the AgentLayer install or update.
+Existing installs keep the same boot-key value during upgrades.
 
 Useful CLI commands (require the global install above):
 
 ```bash
 wallet status                    # show active runtime version and health
 wallet doctor                    # diagnose common config problems
+wallet detect --json             # show detected and already-managed hosts
 wallet update --yes              # upgrade to the latest published version
 wallet update --yes --dry-run    # preview the upgrade without applying it
 wallet rollback                  # revert to the previous release
@@ -116,7 +131,14 @@ wallet hermes install --yes      # (re)connect Hermes to the current runtime
 wallet codex install --yes       # (re)connect Codex to the current runtime
 ```
 
-`wallet update --yes` fetches the latest npm package, installs it under `releases/<version>`, and flips the `current` symlink. Python and Node dependency snapshots are reused when the dependency fingerprint has not changed, so subsequent updates are fast. All frameworks that read from `current/` (Claude Code, Codex, Hermes) pick up the new code automatically on their next session start; OpenClaw requires a gateway restart to reload its TypeScript extension.
+`wallet update --yes` fetches the latest npm package, installs it under
+`releases/<version>`, and flips the `current` symlink. Updates repair only hosts
+already recorded as AgentLayer-managed; a newly detected framework is never
+silently enrolled during update. Python and Node dependency snapshots are
+reused when the dependency fingerprint has not changed, so subsequent updates
+are fast. All frameworks that read from `current/` (Claude Code, Codex, Hermes)
+pick up the new code automatically on their next session start; OpenClaw
+requires a gateway restart to reload its TypeScript extension.
 
 ## Native OpenClaw plugin installs
 
@@ -280,10 +302,10 @@ For the default Solana flow, run the installer directly:
 npx @agentlayer.tech/wallet install --yes
 ```
 
-That installs the runtime, patches the OpenClaw plugin config, generates local
+That installs the runtime, connects each detected framework, generates local
 runtime secrets when missing, and creates the first encrypted per-user Solana
-mainnet wallet. The agent receives the public address and guarded wallet tools,
-not the private key.
+mainnet wallet. `openclaw.json` is patched only when OpenClaw is selected. The
+agent receives the public address and guarded wallet tools, not the private key.
 
 BTC and EVM are separate host-side setup flows.
 
@@ -377,10 +399,11 @@ The installer then:
 - creates `agent-wallet/.env` from `agent-wallet/.env.example` if it does not exist
 - creates `agent-wallet/.runtime-venv` and installs the Python backend
 - installs Node dependencies for `wdk-btc-wallet`, `wdk-evm-wallet`, and `flash-sdk-bridge`
-- creates a minimal `~/.openclaw/openclaw.json` if one does not exist
 - if the required secrets are already present, writes or updates `~/.openclaw/sealed_keys.json`
-- if the required secrets are already present, patches `~/.openclaw/openclaw.json` to load the `agent-wallet` extension and point it at the installed runtime
-- `wallet hermes install --yes` additionally connects Hermes Agent to the same runtime without copying wallet tools or policy
+- detects OpenClaw, Codex, Claude Code, and Hermes before changing host config
+- connects the selected hosts to `agent-wallet-runtime/current`
+- creates or patches `~/.openclaw/openclaw.json` only when OpenClaw is selected
+- records non-secret ownership metadata so later updates repair only managed hosts
 
 When the installer reaches the final config step, the default plugin config is:
 

package/VERSION

@@ -1 +1 @@
-0.1.89
+0.1.91

package/agent-wallet/README.md

@@ -138,7 +138,20 @@ If you want a simpler local setup flow, use the installer:
 sh ../setup.sh
 ```
 
-If you already use a local coding agent on the same machine, it can run this installer for you. You can simply ask the agent to install the wallet, and it can perform the file setup, Python setup, and OpenClaw config patching steps automatically.
+The public npm entrypoint is a universal host orchestrator:
+
+```bash
+npx @agentlayer.tech/wallet install --yes
+npx @agentlayer.tech/wallet install --yes --hosts codex,claude-code
+npx @agentlayer.tech/wallet detect --json
+```
+
+It detects OpenClaw, Codex, Claude Code, and Hermes before installation. The
+direct `setup.sh`/Python path retains its OpenClaw-oriented default for
+backward compatibility; the npm CLI passes `--no-configure-openclaw` and lets
+the selected OpenClaw host adapter own `openclaw.json`.
+
+If you already use a local coding agent on the same machine, it can run this installer for you. You can simply ask the agent to install the wallet, and it can perform the file setup, Python setup, and selected host-bridge setup automatically.
 
 By default it will:
 
@@ -562,6 +575,18 @@ That native plugin package is additive. Keep the existing runtime installer for
 npx @agentlayer.tech/wallet install --yes
 ```
 
+To bind a welcome invite from `https://www.agent-layer.tech/onboard` to the
+local Base address during installation:
+
+```bash
+npx @agentlayer.tech/wallet install --yes --invite alw_...
+```
+
+The installer sends only the one-time invite and the public EVM address to the
+AgentLayer onboarding API. It never sends a private key, seed, wallet password,
+local user ID, or telemetry install ID. A network or EVM provisioning failure
+does not consume the invite and does not roll back the wallet installation.
+
 The ClawHub plugin package auto-checks `~/.openclaw/agent-wallet-runtime/current/agent-wallet` before it falls back to a local workspace checkout.
 
 Public-safe helper scripts are available in `agent-wallet/scripts/`:

package/agent-wallet/UPGRADE_COMPATIBILITY.md

@@ -20,8 +20,9 @@ Raising the floor requires all of the following:
 
 | Path | Purpose | Removal condition |
 |---|---|---|
-| JavaScript boot-key fallback | Updates runtimes that predate the verified Python installer resolver. | The supported floor includes `resolve_boot_key_for_installer`, and direct-upgrade fixtures no longer require the fallback. |
+| JavaScript boot-key fallback | Updates runtimes that predate the verified Python installer resolver. | The supported floor no longer includes releases without `resolve_boot_key_for_installer`; until then, isolated CI upgrades the published `0.1.53` package to the packed candidate and verifies boot-key, sealed-bundle, wallet-file, and address identity. |
 | Directory runtime-pointer migration | Converts pre-versioned `current/` directories into release entries. | The supported floor guarantees symlink-based runtime pointers. |
+| OpenClaw legacy adoption | Recognizes an AgentLayer entry whose package or extension path belongs to the active runtime home. | The supported floor guarantees an `integrations.json` OpenClaw ownership entry. |
 | Hermes legacy adoption | Recognizes an AgentLayer plugin installed before the ownership registry. | The supported floor guarantees an `integrations.json` Hermes ownership entry. |
 | Codex legacy adoption | Recognizes a matching local marketplace registration and AgentLayer manifest. | The supported floor guarantees an `integrations.json` Codex ownership entry. |
 | Claude Code legacy adoption | Recognizes the AgentLayer marketplace and plugin manifest before registry ownership. | The supported floor guarantees an `integrations.json` Claude Code ownership entry. |

package/agent-wallet/agent_wallet/__init__.py

@@ -2,7 +2,7 @@
 
 # Keep in sync with package.json, pyproject.toml, and the npm installer version.
 # scripts/check_release_version.mjs enforces this on release.
-__version__ = "0.1.89"
+__version__ = "0.1.91"
 
 __all__ = [
     "config",

package/agent-wallet/agent_wallet/autonomous_permissions.py

@@ -34,7 +34,13 @@ DEFI_TOOLS = frozenset(
     }
 )
 DEFI_TOOLS_ISSUER = "autonomous-permission:defi-tools"
-SUPPORTED_SCOPES = frozenset({BASE_SWAP_SCOPE, DEFI_TOOLS_SCOPE})
+ALL_TOOLS_ISSUER = "autonomous-permission:all-tools"
+#: Canonical scope name -- the group covers every wallet write tool (see
+#: authorize_operation), not just Base swaps or EVM DeFi. base_swaps/
+#: defi_tools remain accepted as deprecated aliases with identical effect,
+#: for backward compatibility with existing callers.
+ALL_SCOPE = "all"
+SUPPORTED_SCOPES = frozenset({ALL_SCOPE, BASE_SWAP_SCOPE, DEFI_TOOLS_SCOPE})
 _PERMISSIONS_FILENAME = "autonomous_permissions.json"
 
 
@@ -213,6 +219,42 @@ def authorize_base_swap(*, tool_name: str, network: str, summary: dict[str, Any]
     )
 
 
+def is_autonomous_approved() -> bool:
+    """Whether the combined high-trust autonomous permission group is active.
+
+    Same underlying flag as :func:`is_base_swap_approved` /
+    :func:`is_defi_tools_approved`; exposed under a name that doesn't imply a
+    narrower scope, for callers that gate every wallet tool rather than just
+    Base swaps or EVM DeFi tools.
+    """
+    return bool(status()["active"])
+
+
+def authorize_operation(*, tool_name: str, network: str, summary: dict[str, Any]) -> str:
+    """Issue an internal approval token for any wallet tool/network once the
+    combined high-trust autonomous permission group is enabled.
+
+    Unlike :func:`authorize_base_swap` / :func:`authorize_defi_tool`, this has
+    no per-tool or per-network allow-list -- the group toggle enabled by
+    ``agentlayer_autonomous_approve`` is the only gate. Callers are expected to
+    have already built ``summary`` from a live preview/quote, matching every
+    other execute path's binding contract.
+    """
+    if not is_autonomous_approved():
+        raise WalletBackendError(
+            "Autonomous execution is not enabled. Ask the user to run "
+            "agentlayer_autonomous_approve first."
+        )
+    return issue_approval_token(
+        tool_name=str(tool_name),
+        network=str(network or "").strip().lower(),
+        summary=summary,
+        mainnet_confirmed=True,
+        ttl_seconds=120,
+        issued_by=ALL_TOOLS_ISSUER,
+    )
+
+
 def authorize_defi_tool(*, tool_name: str, network: str, summary: dict[str, Any]) -> str:
     """Issue an internal approval token for one exact EVM DeFi operation."""
     normalized_network = str(network or "").strip().lower()