openany-cli-dev 0.1.0 → 0.1.2
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/README.md +72 -61
- package/package.json +1 -1
- package/skills/openany/SKILL.md +17 -330
- package/skills/openany/SKILL.zh-CN.md +2 -2
- package/skills/openany/calls.md +116 -0
- package/skills/openany/setup.md +225 -0
- package/skills/openany/topups.md +70 -0
- package/skills/openany-provider/SKILL.md +12 -12
- package/skills/openany-provider/SKILL.zh-CN.md +10 -10
- package/skills/openany-provider/references/apis.md +12 -12
- package/skills/openany-provider/references/apis.zh-CN.md +55 -0
- package/skills/openany-provider/references/application.md +2 -2
- package/skills/openany-provider/references/application.zh-CN.md +2 -2
- package/skills/openany-provider/references/auth.md +1 -57
- package/skills/openany-provider/references/auth.zh-CN.md +3 -0
- package/skills/openany-provider/references/connections.md +17 -19
- package/skills/openany-provider/references/connections.zh-CN.md +23 -20
- package/skills/openany-provider/references/imports.md +42 -23
- package/skills/openany-provider/references/imports.zh-CN.md +37 -35
- package/skills/openany-provider/references/listing.md +6 -6
- package/skills/openany-provider/references/listing.zh-CN.md +11 -0
- package/skills/openany-provider/references/login.md +19 -20
- package/skills/openany-provider/references/login.zh-CN.md +15 -17
- package/skills/openany-provider/references/model-import.md +11 -0
- package/skills/openany-provider/references/model-import.zh-CN.md +2 -3
- package/skills/openany-provider/references/models.zh-CN.md +68 -0
- package/skills/openany-provider/references/publishing.md +20 -63
- package/skills/openany-provider/references/publishing.zh-CN.md +17 -58
- package/skills/openany-provider/references/reviews.zh-CN.md +20 -0
- package/skills/openany-provider/templates/seller-agent-api-import-template.json +10 -27
- package/src/cli.js +4 -0
- package/src/http.js +2 -1
- package/src/native/connection-macos.js +10 -10
- package/src/native/setup-macos.js +10 -10
- package/src/tasks.js +53 -0
package/README.md
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
# OpenAny CLI
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
OpenAny CLI is a standalone Node.js CLI that provides access to OpenAny models, aggregated data and tools, identity, API key management, and top-ups through a single `openany-dev` command. Standard calls require only an API key. If the key is missing, the CLI fails locally before sending an HTTP request.
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
The backend and signing origin are fixed at `https://dev.openany.si`. Model calls use the `https://api-dev.openany.si` gateway and take their paths and query parameters from the public catalog's `curlExample`.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
The skill is available in [Chinese](skills/openany/SKILL.zh-CN.md) and [English](skills/openany/SKILL.md). Both entries and the English task guides ship with the npm package.
|
|
8
8
|
|
|
9
|
-
##
|
|
9
|
+
## Installation
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
Node.js 22 or later is required. Install from npm to make the `openany-dev` command available globally:
|
|
12
12
|
|
|
13
13
|
```bash
|
|
14
14
|
npm install -g openany-cli-dev@latest --registry=https://registry.npmjs.org/
|
|
@@ -16,9 +16,9 @@ openany-dev --version
|
|
|
16
16
|
openany-dev --help
|
|
17
17
|
```
|
|
18
18
|
|
|
19
|
-
|
|
19
|
+
The npm package is `openany-cli-dev`, and the command is `openany-dev`. The package includes the entry and task guides in `skills/openany`. Run `npm root -g` to locate the global installation directory, then install `openany-cli-dev/skills/openany` from that directory into your agent's skill directory. Update the skill whenever you update the CLI.
|
|
20
20
|
|
|
21
|
-
|
|
21
|
+
To develop from source or build a local installation package, run:
|
|
22
22
|
|
|
23
23
|
```bash
|
|
24
24
|
npm ci
|
|
@@ -26,32 +26,32 @@ npm test
|
|
|
26
26
|
npm pack
|
|
27
27
|
```
|
|
28
28
|
|
|
29
|
-
##
|
|
29
|
+
## Native credential setup dialogs
|
|
30
30
|
|
|
31
|
-
macOS
|
|
31
|
+
On macOS and Windows desktops, choose one of these commands to open the API key or wallet dialog:
|
|
32
32
|
|
|
33
33
|
```bash
|
|
34
34
|
openany-dev setup --api_key api_key --gui -j
|
|
35
35
|
openany-dev setup --wallet_connect wallet --gui -j
|
|
36
36
|
```
|
|
37
37
|
|
|
38
|
-
API
|
|
38
|
+
In the API key dialog, enter a label and key, then choose whether to activate it. In the wallet dialog, enter the agent ID and private key. The CLI derives the address locally and asks the user to confirm it. The dialog sends input to the CLI through a subprocess pipe, and stdout contains only the setup result. Agents must avoid reading or taking screenshots of the input fields while the user fills them in.
|
|
39
39
|
|
|
40
|
-
|
|
40
|
+
Canceling or reaching the five-minute timeout discards the input. Saving uses the existing configuration lock and atomic writes. Environment variables still take precedence over local settings. macOS uses the system AppKit, and Windows uses PowerShell and WinForms. Both work without a browser or compiler. Windows uses a directory ACL restricted to the current user. macOS uses mode 0700 for the directory and 0600 for the file. Programs running under the same account can still read local files if they have read access.
|
|
41
41
|
|
|
42
|
-
`--gui`
|
|
42
|
+
`--gui` supports `-j` and invocation without a TTY for API key and wallet setup. If the desktop is unavailable or system policy blocks scripts, remove `--gui` and let the user configure credentials in their own interactive terminal. Email and top-up setup, `--prepare`, and `--non-interactive` are unavailable in native dialogs. CLI checks behave as before when `--gui` is omitted.
|
|
43
43
|
|
|
44
|
-
##
|
|
44
|
+
## Making API calls
|
|
45
45
|
|
|
46
|
-
|
|
46
|
+
On first use, run interactive setup in your terminal:
|
|
47
47
|
|
|
48
48
|
```bash
|
|
49
49
|
openany-dev setup
|
|
50
50
|
```
|
|
51
51
|
|
|
52
|
-
|
|
52
|
+
Select the API calls option, enter a key label and the API key using masked input, then choose whether to make it the active key. Run `openany-dev setup --api_key api_key` to open this option directly. When updating an existing configuration, press Enter to keep the current value or enter a new value to replace it. The prompt indicates when a sensitive value is already configured without displaying it. Setup reads and writes local files only. Canceling discards the changes.
|
|
53
53
|
|
|
54
|
-
|
|
54
|
+
Set `OPENANY_DEV_API_KEY` in the agent's secure credential environment. You can also run `openany-dev keys add --label main --activate` in a terminal and enter an existing key using masked input. If the key is already set in the environment, the command saves it directly. For unattended setup, pass the key through secure standard input with `--stdin` and keep it out of command arguments and logs.
|
|
55
55
|
|
|
56
56
|
```bash
|
|
57
57
|
openany-dev status_check api_key -j
|
|
@@ -61,7 +61,7 @@ openany-dev inspect --id API_ID -j
|
|
|
61
61
|
openany-dev run --id API_ID --query '{"limit":"10"}' -j
|
|
62
62
|
```
|
|
63
63
|
|
|
64
|
-
|
|
64
|
+
Use the API ID and parameters from the live catalog. `status` checks local configuration and reports `configured/missing` without testing network access or key validity. Configure a key before proceeding with authenticated discovery or inspection. Use `discover --public` when the user explicitly requests public catalog browsing only.
|
|
65
65
|
|
|
66
66
|
`run --headers` accepts `Accept` and `Accept-Language` even when they are absent from the published inputs. Header names are case-insensitive. Published constraints still apply when these headers are declared; other unknown headers and reserved headers remain rejected.
|
|
67
67
|
|
|
@@ -69,9 +69,20 @@ API_ID 和参数必须依据实时目录。`status` 只检查本地配置,读
|
|
|
69
69
|
openany-dev run --id API_ID --headers '{"Accept":"application/json;version=20230203","Accept-Language":"zh-CN"}' -j
|
|
70
70
|
```
|
|
71
71
|
|
|
72
|
-
|
|
72
|
+
Balance checks use `GET /api/v1/agent-api-account` with a Bearer API key. This works with both wallet and email account keys. `run` reads the API contract, validates parameters, checks the balance, and calls the gateway. `calls list/get` retrieves model, data, and tool API usage records for the current key and requires a backend version that includes this fix. Status filters accept only `--status success` or `--status failed`. Passing `--review-required` produces a local error.
|
|
73
73
|
|
|
74
|
-
##
|
|
74
|
+
## Retrieving asynchronous API results
|
|
75
|
+
|
|
76
|
+
When `run -j` returns HTTP 202, read `body.task_id` from its JSON output. Use the same API key and environment as the submission.
|
|
77
|
+
|
|
78
|
+
```bash
|
|
79
|
+
openany-dev tasks get --id TASK_ID -j
|
|
80
|
+
openany-dev tasks wait --id TASK_ID --timeout-seconds 120 -j
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
`tasks get` reads the task once. `tasks wait` polls until `status` is `completed`, `failed`, or `timed_out`, then prints the task record, including any available `result` or `artifacts` metadata. Check `status` for the task outcome. The wait defaults to 120 seconds and accepts 1–600 seconds. If the local wait expires, the command returns the latest available snapshot with `timedOut: true`. Run it again with the same task ID to resume reading. Both commands only query the existing task, with no balance check or repeat submission. In Dev, use `openany-dev`.
|
|
84
|
+
|
|
85
|
+
## Viewing calls and costs
|
|
75
86
|
|
|
76
87
|
```bash
|
|
77
88
|
openany-dev calls list --status success --limit 20 -j
|
|
@@ -79,13 +90,13 @@ openany-dev calls list --status failed --limit 20 -j
|
|
|
79
90
|
openany-dev calls get --id 3535549d4364136631ff21dd06516e0a -j
|
|
80
91
|
```
|
|
81
92
|
|
|
82
|
-
|
|
93
|
+
Replace the example ID with the actual request ID. Lookups accept model trace IDs and UUIDs. A 32-character hexadecimal UUID is equivalent to its hyphenated form. Other IDs require an exact match. `usageType` distinguishes `model` from `api`. Model records include `model` and `provider`, with `apiId` set to null. `chargedCostMicroUsd` gives the cost of the individual usage record in microdollars. `monthlyUsageMicroUsd` is cumulative and cannot be used to infer the cost of an individual request.
|
|
83
94
|
|
|
84
|
-
|
|
95
|
+
The list defaults to the past seven days. `--from` and `--to` use UTC timestamps in milliseconds, with a maximum span of 31 days. Detail lookups are independent of the list's time window. All queries are scoped to the current account and key. After upgrading, restart pagination from the first page to get a new cursor. Missing metadata such as review and settlement stages remains unknown. Status aliases such as `succeeded/ok/pending/error/unknown` are unsupported. Model records become available only after the backend update is deployed.
|
|
85
96
|
|
|
86
|
-
##
|
|
97
|
+
## Calling models
|
|
87
98
|
|
|
88
|
-
**0.2.0
|
|
99
|
+
**Upgrading to 0.2.0.** Model calls now use curl examples from the catalog. The legacy `models run --protocol/--mode` options are unsupported. After upgrading, run `models examples` to find providers and example IDs, then select a request with `--provider` and `--example`. Audio transcription is currently unsupported.
|
|
89
100
|
|
|
90
101
|
Model examples prefer active playground `curlExample` records for the selected
|
|
91
102
|
model and provider. Price examples supplement missing method/path pairs; a
|
|
@@ -99,13 +110,13 @@ URL path parameters `{model}` and `{provider}` are bound automatically.
|
|
|
99
110
|
Concrete conflicting identities still fail validation; ordinary text fields
|
|
100
111
|
are never rewritten. Refresh example IDs after upgrading.
|
|
101
112
|
|
|
102
|
-
|
|
113
|
+
First, fetch the curl examples for the model and provider:
|
|
103
114
|
|
|
104
115
|
```bash
|
|
105
116
|
openany-dev models examples --model doubao-seedance-2-0-fast --public -j
|
|
106
117
|
```
|
|
107
118
|
|
|
108
|
-
|
|
119
|
+
The output includes each request's `id`, `provider`, request template, path variables, and parsing errors. Save the selected creation request's `request.json` template as `input.json` and fill in the complete body. Use that file as input and leave the rest of the example list out of the request.
|
|
109
120
|
|
|
110
121
|
```bash
|
|
111
122
|
openany-dev models run --model doubao-seedance-2-0-fast --provider ByteDance --example CREATE_EXAMPLE_ID -f input.json --dry-run
|
|
@@ -113,55 +124,55 @@ openany-dev models run --model doubao-seedance-2-0-fast --provider ByteDance --e
|
|
|
113
124
|
openany-dev models run --model doubao-seedance-2-0-fast --provider ByteDance --example QUERY_EXAMPLE_ID --path '{"task_id":"ACTUAL_TASK_ID"}'
|
|
114
125
|
```
|
|
115
126
|
|
|
116
|
-
|
|
127
|
+
Replace `CREATE_EXAMPLE_ID` and `QUERY_EXAMPLE_ID` with IDs from the current `models examples` output. Query examples must use the explicit `{task_id}` variable. The CLI rejects `YOUR_TASK_ID`. Retrieve the task ID from the service response and pass it explicitly. The caller handles ID extraction, polling, retries, and video downloads.
|
|
117
128
|
|
|
118
129
|
- `--provider` is optional. Multiple examples require `--example`; `--endpoint` only checks the selected path. Refresh IDs after example changes.
|
|
119
|
-
- `--input` / `--file`
|
|
120
|
-
- `--dry-run`
|
|
121
|
-
-
|
|
122
|
-
- `operations`
|
|
123
|
-
-
|
|
130
|
+
- `--input` / `--file` supplies the complete JSON request body. Include the matching `model` unless the URL explicitly contains `{model}`. The CLI sends the supplied body without merging the example's prompt, messages, or other defaults. Omit `route.provider` for server-side automatic routing. An explicit `--provider` binds routing; a concrete input provider is preserved and validated against the selected example. Unresolved provider placeholders are removed when no provider is selected.
|
|
131
|
+
- `--dry-run` uses the public catalog and prints the redacted final request without requiring an API key, checking the balance, or calling the model. Live calls require an API key. The CLI checks the balance before POST creation requests and skips that check for GET queries.
|
|
132
|
+
- Multipart requests currently support `/v1/images/edit` and `/v1/images/edits`. Specify each local file explicitly with `--attach FIELD=FILE` and repeat the option as needed for the same field. The CLI never reads file paths from examples. Supply scalar form fields as JSON, use arrays for repeated fields, and provide `route` as a JSON object. Audio transcription is unsupported.
|
|
133
|
+
- Model calls can run without `operations` or `parameters`. You can still query `models parameters` independently. `models run` rejects the legacy `--protocol` and `--mode` options and the `--method`, `--query`, and `--headers` overrides.
|
|
134
|
+
- The parser supports GET, JSON POST, and multipart POST for image edits, including quotes, line continuations, comments, and repeated form fields. It reports invalid JSON, dangling line continuations, model or provider conflicts, and unknown curl options as errors. It neither attempts repairs nor executes shell commands. When it encounters `--location`, it explains that the CLI does not automatically follow redirects.
|
|
124
135
|
|
|
125
|
-
|
|
136
|
+
See the [skill documentation](skills/openany/SKILL.md) for detailed instructions.
|
|
126
137
|
|
|
127
|
-
##
|
|
138
|
+
## Configuring advanced features
|
|
128
139
|
|
|
129
|
-
|
|
|
130
|
-
|
|
|
131
|
-
|
|
|
132
|
-
|
|
|
133
|
-
|
|
|
134
|
-
|
|
|
140
|
+
| Feature | Required configuration |
|
|
141
|
+
| --- | --- |
|
|
142
|
+
| Standard model and API calls | `OPENANY_DEV_API_KEY` or a saved active key |
|
|
143
|
+
| Wallet login, key creation, and key rotation | `OPENANY_DEV_WALLET_ADDRESS`, either `OPENANY_DEV_WALLET_PRIVATE_KEY` or an external signer, and a stable `OPENANY_DEV_AGENT_ID` |
|
|
144
|
+
| Email login and key management | `OPENANY_DEV_EMAIL`, authorized mailbox access for the agent, and a workspace selection when required |
|
|
145
|
+
| Top-ups | The target account's API key, the corresponding wallet or email session, a payment wallet and signing capability, and explicit authorization for the network, per-payment and cumulative limits, scope, and expiration |
|
|
135
146
|
|
|
136
|
-
`openany-dev setup`
|
|
147
|
+
`openany-dev setup` offers three setup options in an interactive terminal. You can also select one directly with a flag:
|
|
137
148
|
|
|
138
|
-
- `--api_key api_key
|
|
139
|
-
- `--wallet_connect wallet
|
|
140
|
-
- `--email_login email
|
|
149
|
+
- `--api_key api_key` prompts for a key label, the API key using masked input, and whether to activate it. Updating a key with the same label replaces its value.
|
|
150
|
+
- `--wallet_connect wallet` prompts for the wallet private key using masked input, derives the address, and asks for a stable agent ID. Press Enter to keep existing values. This setup option accepts local keys only. After saving, follow the wallet workflow in [the setup guide](skills/openany/setup.md#wallet-login-and-api-key-management). For first-time use, run `openany-dev keys create --identity wallet --label agent-main -j` to register the account automatically, confirm the key was saved, then run `openany-dev auth wallet -j`. If you already have a key for the wallet, log in directly.
|
|
151
|
+
- `--email_login email` prompts for an email address. After saving it, run `openany-dev auth email send` to send a verification code, then run `openany-dev auth email verify --code SIX_DIGITS` to log in.
|
|
141
152
|
|
|
142
|
-
`openany-dev status_check wallet|email|api_key|payment`
|
|
153
|
+
`openany-dev status_check wallet|email|api_key|payment` checks local configuration only. Use the literal names `wallet`, `email`, and `api_key` where applicable. The legacy `setup --scenario …` and `status --scenario …` forms still work, and the JSON `scenario` field retains its original value. `setup -j`, `setup --non-interactive`, non-terminal input, `setup --prepare`, and `setup --scenario payment` continue to check configuration without waiting for input or saving changes. Add `--prepare` to check an existing external-signing command. For top-up checks, specify `--identity wallet|email`. Configuration status reports only whether local settings are present. Login, key validity, and payment authorization require separate checks.
|
|
143
154
|
|
|
144
155
|
EVM private keys use 64 hexadecimal characters (32 bytes), with or without a `0x` prefix. MetaMask exports can be pasted directly into `setup`; environment-based keys accept both formats too. Solana requires a Base58-encoded 64-byte secret key.
|
|
145
156
|
|
|
146
|
-
|
|
157
|
+
Use `setup` to save the private key in the existing restricted credentials file, or supply it through a secure environment variable. Subsequent commands load the local wallet, agent ID, and email settings automatically. Nonempty environment variables take precedence. The `environmentOverrides` field in the setup result lists the names of variables that override local settings. The CLI leaves mailbox access to the agent. Use the agent's authorized mailbox tool to read the verification code, then pass it to `auth email verify --code SIX_DIGITS`.
|
|
147
158
|
|
|
148
|
-
|
|
159
|
+
Wallet commands include `auth wallet` and `keys create|rotate --identity wallet --label LABEL`. For external signing, first run the command with `--prepare`, then repeat it with `--challenge-id ID --signature-file FILE`. The identity signature file contains the raw signature as text.
|
|
149
160
|
|
|
150
|
-
|
|
161
|
+
Use `auth email send|verify|refresh|workspace` for email authentication and `keys remote list|get|create|revoke` to manage remote keys. To rotate an email account key, create a new key, switch callers to it, verify it works, and revoke the old key manually. The `OPENANY_DEV_API_KEY` environment variable takes precedence over the local key. Update the environment secret after rotation.
|
|
151
162
|
|
|
152
|
-
|
|
163
|
+
Top-ups use `topups authorize → create → pay → get`. See [the top-up guide](skills/openany/topups.md) for the complete commands and external signature formats. Limits apply to the actual payment amount, including fees. Orders awaiting payment also count against the reserved amount. Each intent fixes the amount, destination, and network. If creation has an uncertain outcome, rerun with the original arguments and `--resume`. If payment submission has an uncertain outcome, query its status only. The CLI leaves repeat top-ups and increases to authorization limits to the caller.
|
|
153
164
|
|
|
154
|
-
##
|
|
165
|
+
## Output, persistence, and recovery
|
|
155
166
|
|
|
156
|
-
- `-j`
|
|
157
|
-
-
|
|
158
|
-
-
|
|
159
|
-
-
|
|
160
|
-
-
|
|
161
|
-
- SSE
|
|
162
|
-
-
|
|
167
|
+
- `-j` prints compact JSON. `-o FILE` saves the result and refuses to overwrite an existing file. Supply the request body with `-i JSON` or `-f FILE` and use JSON arguments for path parameters, query parameters, and additional headers.
|
|
168
|
+
- Critical errors go to stderr and exit with status 1. They include an error code, a description, and the `requestId` and `status` when available. HTTP requests are never retried automatically. Stdout excludes API keys and private keys.
|
|
169
|
+
- The default local configuration path is `~/.config/openany-dev/credentials.json`. Set `OPENANY_DEV_CONFIG_DIR` to use an isolated directory. The existing permissions remain mode 0600 for files and 0700 for directories, with no additional permission options. Keep the file private and out of version control. It contains keys, any saved wallet private key and address, the agent ID, email, sessions, payment policies, and intents. The file has no additional encryption. Writes hold a lock. If a crash leaves a stale lock, confirm the process has exited before removing it manually.
|
|
170
|
+
- If the service completes an identity change and local saving fails, the CLI keeps a recovery file. Run `auth recover --file PATH` with the exact path returned by the CLI. Avoid resubmitting the creation or rotation request.
|
|
171
|
+
- Payment signature files use JSON. Use `{ "signature": "..." }` for EVM and `{ "transaction": "BASE64..." }` for Solana. The signing tool must sign exactly what the CLI exports.
|
|
172
|
+
- SSE returns after the CLI receives the complete stream and validates the end event. Live token display is currently unavailable. Asynchronous data and tool APIs can return a task receipt. For asynchronous model requests, use the published GET example. Task cancellation is unavailable.
|
|
173
|
+
- Audio generation requires `-o`. For other binary responses without an output path, the CLI writes to a temporary file with restricted permissions and returns its path.
|
|
163
174
|
|
|
164
|
-
##
|
|
175
|
+
## Verification and deployment
|
|
165
176
|
|
|
166
177
|
```bash
|
|
167
178
|
npm test
|
|
@@ -169,20 +180,20 @@ npm run check
|
|
|
169
180
|
npm pack --dry-run
|
|
170
181
|
```
|
|
171
182
|
|
|
172
|
-
|
|
183
|
+
Tests use an injected HTTP transport and fixed, unfunded test keys. They cover zero network requests when the API key is missing, contracts, identity isolation, real local signing, top-up limits, and recovery from uncertain outcomes. They run without making real payments, modifying databases, or calling paid APIs.
|
|
173
184
|
|
|
174
|
-
|
|
185
|
+
The backend signing origin must be `https://dev.openany.si`. Deploy the service for changes to Dockerfile defaults to take effect. Orders locked to the previous origin remain subject to signature verification against that origin. Reconcile existing orders and environment overrides before deployment.
|
|
175
186
|
|
|
176
187
|
## Skill documentation maintenance
|
|
177
188
|
|
|
178
|
-
`
|
|
189
|
+
`SKILL.md`, `setup.md`, `calls.md`, and `topups.md` in `skills/openany` are the packaged English skill and the source for the website copies. After updating any of them, synchronize the website checkout and verify the result:
|
|
179
190
|
|
|
180
191
|
```bash
|
|
181
192
|
npm run sync:skill -- ../openany-interface/openany-interface
|
|
182
193
|
npm run sync:skill -- ../openany-interface/openany-interface --check
|
|
183
194
|
```
|
|
184
195
|
|
|
185
|
-
The path must point to the `openany-web` project. The command validates that the skill uses the latest CLI release channel and updates `public
|
|
196
|
+
The path must point to the `openany-web` project. The command validates that the skill uses the latest CLI release channel and updates the entry and three guides under `public/` and `docs/skills/openany/`. In the website checkout, run `npm run check:agent-docs` to verify that guides and client recipes also use the latest release channel without pinning a CLI version. Website builds run that check automatically. Commit both repositories together for a documentation release; these commands do not publish packages or deploy the website.
|
|
186
197
|
|
|
187
198
|
### New email registration
|
|
188
199
|
|