@agentlayer.tech/wallet 0.1.53 → 0.1.58

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (31) hide show
  1. package/.openclaw/extensions/agent-wallet/openclaw.plugin.json +1 -1
  2. package/.openclaw/extensions/agent-wallet/package.json +1 -1
  3. package/CHANGELOG.md +63 -0
  4. package/README.md +14 -12
  5. package/VERSION +1 -1
  6. package/agent-wallet/.env.example +1 -0
  7. package/agent-wallet/agent_wallet/__init__.py +1 -1
  8. package/agent-wallet/agent_wallet/config.py +9 -0
  9. package/agent-wallet/agent_wallet/openclaw_cli.py +95 -39
  10. package/agent-wallet/agent_wallet/openclaw_runtime.py +8 -3
  11. package/agent-wallet/agent_wallet/providers/jupiter.py +34 -0
  12. package/agent-wallet/agent_wallet/user_wallets.py +46 -3
  13. package/agent-wallet/agent_wallet/wallet_layer/solana.py +34 -8
  14. package/agent-wallet/openclaw.plugin.json +1 -1
  15. package/agent-wallet/pyproject.toml +1 -1
  16. package/claude-code/plugins/agent-wallet/.claude-plugin/plugin.json +1 -1
  17. package/claude-code/plugins/agent-wallet/README.md +9 -3
  18. package/claude-code/plugins/agent-wallet/commands/agentlayer-autonomous-approve.md +17 -2
  19. package/claude-code/plugins/agent-wallet/commands/agentlayer-autonomous-revoke.md +1 -0
  20. package/claude-code/plugins/agent-wallet/commands/wallet-base.md +37 -0
  21. package/claude-code/plugins/agent-wallet/commands/wallet-ethereum.md +37 -0
  22. package/claude-code/plugins/agent-wallet/commands/wallet-evm.md +38 -0
  23. package/claude-code/plugins/agent-wallet/commands/wallet-sol.md +30 -0
  24. package/codex/plugins/agent-wallet/.codex-plugin/plugin.json +1 -1
  25. package/codex/plugins/agent-wallet/README.md +9 -0
  26. package/codex/plugins/agent-wallet/server.py +427 -6
  27. package/codex/plugins/agent-wallet/skills/wallet-sol/SKILL.md +29 -0
  28. package/hermes/plugins/agent_wallet/plugin.yaml +1 -1
  29. package/package.json +1 -1
  30. package/wdk-btc-wallet/package.json +1 -1
  31. package/wdk-evm-wallet/package.json +1 -1
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "agent-wallet",
3
3
  "displayName": "Agent Wallet",
4
- "version": "0.1.53",
4
+ "version": "0.1.58",
5
5
  "description": "Claude Code bridge for the existing AgentLayer wallet runtime. Connects to Solana, Bitcoin, and EVM wallets without creating a new one.",
