@thirdfy/agent-cli 0.2.2 → 0.2.4

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.
package/CHANGELOG.md CHANGED
@@ -4,6 +4,18 @@ All notable changes to `@thirdfy/agent-cli` are documented here. The format is b
4
4
 
5
5
  ## [Unreleased]
6
6
 
7
+ ## [0.2.4] - 2026-05-28
8
+
9
+ ### Changed
10
+
11
+ - Hyperliquid docs: `complete_hyperliquid_onboarding` as the preferred runtime-owned setup action; clarify separated Hyperliquid main wallet vs managed API/execution wallet params (`mainWalletAddress`, `apiWalletAddress`, order `userAddress`).
12
+
13
+ ## [0.2.3] - 2026-05-26
14
+
15
+ ### Added
16
+
17
+ - Hyperliquid and Polymarket `recoveryActions` and `decommissionExample` in `providerHints` for fund recovery before runtime delete (pairs with Thirdfy API v3.4.42+).
18
+
7
19
  ## [0.2.2] - 2026-05-23
8
20
 
9
21
  ### Changed
package/README.md CHANGED
@@ -40,12 +40,15 @@ Run without global install:
40
40
  npx @thirdfy/agent-cli --help
41
41
  ```
42
42
 
43
- ## What's new in v0.2.2
43
+ ## What's new in v0.2.4
44
44
 
45
- - **npm README cleanup** the registry homepage is user-facing again: one **What's new** section for the current version, full history in [CHANGELOG.md](./CHANGELOG.md) (no multi-version release wall or maintainer publish steps on npm).
46
- - **Public docs validation** `npm run validate:public-docs` enforces README/npm surface rules before publish.
45
+ - Hyperliquid setup docs now lead with `complete_hyperliquid_onboarding` for runtime-owned Li.Fi, Bridge2, and approval steps.
46
+ - Clarified the separated Hyperliquid wallet model: pass `mainWalletAddress` / order `userAddress` for the funded HL account and `apiWalletAddress` for the managed execution/API wallet when they differ.
47
+ - Operator previews still use `get_hyperliquid_onboarding_plan` and `prepare_hyperliquid_onboarding`.
47
48
 
48
- Older highlights (Commander routing, stricter flags): see [CHANGELOG.md](./CHANGELOG.md) · [GitHub Releases](https://github.com/thirdfy/agent-cli/releases).
49
+ Older versions: [CHANGELOG.md](./CHANGELOG.md) and [GitHub Releases](https://github.com/thirdfy/agent-cli/releases).
50
+
51
+ Older versions: [CHANGELOG.md](./CHANGELOG.md) and [GitHub Releases](https://github.com/thirdfy/agent-cli/releases).
49
52
 
50
53
  ## Quick start
51
54
 
@@ -180,7 +183,7 @@ Auth expectations by mode:
180
183
  - `hybrid`: requires execution identity and governed mirror semantics (`--hybrid-wallet-mode self|agent_wallet`, default `self`).
181
184
  - `thirdfy`: requires execution identity and delegated governance path.
182
185
  - `agent_wallet`: requires execution identity and owner `userDid`, but does not require subscriber delegation when the owner identity matches the agent wallet/creator. Thirdfy credits/free quota still gate execution; Privy gas sponsorship only covers network gas when enabled.
183
- - Hyperliquid Bridge2 setup is the Arbitrum exception to the Base-focused `agent_wallet` rule: Bridge2 credits the transaction sender. Pass **`--estimated-amount-usd`** as a top-level flag (not inside `--params`). When USDC sits on your linked email-login wallet (`primaryEvmWallet`) instead of the managed execution wallet, Thirdfy API returns **`FUND_AGENT_EXECUTION_WALLET`** / **`MANUAL_BRIDGE2_DEPOSIT_REQUIRED`** with `fundedWallet` and `executionWalletAddress`; move native Arbitrum USDC to `executionWalletAddress` and retry.
186
+ - Hyperliquid setup uses `complete_hyperliquid_onboarding` for runtime-owned funding/setup. It can submit Li.Fi and Bridge2 steps automatically, then return `bridge2_submitted` while Hyperliquid credits the deposit. Bridge2 setup is the Arbitrum exception to the Base-focused `agent_wallet` rule: Bridge2 credits the transaction sender. Pass **`--estimated-amount-usd`** as a top-level flag (not inside `--params`). The normal solo `agent_wallet` path uses the managed execution wallet as the Hyperliquid main wallet. If margin already sits on a different Hyperliquid main wallet, pass that wallet as `mainWalletAddress` / order `userAddress`, and pass the approved execution/API wallet as `apiWalletAddress`. When USDC sits on your linked email-login wallet (`primaryEvmWallet`) instead of the managed execution wallet, Thirdfy API returns **`FUND_AGENT_EXECUTION_WALLET`** / **`MANUAL_BRIDGE2_DEPOSIT_REQUIRED`** with `fundedWallet` and `executionWalletAddress`; move native Arbitrum USDC to `executionWalletAddress` and retry.
184
187
  - custody mode defaults are profile-aware:
185
188
  - `managed` default for `thirdfy`
186
189
  - `external` default for `self` and `hybrid`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@thirdfy/agent-cli",
3
- "version": "0.2.2",
3
+ "version": "0.2.4",
4
4
  "description": "Thirdfy Agent CLI for onboarding, governance preflight, execute-intent, and status polling.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -61,6 +61,12 @@ export function createProviderHints({ getNegotiatedCapabilitiesCache }) {
61
61
  'get_hyperliquid_builder_fee_status',
62
62
  'get_hyperliquid_referral_status',
63
63
  ],
64
+ recoveryActions: [
65
+ 'get_hyperliquid_user_state',
66
+ 'withdraw_hyperliquid_to_arbitrum',
67
+ ],
68
+ decommissionExample:
69
+ 'get_hyperliquid_user_state -> withdraw_hyperliquid_to_arbitrum -> withdraw-to-user on execution wallet',
64
70
  credentialType: 'hyperliquid_api_wallet',
65
71
  credentialUx:
66
72
  'Thirdfy manages Hyperliquid API-wallet setup for normal users. Delegated writes require encrypted privateKey-backed hyperliquid_api_wallet credentials; walletAddress-only records are rejected until Privy walletId-backed Hyperliquid signing ships.',
@@ -168,7 +174,17 @@ export function createProviderHints({ getNegotiatedCapabilitiesCache }) {
168
174
  'browser_setup:create_or_derive_clob_credentials',
169
175
  'browser_setup:deploy_deposit_wallet_and_set_approvals',
170
176
  ],
171
- statusActions: ['get_polymarket_setup_status'],
177
+ statusActions: [
178
+ 'get_polymarket_funding_status',
179
+ 'get_polymarket_setup_status',
180
+ 'get_polymarket_recovery_status',
181
+ ],
182
+ recoveryActions: [
183
+ 'get_polymarket_recovery_status',
184
+ 'withdraw_polymarket_collateral',
185
+ ],
186
+ decommissionExample:
187
+ 'get_polymarket_recovery_status -> withdraw_polymarket_collateral -> withdraw-to-user',
172
188
  credentialType: 'polymarket_clob',
173
189
  credentialUx:
174
190
  'Autonomous agents use an agent-owned Privy wallet and Polymarket deposit wallet first: Thirdfy creates the agent wallet, deploys/approves the deposit wallet, and stores encrypted CLOB credentials once Polymarket key creation is available. User-owned browser setup remains optional for interactive capital.',