6
6
  "author": {
7
7
  "name": "AgentLayer"
@@ -51,11 +51,17 @@ no-op once the backend is healthy.
51
51
  - `/wallet-setup` — install (or repair) the backend explicitly instead of
52
52
  waiting for the hook (requires `/reload-plugins` first so the command is
53
53
  registered).
54
+ - `/wallet-sol` — print the current Solana wallet overview directly in chat.
55
+ - `/wallet-evm` — print the wallet overview for the current/default EVM network
56
+ directly in chat.
57
+ - `/wallet-base` — print the Base EVM wallet overview directly in chat.
58
+ - `/wallet-ethereum` — print the Ethereum EVM wallet overview directly in chat.
54
59
  - `/agentlayer-autonomous-approve` — enable high-trust autonomous Base swaps
55
60
  (`swap_evm_tokens` / `swap_evm_uniswap_tokens` on Base only) without
56
- per-transaction approvals.
57
- - `/agentlayer-autonomous-revoke` disable that autonomous Base swap
58
- permission.
61
+ per-transaction approvals. In Claude Code this command now asks for an
62
+ explicit in-command confirmation before enabling the standing permission.
63
+ - `/agentlayer-autonomous-revoke` — disable the combined autonomous permission
64
+ group for Base swaps and supported EVM DeFi tools.
59
65
  - `AGENT_WALLET_AUTO_BOOTSTRAP=0` — opt out of the auto-install: the
60
66
  `SessionStart` hook then only reminds you to run `/wallet-setup` instead of
61
67
  installing the backend itself.
@@ -1,11 +1,24 @@
1
1
  ---
2
2
  description: Enable AgentLayer autonomous Base swaps and EVM DeFi tools without per-transaction approvals.
3
- allowed-tools: mcp__agent_wallet__agentlayer_autonomous_approve, mcp__agent_wallet__agentlayer_autonomous_status
3
+ allowed-tools: AskUserQuestion, mcp__agent_wallet__agentlayer_autonomous_approve, mcp__agent_wallet__agentlayer_autonomous_status
4
+ disable-model-invocation: true
4
5
  ---
5
6
 
6
7
  Enable the high-trust autonomous AgentLayer permission group.
7
8
 
8
- Call `agentlayer_autonomous_approve` with:
9
+ First call `agentlayer_autonomous_status`.
10
+
11
+ If both `base_swaps` and `defi_tools` are already enabled, report that the combined autonomous permission group is already active and remind the user that `/agentlayer-autonomous-revoke` disables it.
12
+
13
+ Otherwise, use `AskUserQuestion` to confirm:
14
+
15
+ - header: `Autonomy`
16
+ - question: `Enable AgentLayer autonomous Base swaps and EVM DeFi tools without per-transaction approvals?`
17
+ - options:
18
+ - `Enable` — `Turns on the combined autonomous permission group until revoked.`
19
+ - `Cancel` — `Leaves per-transaction approvals in place and does not change permissions.`
20
+
21
+ Only if the user selects `Enable`, call `agentlayer_autonomous_approve` with:
9
22
 
10
23
  ```json
11
24
  {
@@ -17,6 +30,8 @@ Call `agentlayer_autonomous_approve` with:
17
30
 
18
31
  Then call `agentlayer_autonomous_status` and report whether both `base_swaps` and `defi_tools` are enabled.
19
32
 
33
+ If the user selects `Cancel`, do not call any write tool. State that autonomous permissions were not changed.
34
+
20
35
  Be explicit in the response:
21
36
 
22
37
  - This removes per-transaction approvals for Base Velora/Uniswap swap execute calls and supported EVM DeFi management tools.
@@ -1,6 +1,7 @@
1
1
  ---
2
2
  description: Disable AgentLayer autonomous Base swaps and EVM DeFi tools.
3
3
  allowed-tools: mcp__agent_wallet__agentlayer_autonomous_revoke, mcp__agent_wallet__agentlayer_autonomous_status
4
+ disable-model-invocation: true
4
5
  ---
5
6
 
6
7
  Disable the full high-trust autonomous AgentLayer permission group.
@@ -0,0 +1,37 @@
1
+ ---
2
+ description: Show the connected EVM wallet overview for Base directly in chat.
3
+ allowed-tools: mcp__agent_wallet__get_wallet_overview
4
+ disable-model-invocation: true
5
+ ---
6
+
7
+ Show the connected EVM wallet overview for Base directly in chat.
8
+
9
+ 1. Call `get_wallet_overview` with:
10
+
11
+ ```json
12
+ {
13
+ "backend": "evm",
14
+ "network": "base"
15
+ }
16
+ ```
17
+
18
+ 2. Format the response as a compact wallet report:
19
+
20
+ - state the wallet as `EVM (Base)`
21
+ - include `chain`, `network` (or `requested_network`), `address`, and `total_value_usd` when present
22
+ - render a Markdown table with columns: `Asset | Type | Amount | USD Value`
23
+ - use `assets` when present
24
+ - for each asset row, prefer:
25
+ - asset label: `symbol`, then `token_address`, then `asset_type`
26
+ - amount: `amount_ui`, then `balance_ui`, then `balance_native`, then `amount_raw`
27
+ - usd value: `value_usd`, then `balance_usd`
28
+ - omit zero-value rows only when both the amount and USD value are clearly zero
29
+ - if no asset rows are available, still report the native balance summary in prose
30
+
31
+ 3. After the table, add one short metadata line with any available sources:
32
+
33
+ - `source`
34
+ - `token_discovery_source`
35
+ - `pricing_source`
36
+
37
+ 4. Do not suggest transfers, swaps, or other write actions unless the user explicitly asks for them.
@@ -0,0 +1,37 @@
1
+ ---
2
+ description: Show the connected EVM wallet overview for Ethereum directly in chat.
3
+ allowed-tools: mcp__agent_wallet__get_wallet_overview
4
+ disable-model-invocation: true
5
+ ---
6
+
7
+ Show the connected EVM wallet overview for Ethereum directly in chat.
8
+
9
+ 1. Call `get_wallet_overview` with:
10
+
11
+ ```json
12
+ {
13
+ "backend": "evm",
14
+ "network": "ethereum"
15
+ }
16
+ ```
17
+
18
+ 2. Format the response as a compact wallet report:
19
+
20
+ - state the wallet as `EVM (Ethereum)`
21
+ - include `chain`, `network` (or `requested_network`), `address`, and `total_value_usd` when present
22
+ - render a Markdown table with columns: `Asset | Type | Amount | USD Value`
23
+ - use `assets` when present
24
+ - for each asset row, prefer:
25
+ - asset label: `symbol`, then `token_address`, then `asset_type`
26
+ - amount: `amount_ui`, then `balance_ui`, then `balance_native`, then `amount_raw`
27
+ - usd value: `value_usd`, then `balance_usd`
28
+ - omit zero-value rows only when both the amount and USD value are clearly zero
29
+ - if no asset rows are available, still report the native balance summary in prose
30
+
31
+ 3. After the table, add one short metadata line with any available sources:
32
+
33
+ - `source`
34
+ - `token_discovery_source`
35
+ - `pricing_source`
36
+
37
+ 4. Do not suggest transfers, swaps, or other write actions unless the user explicitly asks for them.
@@ -0,0 +1,38 @@
1
+ ---
2
+ description: Show the connected EVM wallet overview for the current/default EVM network directly in chat.
3
+ allowed-tools: mcp__agent_wallet__get_wallet_overview
4
+ disable-model-invocation: true
5
+ ---
6
+
7
+ Show the connected EVM wallet overview directly in chat.
8
+
9
+ 1. Call `get_wallet_overview` with:
10
+
11
+ ```json
12
+ {
13
+ "backend": "evm"
14
+ }
15
+ ```
16
+
17
+ 2. Format the response as a compact wallet report:
18
+
19
+ - state the wallet as `EVM`
20
+ - include `chain`, the active/default EVM network (`network` or `requested_network`), `address`, and `total_value_usd` when present
21
+ - render a Markdown table with columns: `Asset | Type | Amount | USD Value`
22
+ - use `assets` when present
23
+ - for each asset row, prefer:
24
+ - asset label: `symbol`, then `token_address`, then `asset_type`
25
+ - amount: `amount_ui`, then `balance_ui`, then `balance_native`, then `amount_raw`
26
+ - usd value: `value_usd`, then `balance_usd`
27
+ - omit zero-value rows only when both the amount and USD value are clearly zero
28
+ - if no asset rows are available, still report the native balance summary in prose
29
+
30
+ 3. After the table, add one short metadata line with any available sources:
31
+
32
+ - `source`
33
+ - `token_discovery_source`
34
+ - `pricing_source`
35
+
36
+ 4. Be explicit that this command shows one EVM network at a time: the active/default network returned in the overview payload.
37
+
38
+ 5. Do not suggest transfers, swaps, or other write actions unless the user explicitly asks for them.
@@ -0,0 +1,30 @@
1
+ ---
2
+ description: Show the connected Solana wallet portfolio directly in chat.
3
+ allowed-tools: mcp__agent_wallet__get_wallet_portfolio
4
+ disable-model-invocation: true
5
+ ---
6
+
7
+ Show the connected Solana wallet portfolio directly in chat.
8
+
9
+ 1. Call `get_wallet_portfolio` with:
10
+
11
+ ```json
12
+ {}
13
+ ```
14
+
15
+ 2. Format the response as a compact wallet report:
16
+
17
+ - state the wallet as `Solana`
18
+ - include `chain`, `network` (or `requested_network` when `network` is absent), `address`, and `total_value_usd` when present
19
+ - render a Markdown table with columns: `Asset | Type | Amount | USD Value`
20
+ - use `assets` when present
21
+ - for each asset row, prefer:
22
+ - asset label: `symbol`, then `name`, then `mint`, then `token_address`, then `asset_type`
23
+ - when the label came from `symbol`/`name` (not the mint/token_address itself) and a `mint` or `token_address` is present, append it shortened in parentheses next to the label as `first6…last4` (e.g. `USDC (EPjFWd…TDt1v)`) — keep the contract visible but compact, never show it twice
24
+ - amount: `amount_ui`, then `balance_ui`, then `balance_native`, then `amount_raw`
25
+ - usd value: `value_usd`, then `balance_usd`
26
+ - omit zero-value rows only when both the amount and USD value are clearly zero
27
+ - if no asset rows are available, still report the native balance summary in prose
28
+ - do not include source metadata lines or footer fields such as `source`, `token_discovery_source`, `pricing_source`, or `pricing_errors`
29
+
30
+ 3. Do not suggest transfers, swaps, or other write actions unless the user explicitly asks for them.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "agent-wallet",
3
- "version": "0.1.53",
3
+ "version": "0.1.58",
4
4
  "description": "Codex plugin bridge for the AgentLayer wallet runtime.",
5
5
  "author": {
6
6
  "name": "AgentLayer"
@@ -21,6 +21,8 @@ Primary design rules:
21
21
  - session wallet selection with `set_wallet_backend`
22
22
  - EVM network selection with `set_evm_network`
23
23
  - auto-managed approval binding for `preview -> execute` write flows
24
+ - bundled Codex skills, including `wallet-sol` for showing the Solana wallet
25
+ portfolio directly in chat
24
26
 
25
27
  ## Runtime requirements
26
28
 
@@ -28,6 +30,13 @@ Primary design rules:
28
30
  - keep the local wallet files and `~/.openclaw/sealed_keys.json` in place
29
31
  - use `wallet codex install --yes` to install this plugin into Codex
30
32
 
33
+ ## Bundled skill
34
+
35
+ After `wallet codex install --yes` and a Codex restart, the plugin ships a
36
+ bundled `wallet-sol` skill. In Codex you can invoke it from the slash menu or
37
+ explicitly as `$wallet-sol` to render the connected Solana wallet portfolio as a
38
+ compact chat table.
39
+
31
40
  ## Path resolution
32
41
 
33
42
  The bridge resolves the wallet runtime from: