@oneciel-ai/claude-any 0.1.25 → 0.1.28

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 CHANGED
@@ -1,260 +1,338 @@
1
1
  # Claude Any
2
2
 
3
+ ![Claude Any: full Claude Code experience with free or low-cost LLMs](claude-any-adv.png)
4
+
3
5
  | English | [한국어](docs/README.ko.md) | [日本語](docs/README.ja.md) | [中文](docs/README.zh.md) |
4
6
  | --- | --- | --- | --- |
5
-
6
- [![npm version](https://img.shields.io/npm/v/@oneciel-ai/claude-any?logo=npm&label=npm)](https://www.npmjs.com/package/@oneciel-ai/claude-any)
7
- [![npm downloads](https://img.shields.io/npm/dm/@oneciel-ai/claude-any?logo=npm&label=downloads)](https://www.npmjs.com/package/@oneciel-ai/claude-any)
8
- [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
9
-
10
- > ## 🚀 Use the full Claude Code experience with free or low-cost LLMs
11
- >
7
+
8
+ [![npm version](https://img.shields.io/npm/v/@oneciel-ai/claude-any?logo=npm&label=npm)](https://www.npmjs.com/package/@oneciel-ai/claude-any)
9
+ [![npm downloads](https://img.shields.io/npm/dm/@oneciel-ai/claude-any?logo=npm&label=downloads)](https://www.npmjs.com/package/@oneciel-ai/claude-any)
10
+ [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
11
+
12
+ > ## 🚀 Use the full Claude Code experience with free or low-cost LLMs
13
+ >
12
14
  > - **Free** — [NVIDIA hosted NIM](https://build.nvidia.com/) (qwen3-coder-480b, gpt-oss, and friends) through the API Catalog.
13
15
  > - **Low-cost** — [Ollama Cloud](https://ollama.com/cloud) for GLM, Qwen, DeepSeek, and other open-weight models at a fraction of frontier-model pricing.
14
16
  > - **Free + local** — [Ollama](https://ollama.com/) or [vLLM](https://github.com/vllm-project/vllm) on your own GPU, fully offline.
17
+ > - **Plan Mode + Advisor ready** — Claude Any preserves Claude Code Plan Mode on non-Anthropic providers and adds an optional long-context Advisor model for review.
18
+ > - **Smooth free-model pacing** — Claude Code spends time reading files and running tools, and Claude Any uses that natural gap for RPM pacing so NVIDIA hosted free models feel usable even with strict per-minute limits.
15
19
  >
16
20
  > Provider, model, base URL, API key, streaming behavior, and LLM options are all selected from a console menu **before** Claude Code starts. Claude Code itself runs untouched with all of its native tooling, slash commands, and workflows.
17
21
 
18
- ### Demo
19
-
20
- ![NVIDIA hosted NIM driving Claude Code (deepseek-4-flash)](docs/assets/claude-any-nvidia-nim.gif)
21
-
22
- NVIDIA hosted NIM (deepseek-4-flash) driving Claude Code through the claude-any router.  [full mp4 ⤓](https://github.com/OneCielAI/claude-any/raw/main/demo/claude-any-nvidia-nim.mp4)
23
-
24
- ![Ollama Cloud streamed through the claude-any router (glm-5.1)](docs/assets/claude-any-ollama-cloud.gif)
25
-
26
- Ollama Cloud (glm-5.1) streamed through the claude-any router with SSE word-boundary chunking enabled.  [full mp4 ⤓](https://github.com/OneCielAI/claude-any/raw/main/demo/claude-any-ollama-cloud.mp4)
27
-
28
- ---
29
-
30
- Claude Any is a provider selector and compatibility launcher for Claude Code.
31
- It lets you choose Anthropic, Ollama, Ollama Cloud, vLLM, NVIDIA hosted models,
32
- or self-hosted NIM before Claude Code starts, then passes normal Claude Code
33
- arguments through unchanged.
34
-
35
- Credits: One Ciel LLC
36
-
37
- Current version: `0.1.25`
38
-
39
- ## Why This Exists
40
-
41
- Claude Any started from a practical need: even on the highest Claude Code plan,
42
- long sessions can run out of available tokens or become blocked while waiting
43
- for the next quota window. The goal is not to replace Claude Code, but to keep
44
- work moving. Slower but usable providers such as NVIDIA NIM, Ollama Cloud,
45
- vLLM, and local Ollama can act as hybrid third-party agents for summaries,
46
- research, journaling, simple coding tasks, and delegated background work.
47
-
48
- Another design goal is to keep as much of Claude Code's native experience as
49
- possible. When a provider exposes an Anthropic-compatible endpoint, Claude Any
50
- prefers that path so Claude Code tooling, permissions, model selection, and
51
- workflow behavior remain close to the original. For capabilities that remote
52
- providers cannot supply directly, such as web search, Claude Any adds separate
53
- MCP-based tooling.
54
-
55
- The pre-launch menu is console-first. Provider, model, base URL, API key, and
56
- options are meant to be easy to review and change before Claude Code starts,
57
- including over SSH.
58
-
59
- macOS has not been fully tested by the maintainer yet, but Claude Any uses
60
- portable Python and shell wrappers. If you hit a macOS issue, please report it.
22
+ ## Today's Top 3 Benefits
61
23
 
62
- - D. Yun
24
+ 1. **Plan Mode works on non-Anthropic models** — Claude Any keeps Claude Code's Plan Mode usable even when the upstream provider is NVIDIA hosted, Ollama Cloud, local Ollama, vLLM, or NIM.
25
+ 2. **Advisor review with a bigger model** — pick a long-context Advisor Model at launch, then use `/advisor` inside Claude Code to review the current task, blockers, and next concrete action.
26
+ 3. **Free-model RPM limits feel smoother** — router-side RPM pacing uses the natural time spent reading files and running tools, so NVIDIA hosted free models can stay within per-minute limits with less visible waiting.
63
27
 
64
- ## Install
65
-
66
- [![npm version](https://img.shields.io/npm/v/@oneciel-ai/claude-any.svg)](https://www.npmjs.com/package/@oneciel-ai/claude-any)
67
- [![npm downloads](https://img.shields.io/npm/dm/@oneciel-ai/claude-any.svg)](https://www.npmjs.com/package/@oneciel-ai/claude-any)
68
-
69
- Requirements:
70
-
71
- - Python 3.10+
72
- - Claude Code installed and available as `claude`
73
- - Node/npm (used for the install shim and optional MCP web tooling)
74
-
75
- **Install from the npm registry (recommended):**
28
+ ### Demo
76
29
 
30
+ ![NVIDIA hosted NIM driving Claude Code (deepseek-4-flash)](docs/assets/claude-any-nvidia-nim.gif)
31
+
32
+ NVIDIA hosted NIM (deepseek-4-flash) driving Claude Code through the claude-any router.  [full mp4 ⤓](https://github.com/OneCielAI/claude-any/raw/main/demo/claude-any-nvidia-nim.mp4)
33
+
34
+ ![Ollama Cloud streamed through the claude-any router (glm-5.1)](docs/assets/claude-any-ollama-cloud.gif)
35
+
36
+ Ollama Cloud (glm-5.1) streamed through the claude-any router with SSE word-boundary chunking enabled.  [full mp4 ⤓](https://github.com/OneCielAI/claude-any/raw/main/demo/claude-any-ollama-cloud.mp4)
37
+
38
+ ---
39
+
40
+ Claude Any is a provider selector and compatibility launcher for Claude Code.
41
+ It lets you choose Anthropic, Ollama, Ollama Cloud, vLLM, NVIDIA hosted models,
42
+ or self-hosted NIM before Claude Code starts, then passes normal Claude Code
43
+ arguments through unchanged.
44
+
45
+ Credits: One Ciel LLC
46
+
47
+ Current version: `0.1.28`
48
+
49
+ ## Why This Exists
50
+
51
+ Claude Any started from a practical need: even on the highest Claude Code plan,
52
+ long sessions can run out of available tokens or become blocked while waiting
53
+ for the next quota window. The goal is not to replace Claude Code, but to keep
54
+ work moving. Slower but usable providers such as NVIDIA NIM, Ollama Cloud,
55
+ vLLM, and local Ollama can act as hybrid third-party agents for summaries,
56
+ research, journaling, simple coding tasks, and delegated background work.
57
+
58
+ Another design goal is to keep as much of Claude Code's native experience as
59
+ possible. When a provider exposes an Anthropic-compatible endpoint, Claude Any
60
+ prefers that path so Claude Code tooling, permissions, model selection, and
61
+ workflow behavior remain close to the original. For capabilities that remote
62
+ providers cannot supply directly, such as web search, Claude Any adds separate
63
+ MCP-based tooling.
64
+
65
+ The pre-launch menu is console-first. Provider, model, base URL, API key, and
66
+ options are meant to be easy to review and change before Claude Code starts,
67
+ including over SSH.
68
+
69
+ macOS has not been fully tested by the maintainer yet, but Claude Any uses
70
+ portable Python and shell wrappers. If you hit a macOS issue, please report it.
71
+
72
+ - D. Yun
73
+
74
+ ## Install
75
+
76
+ [![npm version](https://img.shields.io/npm/v/@oneciel-ai/claude-any.svg)](https://www.npmjs.com/package/@oneciel-ai/claude-any)
77
+ [![npm downloads](https://img.shields.io/npm/dm/@oneciel-ai/claude-any.svg)](https://www.npmjs.com/package/@oneciel-ai/claude-any)
78
+
79
+ Requirements:
80
+
81
+ - Python 3.10+
82
+ - Claude Code installed and available as `claude`
83
+ - Node/npm (used for the install shim and optional MCP web tooling)
84
+
85
+ **Install from the npm registry (recommended):**
86
+
77
87
  ```sh
78
88
  npm install -g @oneciel-ai/claude-any
79
- claude-any
80
89
  ```
81
90
 
82
- **Upgrade:**
83
-
91
+ ```sh
92
+ claude-any
93
+ ```
94
+
95
+ **Upgrade:**
96
+
84
97
  ```sh
85
98
  npm update -g @oneciel-ai/claude-any
86
- claude-any version
87
99
  ```
88
100
 
89
- **Uninstall:**
90
-
91
101
  ```sh
92
- npm uninstall -g @oneciel-ai/claude-any
102
+ claude-any version
93
103
  ```
94
-
95
- ### Alternative install paths
96
-
97
- Install directly from the GitHub repository (useful for testing unreleased
98
- commits between npm publishes):
99
-
104
+
105
+ **Uninstall:**
106
+
107
+ ```sh
108
+ npm uninstall -g @oneciel-ai/claude-any
109
+ ```
110
+
111
+ ### Alternative install paths
112
+
113
+ Install directly from the GitHub repository (useful for testing unreleased
114
+ commits between npm publishes):
115
+
100
116
  ```sh
101
117
  npm install -g https://github.com/OneCielAI/claude-any.git
102
- claude-any
103
118
  ```
104
119
 
105
- POSIX source install:
106
-
120
+ ```sh
121
+ claude-any
122
+ ```
123
+
124
+ POSIX source install:
125
+
107
126
  ```sh
108
127
  git clone https://github.com/OneCielAI/claude-any.git
128
+ ```
129
+
130
+ ```sh
109
131
  cd claude-any
110
- ./install.sh
111
- claude-any
112
132
  ```
113
133
 
114
- Windows PowerShell source install:
134
+ ```sh
135
+ ./install.sh
136
+ ```
115
137
 
138
+ ```sh
139
+ claude-any
140
+ ```
141
+
142
+ Windows PowerShell source install:
143
+
116
144
  ```powershell
117
145
  git clone https://github.com/OneCielAI/claude-any.git
118
- cd claude-any
119
- .\install.ps1
120
- claude-any
121
146
  ```
122
147
 
123
- ### Releasing (maintainers)
124
-
125
- The npm registry version is published automatically by the
126
- [`Publish to npm`](.github/workflows/npm-publish.yml) workflow when a new
127
- GitHub Release is published. The workflow needs an `NPM_TOKEN` repository
128
- secret containing a granular access token for `@oneciel-ai/claude-any` with
129
- *Bypass 2FA for publishing* enabled.
130
-
131
- Release flow:
132
-
133
- 1. Bump `version` in `package.json` and `VERSION` in `claude_any.py`.
134
- 2. Add a Changelog entry.
135
- 3. `git tag -a vX.Y.Z -m "..." && git push origin vX.Y.Z`.
136
- 4. `gh release create vX.Y.Z --title "..." --notes "..."` — this triggers
137
- the publish workflow.
138
-
139
-
140
- ![Claude Any menu](docs/assets/claude-any-main.en.png)
141
-
142
- ## Demo
143
-
144
- ![Claude Any demo](docs/assets/claude-any-demo.en.gif)
145
-
146
- The demo sequence now shows provider selection, Base URL entry, model selection,
147
- LLM options, and the compatibility test. The compatibility test checks a plain
148
- text response, a required `tool_use`, and a `tool_result` follow-up before the
149
- launcher recommends starting Claude Code.
150
-
151
- Additional current screenshots:
152
-
153
- | Provider | Base URL | Model | LLM options | Compatibility |
154
- | --- | --- | --- | --- | --- |
155
- | ![Provider](docs/assets/claude-any-provider.en.png) | ![Base URL](docs/assets/claude-any-base-url.en.png) | ![Model](docs/assets/claude-any-model.en.png) | ![Options](docs/assets/claude-any-options.en.png) | ![Test](docs/assets/claude-any-test.en.png) |
156
-
157
- See the [full manual](docs/manual.md) for provider setup, headless flags, and
158
- troubleshooting. A downloadable demo video is available at
159
- [docs/assets/claude-any-demo.mp4](docs/assets/claude-any-demo.mp4).
160
-
161
- ## Development Story
162
-
163
- Claude Any was built through real integration tests: provider switching, model
164
- discovery, API-key entry, compatibility tests, web-search tooling, timeout
165
- handling, and native Claude Code behavior. The main lesson was that
166
- Anthropic-compatible Messages endpoints are the cleanest integration path when a
167
- provider supports them. Ollama, vLLM, and NIM can expose Anthropic-compatible
168
- routes that preserve more of Claude Code's tooling model than a generic
169
- OpenAI-compatible chat route.
170
-
171
- Local inference was also tested with Qwen 3.6 27B Q4 through Ollama and vLLM on
172
- RTX 5090 and MSI GB10-class hardware. It worked, but the speed should not be
173
- judged against native Claude Code or Codex. In practice, some hosted/cloud
174
- choices such as NVIDIA NIM and Ollama Cloud felt more useful for this hybrid
175
- workflow than expected.
176
-
177
- OpenAI-compatible endpoints were deliberately kept out of the primary path for
178
- Claude Code use. In testing, tool-call translation through generic OpenAI chat
179
- compatibility was more brittle around tool parameters, tool results, repeated
180
- calls, retries, and model selection.
181
-
182
- The most recent vLLM finding is that server-side tool-call parsing must match
183
- the model family. For Claude Code, a vLLM server can be reachable and still fail
184
- if `--tool-call-parser` is wrong. In particular, Qwen3-Coder should be served
185
- with `--enable-auto-tool-choice --tool-call-parser qwen3_xml`; Hermes is for
186
- Hermes-style models and some older Qwen tool templates. Claude Any now surfaces
187
- this in the compatibility test instead of treating a simple text response as
188
- enough.
189
-
190
- ## Recommended Uses
191
-
192
- Claude Any is most useful where speed is less important than keeping background
193
- work moving. Good fits include Docker host maintenance, Windows or Linux system
194
- administration, cleanup scripts for unused files, periodic security checklists,
195
- log review, Windows Event Log review, intrusion-attempt triage, and report
196
- drafting.
197
-
198
- It is not a replacement for dedicated security products, but it can help
199
- administrators turn routine checks into repeatable scripts and readable reports.
200
- It is useful for summarizing possible virus, ransomware, brute-force, or
201
- remote-access intrusion attempts. In that sense, Claude Any can help you build a
202
- free or low-cost system security watcher for routine checks, alerts, and
203
- human-readable summaries.
204
-
205
- For example, it can help turn requests such as "install PostgreSQL in a Docker
206
- container" or "analyze today's Docker logs and email me a report" into concrete
207
- commands, scripts, scheduled jobs, and summaries.
208
-
209
- A practical pattern is tiered supervision: use smaller or cheaper models to
210
- watch logs and detect possible issues, use a larger model to review findings,
211
- write policy, and plan the response, then let smaller models execute routine
212
- steps under that larger model's supervision.
148
+ ```powershell
149
+ cd claude-any
150
+ ```
213
151
 
214
- ## Features
152
+ ```powershell
153
+ .\install.ps1
154
+ ```
215
155
 
216
- - Pre-launch provider picker with English, Korean, Japanese, and Chinese UI.
217
- - Provider-aware model list and custom model entry.
218
- - API key entry outside the Claude Code chat input.
219
- - LLM option presets for context window, output tokens, timeout, sampling, and
220
- native compatibility.
221
- - Compatibility test before launch, including text response, tool use, and
222
- tool-result round trip checks.
223
- - Runtime context reporting for vLLM/NIM when `/v1/models` exposes
224
- `max_model_len`.
225
- - Console-first pre-launch menu for SSH and terminal workflows.
226
- - Native paths where providers expose Claude/Anthropic-compatible endpoints.
227
- - Router mode for providers that need request/response adaptation.
228
- - DuckDuckGo and fetch MCP wiring for non-native providers.
156
+ ```powershell
157
+ claude-any
158
+ ```
159
+
160
+ ### Releasing (maintainers)
161
+
162
+ The npm registry version is published automatically by the
163
+ [`Publish to npm`](.github/workflows/npm-publish.yml) workflow when a new
164
+ GitHub Release is published. The workflow needs an `NPM_TOKEN` repository
165
+ secret containing a granular access token for `@oneciel-ai/claude-any` with
166
+ *Bypass 2FA for publishing* enabled.
167
+
168
+ Release flow:
169
+
170
+ 1. Bump `version` in `package.json` and `VERSION` in `claude_any.py`.
171
+ 2. Add a Changelog entry.
172
+ 3. `git tag -a vX.Y.Z -m "..." && git push origin vX.Y.Z`.
173
+ 4. `gh release create vX.Y.Z --title "..." --notes "..."` — this triggers
174
+ the publish workflow.
175
+
176
+
177
+ ![Claude Any menu](docs/assets/claude-any-main.en.png)
178
+
179
+ ## Demo
180
+
181
+ ![Claude Any demo](docs/assets/claude-any-demo.en.gif)
182
+
183
+ The demo sequence now shows provider selection, Base URL entry, model selection,
184
+ LLM options, and the compatibility test. The compatibility test checks a plain
185
+ text response, a required `tool_use`, and a `tool_result` follow-up before the
186
+ launcher recommends starting Claude Code.
187
+
188
+ Additional current screenshots:
189
+
190
+ | Provider | Base URL | Model | LLM options | Compatibility |
191
+ | --- | --- | --- | --- | --- |
192
+ | ![Provider](docs/assets/claude-any-provider.en.png) | ![Base URL](docs/assets/claude-any-base-url.en.png) | ![Model](docs/assets/claude-any-model.en.png) | ![Options](docs/assets/claude-any-options.en.png) | ![Test](docs/assets/claude-any-test.en.png) |
193
+
194
+ See the [full manual](docs/manual.md) for provider setup, headless flags, and
195
+ troubleshooting. A downloadable demo video is available at
196
+ [docs/assets/claude-any-demo.mp4](docs/assets/claude-any-demo.mp4).
197
+
198
+ ## Development Story
199
+
200
+ Claude Any was built through real integration tests: provider switching, model
201
+ discovery, API-key entry, compatibility tests, web-search tooling, timeout
202
+ handling, and native Claude Code behavior. The main lesson was that
203
+ Anthropic-compatible Messages endpoints are the cleanest integration path when a
204
+ provider supports them. Ollama, vLLM, and NIM can expose Anthropic-compatible
205
+ routes that preserve more of Claude Code's tooling model than a generic
206
+ OpenAI-compatible chat route.
207
+
208
+ Local inference was also tested with Qwen 3.6 27B Q4 through Ollama and vLLM on
209
+ RTX 5090 and MSI GB10-class hardware. It worked, but the speed should not be
210
+ judged against native Claude Code or Codex. In practice, some hosted/cloud
211
+ choices such as NVIDIA NIM and Ollama Cloud felt more useful for this hybrid
212
+ workflow than expected.
213
+
214
+ OpenAI-compatible endpoints were deliberately kept out of the primary path for
215
+ Claude Code use. In testing, tool-call translation through generic OpenAI chat
216
+ compatibility was more brittle around tool parameters, tool results, repeated
217
+ calls, retries, and model selection.
218
+
219
+ The most recent vLLM finding is that server-side tool-call parsing must match
220
+ the model family. For Claude Code, a vLLM server can be reachable and still fail
221
+ if `--tool-call-parser` is wrong. In particular, Qwen3-Coder should be served
222
+ with `--enable-auto-tool-choice --tool-call-parser qwen3_xml`; Hermes is for
223
+ Hermes-style models and some older Qwen tool templates. Claude Any now surfaces
224
+ this in the compatibility test instead of treating a simple text response as
225
+ enough.
226
+
227
+ ## Recommended Uses
228
+
229
+ Claude Any is most useful where speed is less important than keeping background
230
+ work moving. Good fits include Docker host maintenance, Windows or Linux system
231
+ administration, cleanup scripts for unused files, periodic security checklists,
232
+ log review, Windows Event Log review, intrusion-attempt triage, and report
233
+ drafting.
234
+
235
+ It is not a replacement for dedicated security products, but it can help
236
+ administrators turn routine checks into repeatable scripts and readable reports.
237
+ It is useful for summarizing possible virus, ransomware, brute-force, or
238
+ remote-access intrusion attempts. In that sense, Claude Any can help you build a
239
+ free or low-cost system security watcher for routine checks, alerts, and
240
+ human-readable summaries.
241
+
242
+ For example, it can help turn requests such as "install PostgreSQL in a Docker
243
+ container" or "analyze today's Docker logs and email me a report" into concrete
244
+ commands, scripts, scheduled jobs, and summaries.
245
+
246
+ A practical pattern is tiered supervision: use smaller or cheaper models to
247
+ watch logs and detect possible issues, use a larger model to review findings,
248
+ write policy, and plan the response, then let smaller models execute routine
249
+ steps under that larger model's supervision.
250
+
251
+ ## Features
252
+
253
+ - Pre-launch provider picker with English, Korean, Japanese, and Chinese UI.
254
+ - Provider-aware model list and custom model entry.
255
+ - API key entry outside the Claude Code chat input.
256
+ - LLM option presets for context window, output tokens, timeout, sampling, and
257
+ native compatibility.
258
+ - Compatibility test before launch, including text response, tool use, and
259
+ tool-result round trip checks.
260
+ - Runtime context reporting for vLLM/NIM when `/v1/models` exposes
261
+ `max_model_len`.
262
+ - Console-first pre-launch menu for SSH and terminal workflows.
263
+ - Native paths where providers expose Claude/Anthropic-compatible endpoints.
264
+ - Router mode for providers that need request/response adaptation.
265
+ - DuckDuckGo and fetch MCP wiring for non-native providers.
229
266
  - Headless setup flags such as `--ca-provider`, `--ca-model`, `--ca-base-url`,
230
267
  `--ca-api-key-env`, `--ca-ollama-option`, and `--ca-max-output-tokens`.
268
+ - Claude Code Plan Mode support on router-backed non-Anthropic providers,
269
+ including local handling for `EnterPlanMode` and plan artifacts.
270
+ - Optional `/advisor` slash command that routes the current task state to a
271
+ selected Advisor Model, useful for long-context review and next-step checks.
272
+ - Claude Code `statusLine` integration showing router RPM usage and wait time
273
+ in the bottom status area instead of polluting the chat transcript.
274
+ - Router-side RPM control for NVIDIA hosted, self-hosted NIM, Ollama, and
275
+ Ollama Cloud. `rate_limit_rpm=0` disables throttling while still showing the
276
+ last-60-seconds usage rate.
277
+ - Soft pacing subtracts time already spent reading files, running commands, and
278
+ waiting for tool results. In real coding sessions, those tool-call gaps absorb
279
+ much of the RPM spacing naturally, so providers such as NVIDIA hosted NIM can
280
+ stay within free-model limits without making every Claude Code turn feel
281
+ rate-limited.
231
282
  - Streaming proxy for Ollama/Ollama Cloud router path — tokens are delivered
232
283
  to Claude Code as they arrive instead of waiting for the full response.
233
- - Per-provider `stream` on/off toggle and `stream_word_chunking` option to
234
- batch text deltas at word boundaries, mitigating SSE fragmentation that can
235
- break tool-call / JSON parsing in long streamed responses.
236
- - LLM options menu shows the meaning of the highlighted row at the bottom of
237
- the panel in the selected language (English, Korean, Japanese, Chinese), and
238
- boolean rows (`Stream`, `Stream word chunking`, `Native compatibility`,
239
- `Think`) toggle in place when you press Enter — no input prompt.
240
- - Tool guard hook coverage extended to the full Claude Code hook surface,
241
- including `WorktreeCreate` / `WorktreeRemove`, so non-git working directories
242
- no longer fail Agent isolation with
243
- `Cannot create agent worktree: not in a git repository...`.
284
+ - Per-provider `stream` on/off toggle and `stream_word_chunking` option to
285
+ batch text deltas at word boundaries, mitigating SSE fragmentation that can
286
+ break tool-call / JSON parsing in long streamed responses.
287
+ - LLM options menu shows the meaning of the highlighted row at the bottom of
288
+ the panel in the selected language (English, Korean, Japanese, Chinese), and
289
+ boolean rows (`Stream`, `Stream word chunking`, `Native compatibility`,
290
+ `Think`) toggle in place when you press Enter — no input prompt.
291
+ - Tool guard hook coverage extended to the full Claude Code hook surface,
292
+ including `WorktreeCreate` / `WorktreeRemove`, so non-git working directories
293
+ no longer fail Agent isolation with
294
+ `Cannot create agent worktree: not in a git repository...`.
244
295
  - Config file caching — settings are read from disk once and reused until the
245
296
  file changes, reducing per-request overhead in the router.
246
297
  - Router control-plane endpoints for headless agent coordination:
247
298
  `/ca/chat/messages`, `/ca/chat/wait`, `/ca/chat/stream`, `/ca/chat/files`,
248
299
  and `/ca/plan/artifacts`.
249
-
300
+
250
301
  ## Changelog
251
302
 
303
+ ### 0.1.28
304
+
305
+ - **Plan Mode + Advisor headline**: document Claude Any's Plan Mode support for
306
+ router-backed non-Anthropic providers and the `/advisor` slash command backed
307
+ by a selected long-context Advisor Model.
308
+ - **Status-line RPM telemetry**: Claude Any installs a Claude Code `statusLine`
309
+ command that shows router RPM usage and the latest wait time in the bottom
310
+ status area, keeping rate-limit telemetry out of the chat transcript.
311
+ - **Soft RPM pacing for free hosted models**: NVIDIA hosted, self-hosted NIM,
312
+ Ollama, and Ollama Cloud can use router-side RPM pacing. The pacing subtracts
313
+ time already spent in file reads, command execution, and tool-result waits, so
314
+ normal coding tool-call gaps naturally absorb much of the RPM spacing.
315
+ - **Unlimited usage display**: `rate_limit_rpm=0` disables throttling while
316
+ still displaying the last-60-seconds request rate.
317
+
318
+ ### 0.1.27
319
+
320
+ - **Plan mode support for non-Anthropic providers**: the router now keeps
321
+ `EnterPlanMode` available and supports Claude Code Plan mode even when the
322
+ upstream model does not reliably choose that internal tool. Forced
323
+ `tool_choice=EnterPlanMode` is answered locally with a valid Anthropic
324
+ `tool_use`, and long implementation requests that receive only a short or
325
+ empty non-actionable text response are promoted to `EnterPlanMode` using
326
+ language-agnostic structure checks.
327
+ - **Plan-mode self-tool handling**: unsupported Claude Code self-tools are
328
+ still stripped for non-Anthropic providers, but Plan-mode tools are handled
329
+ separately so planning can work instead of being disabled.
330
+
252
331
  ### 0.1.25
253
332
 
254
- - **Plan-mode guard + diagnostics**: non-Anthropic providers now strip Claude
255
- Code self-tools such as `EnterPlanMode` before forwarding requests upstream.
256
- Set `~/.config/claude-any/log-level` to `TRACE` to capture redacted request
257
- and response summaries in `requests.jsonl` / `responses.jsonl`.
333
+ - **Plan-mode diagnostics**: set `~/.config/claude-any/log-level` to `TRACE`
334
+ to capture redacted request and response summaries in `requests.jsonl` /
335
+ `responses.jsonl`.
258
336
  - **Headless agent chat service**: the router exposes a small HTTP control
259
337
  plane for sub coding agents. Agents can post messages, poll updates after
260
338
  the last seen message id, or wait on an SSE stream when they do not have
@@ -266,177 +344,177 @@ steps under that larger model's supervision.
266
344
  ### 0.1.24
267
345
 
268
346
  - **First public npm release** under the correct scope: `@oneciel-ai/claude-any`. Earlier 0.1.x versions were never published to the registry; this is the version that is actually installable via `npm install -g @oneciel-ai/claude-any`.
269
-
270
- ### 0.1.23
271
-
272
- - **Stream toggle**: each non-Anthropic provider now has a `stream_enabled`
273
- knob in the LLM options menu, in `claude-anyctl ollama-options` /
274
- `provider-options`, and in headless flags. When off, the router forces
275
- `stream:false` upstream and returns the full response to Claude Code — a
276
- workaround when streaming fragmentation breaks tool-call or JSON parsing.
277
- - **Word-boundary streaming**: new `stream_word_chunking` option buffers SSE
278
- text deltas to whitespace/word boundaries before flushing. Implemented for
279
- both the Ollama router path and the native pass-through path (vLLM, NVIDIA
280
- hosted, self-hosted NIM). Tool deltas and non-text SSE events pass through
281
- unchanged.
282
- - **All-hooks tool guard**: `install_tool_guard_hooks` now registers the full
283
- set of Claude Code hook events (PreToolUse, PostToolUse, PostToolUseFailure,
284
- PostToolBatch, PermissionRequest, PermissionDenied, SessionStart/End, Setup,
285
- UserPromptSubmit/Expansion, Stop, StopFailure, InstructionsLoaded,
286
- ConfigChange, CwdChanged, Notification, SubagentStart/Stop, TeammateIdle,
287
- TaskCreated, TaskCompleted, PreCompact, PostCompact, WorktreeCreate,
288
- WorktreeRemove, Elicitation, ElicitationResult). The WorktreeCreate handler
289
- emits `worktreePath = base_path` so Agent isolation works in non-git
290
- directories.
291
- - **Windows hook compatibility**: `shell_command_string` now emits forward
292
- slashes and POSIX quoting on Windows so Claude Code's sh-based hook runner
293
- doesn't strip backslashes from paths like `C:\Users\...`.
294
- - **LLM options UX**: per-row description footer rendered in the user's
295
- selected language, and boolean toggles (`Stream`, `Stream word chunking`,
296
- `Native compatibility`, `Think`) flip on Enter without a prompt.
297
-
298
- ### 0.1.22
299
-
300
- - **Headless manual expansion**: expand the manual with practical headless setup, launch, testing, passthrough, and cleanup examples for automation and remote-server use.
301
-
302
- ### 0.1.21
303
-
304
- - **Service lifecycle documentation**: clarify that Claude Any starts only the router/proxy services required for the selected provider at launch time, and `claude-any stop` is the explicit cleanup command.
305
-
306
- ### 0.1.20
307
-
308
- - **NVIDIA hosted quick test**: `auto` mode now uses a text-only quick test for NVIDIA hosted providers, avoiding slow or flaky tool_use requests during menu checks. Use `smoke` for text + tool_use, or `full` for the full text/tool_use/tool_result round trip.
309
- - **Menu test timeout**: the terminal menu now runs `claude-any test 60 auto`, which keeps the pre-launch test responsive for hosted models.
310
-
311
- ### 0.1.19
312
-
313
- - **Faster compatibility tests**: `claude-any test` now supports `auto`, `smoke`, and `full` modes.
314
- - **Menu default speedup**: the terminal menu runs `claude-any test 120 auto`, so NVIDIA hosted compatibility checks finish faster while full validation remains available with `claude-any test 180 full`.
315
-
316
- ### 0.1.18
317
-
318
- - **NVIDIA hosted transient diagnostics**: compatibility tests now identify `RemoteDisconnected`, connection resets, and 502/503/504 responses from NVIDIA hosted backends as transient upstream/API Catalog failures.
319
- - **NVIDIA proxy cleanup**: `claude-any stop` now also matches `nvd-claude-proxy` executable processes so stale proxy sessions are cleaned up reliably.
320
-
321
- ### 0.1.17
322
-
323
- - **Menu compatibility-test timeout**: the terminal menu now runs compatibility tests with an explicit 180 s timeout and stops the child process if it exceeds the menu hard limit, so slow hosted models cannot leave the menu appearing indefinitely pending.
324
-
325
- ### 0.1.16
326
-
327
- - **NVIDIA hosted proxy startup fix**: detect and launch an installed `nvd-claude-proxy`/`ncp` executable before falling back to `python -m nvd_claude_proxy.main`. This supports uv-tool installs where the proxy is available as a command but not importable from Claude Any's Python interpreter.
328
-
329
- ### 0.1.15
330
-
331
- - **Ollama/Ollama Cloud tool-call streaming fix**: emit streamed tool calls using sequential Anthropic SSE content block indexes and `input_json_delta` payloads. This prevents Claude Code from rejecting malformed streamed tool-use blocks with `Invalid tool parameters`.
332
- - **Tool guard auto-install**: non-Anthropic launches now merge the Claude Any tool guard into `~/.claude/settings.json` so generated tool inputs can be normalized before execution.
333
- - **Tool-call diagnostics**: router-side tool calls are logged to `~/.config/claude-any/tool-calls.jsonl`, and Claude Code hook inputs are logged to `~/.claude/claude-any-tool-guard/tool-events.jsonl` for precise debugging.
334
- - **Tool input normalization**: the guard now maps common aliases such as `path` to `file_path`, `cmd` to `command`, and `query` to `pattern`, and returns explicit guidance when required fields are missing.
335
-
336
- ### 0.1.14
337
-
338
- - **SSH/terminal arrow-key compatibility**: rewrote `read_menu_key()` with a proper ANSI escape sequence parser and moved raw terminal setup into `portable_select()` so the terminal stays in raw mode for the entire menu loop. This prevents escape sequences from leaking to the screen when `ECHO` is restored between keystrokes. Arrow keys, Home, and End now work reliably in SSH sessions.
339
- - **Test timeout**: default compatibility test timeout increased from 60 s to 120 s for slower cloud providers.
340
- - **Ollama Cloud compatibility test fix**: added `"stream": false` to compatibility test requests so the router fetches a single JSON response from Ollama Cloud instead of SSE streaming, which was causing `post_json` to timeout while collecting all chunks.
341
-
342
- ### 0.1.13
343
-
344
- - **Ollama streaming proxy**: The router now streams Ollama and Ollama Cloud
345
- responses through to Claude Code in real time using Anthropic SSE format,
346
- instead of buffering the entire response before delivery.
347
- - **Config caching**: `load_config()` now caches the configuration file in
348
- memory and only re-reads from disk when the file modification time changes.
349
- This eliminates repeated file I/O and JSON parsing on every router request.
350
- - **Token estimation caching**: `estimate_tokens()` now accepts an optional
351
- cache dict to avoid redundant `json.dumps()` calls within a single request.
352
- `ollama_chat_request` and `cap_output_tokens_for_context` share the same
353
- cache when computing context window sizing.
354
-
355
- ### 0.1.12
356
-
357
- - Refresh docs and demo assets.
358
-
359
- ### 0.1.11
360
-
361
- - Validate tool call compatibility.
362
-
363
- ### 0.1.10
364
-
365
- - Show runtime context in tests.
366
-
367
- ### 0.1.9
368
-
369
- - Cap presets to server context.
370
-
371
- ### 0.1.8
372
-
373
- - Localize LLM presets.
374
-
375
- ## Provider Notes
376
-
377
- | Provider | Mode | Notes |
378
- | --- | --- | --- |
379
- | Anthropic | Native Claude Code | Uses Claude login or Anthropic API key. |
380
- | Ollama | Native when available, router otherwise | Local Ollama normally needs no API key. Cloud models through local Ollama require `ollama signin` on the Ollama host. |
381
- | Ollama Cloud | Router | Calls `https://ollama.com/api`; requires an Ollama API key. |
382
- | vLLM | Native Anthropic-compatible endpoint | Use a vLLM endpoint that exposes Anthropic-compatible `/v1/messages`; match `--tool-call-parser` to the model family. |
383
- | NVIDIA hosted | Router/proxy | Uses NVIDIA hosted API through the compatibility path. |
384
- | self-hosted NIM | Native Anthropic-compatible endpoint | Use the self-hosted NIM Anthropic-compatible endpoint. |
385
-
386
- ## Service Lifecycle
387
-
388
- Claude Any does not keep every possible backend helper running all the time. The
389
- normal lifecycle is:
390
-
391
- - Before launch, managed router/proxy processes can be stopped with
392
- `claude-any stop`.
393
- - When `claude-any` starts Claude Code, it starts only the services required by
394
- the selected provider.
395
- - Ollama and Ollama Cloud router mode use the Claude Any router on
396
- `127.0.0.1:8799`.
397
- - NVIDIA hosted router mode uses the Claude Any router on `127.0.0.1:8799` and
398
- starts `nvd-claude-proxy` on `127.0.0.1:8788` only when that provider needs it.
399
- - Switching away from NVIDIA hosted does not require keeping the NVIDIA proxy
400
- alive; stale sessions should be cleaned with `claude-any stop` before a fresh
401
- test or launch.
402
-
403
- This keeps Claude Code pointed at one stable Claude Any entry point while still
404
- letting provider-specific helpers start on demand.
405
-
406
- For Qwen3-Coder on vLLM, start the server with a matching tool parser:
407
-
408
- ```sh
409
- vllm serve Qwen/Qwen3-Coder-30B-A3B-Instruct \
410
- --host 0.0.0.0 \
411
- --port 8000 \
412
- --served-model-name qwen3-coder-30b \
413
- --max-model-len 65536 \
414
- --enable-auto-tool-choice \
415
- --tool-call-parser qwen3_xml
416
- ```
417
-
418
- ## Provider Links
419
-
420
- - Ollama Cloud: [cloud overview](https://ollama.com/cloud), [API key settings](https://ollama.com/settings/keys), [authentication docs](https://docs.ollama.com/api/authentication).
421
- - Ollama local Anthropic compatibility: [Ollama Anthropic API docs](https://docs.ollama.com/api/anthropic-compatibility).
422
- - vLLM: [Claude Code integration](https://docs.vllm.ai/en/latest/serving/integrations/claude_code/), [tool calling](https://docs.vllm.ai/en/stable/features/tool_calling/), [project GitHub](https://github.com/vllm-project/vllm).
423
- - NVIDIA hosted NIM: [NVIDIA API Catalog](https://build.nvidia.com/), [API Catalog quickstart](https://docs.api.nvidia.com/nim/docs/api-quickstart).
424
- - Self-hosted NVIDIA NIM: [Claude Code with NIM](https://docs.nvidia.com/nim/large-language-models/latest/ai-assistant-integrations/claude-code.html), [NIM for LLMs getting started](https://docs.nvidia.com/nim/large-language-models/1.14.0/getting-started.html), [NGC personal keys](https://org.ngc.nvidia.com/setup/personal-keys).
425
-
426
- ## Headless Examples
427
-
428
- Headless commands skip the pre-launch menu and launch Claude Code immediately.
429
- Claude Any consumes `--ca-*` setup flags, starts the required router/proxy
430
- services, then passes the remaining arguments to Claude Code.
431
-
432
- ```sh
433
- claude-any --ca-provider ollama-cloud --ca-model glm-5.1
434
- claude-any --ca-provider ollama --ca-base-url http://127.0.0.1:11434 --ca-model qwen3-coder
435
- claude-any --ca-provider ollama-cloud --ca-api-key-env OLLAMA_API_KEY --ca-model qwen3-coder:480b:cloud
436
- claude-any --ca-provider vllm --ca-base-url http://127.0.0.1:8000 --ca-model Qwen/Qwen3-Coder
437
- claude-any --ca-no-update-check -p "Reply with OK only." --output-format text
438
- ```
439
-
347
+
348
+ ### 0.1.23
349
+
350
+ - **Stream toggle**: each non-Anthropic provider now has a `stream_enabled`
351
+ knob in the LLM options menu, in `claude-anyctl ollama-options` /
352
+ `provider-options`, and in headless flags. When off, the router forces
353
+ `stream:false` upstream and returns the full response to Claude Code — a
354
+ workaround when streaming fragmentation breaks tool-call or JSON parsing.
355
+ - **Word-boundary streaming**: new `stream_word_chunking` option buffers SSE
356
+ text deltas to whitespace/word boundaries before flushing. Implemented for
357
+ both the Ollama router path and the native pass-through path (vLLM, NVIDIA
358
+ hosted, self-hosted NIM). Tool deltas and non-text SSE events pass through
359
+ unchanged.
360
+ - **All-hooks tool guard**: `install_tool_guard_hooks` now registers the full
361
+ set of Claude Code hook events (PreToolUse, PostToolUse, PostToolUseFailure,
362
+ PostToolBatch, PermissionRequest, PermissionDenied, SessionStart/End, Setup,
363
+ UserPromptSubmit/Expansion, Stop, StopFailure, InstructionsLoaded,
364
+ ConfigChange, CwdChanged, Notification, SubagentStart/Stop, TeammateIdle,
365
+ TaskCreated, TaskCompleted, PreCompact, PostCompact, WorktreeCreate,
366
+ WorktreeRemove, Elicitation, ElicitationResult). The WorktreeCreate handler
367
+ emits `worktreePath = base_path` so Agent isolation works in non-git
368
+ directories.
369
+ - **Windows hook compatibility**: `shell_command_string` now emits forward
370
+ slashes and POSIX quoting on Windows so Claude Code's sh-based hook runner
371
+ doesn't strip backslashes from paths like `C:\Users\...`.
372
+ - **LLM options UX**: per-row description footer rendered in the user's
373
+ selected language, and boolean toggles (`Stream`, `Stream word chunking`,
374
+ `Native compatibility`, `Think`) flip on Enter without a prompt.
375
+
376
+ ### 0.1.22
377
+
378
+ - **Headless manual expansion**: expand the manual with practical headless setup, launch, testing, passthrough, and cleanup examples for automation and remote-server use.
379
+
380
+ ### 0.1.21
381
+
382
+ - **Service lifecycle documentation**: clarify that Claude Any starts only the router/proxy services required for the selected provider at launch time, and `claude-any stop` is the explicit cleanup command.
383
+
384
+ ### 0.1.20
385
+
386
+ - **NVIDIA hosted quick test**: `auto` mode now uses a text-only quick test for NVIDIA hosted providers, avoiding slow or flaky tool_use requests during menu checks. Use `smoke` for text + tool_use, or `full` for the full text/tool_use/tool_result round trip.
387
+ - **Menu test timeout**: the terminal menu now runs `claude-any test 60 auto`, which keeps the pre-launch test responsive for hosted models.
388
+
389
+ ### 0.1.19
390
+
391
+ - **Faster compatibility tests**: `claude-any test` now supports `auto`, `smoke`, and `full` modes.
392
+ - **Menu default speedup**: the terminal menu runs `claude-any test 120 auto`, so NVIDIA hosted compatibility checks finish faster while full validation remains available with `claude-any test 180 full`.
393
+
394
+ ### 0.1.18
395
+
396
+ - **NVIDIA hosted transient diagnostics**: compatibility tests now identify `RemoteDisconnected`, connection resets, and 502/503/504 responses from NVIDIA hosted backends as transient upstream/API Catalog failures.
397
+ - **NVIDIA proxy cleanup**: `claude-any stop` now also matches `nvd-claude-proxy` executable processes so stale proxy sessions are cleaned up reliably.
398
+
399
+ ### 0.1.17
400
+
401
+ - **Menu compatibility-test timeout**: the terminal menu now runs compatibility tests with an explicit 180 s timeout and stops the child process if it exceeds the menu hard limit, so slow hosted models cannot leave the menu appearing indefinitely pending.
402
+
403
+ ### 0.1.16
404
+
405
+ - **NVIDIA hosted proxy startup fix**: detect and launch an installed `nvd-claude-proxy`/`ncp` executable before falling back to `python -m nvd_claude_proxy.main`. This supports uv-tool installs where the proxy is available as a command but not importable from Claude Any's Python interpreter.
406
+
407
+ ### 0.1.15
408
+
409
+ - **Ollama/Ollama Cloud tool-call streaming fix**: emit streamed tool calls using sequential Anthropic SSE content block indexes and `input_json_delta` payloads. This prevents Claude Code from rejecting malformed streamed tool-use blocks with `Invalid tool parameters`.
410
+ - **Tool guard auto-install**: non-Anthropic launches now merge the Claude Any tool guard into `~/.claude/settings.json` so generated tool inputs can be normalized before execution.
411
+ - **Tool-call diagnostics**: router-side tool calls are logged to `~/.config/claude-any/tool-calls.jsonl`, and Claude Code hook inputs are logged to `~/.claude/claude-any-tool-guard/tool-events.jsonl` for precise debugging.
412
+ - **Tool input normalization**: the guard now maps common aliases such as `path` to `file_path`, `cmd` to `command`, and `query` to `pattern`, and returns explicit guidance when required fields are missing.
413
+
414
+ ### 0.1.14
415
+
416
+ - **SSH/terminal arrow-key compatibility**: rewrote `read_menu_key()` with a proper ANSI escape sequence parser and moved raw terminal setup into `portable_select()` so the terminal stays in raw mode for the entire menu loop. This prevents escape sequences from leaking to the screen when `ECHO` is restored between keystrokes. Arrow keys, Home, and End now work reliably in SSH sessions.
417
+ - **Test timeout**: default compatibility test timeout increased from 60 s to 120 s for slower cloud providers.
418
+ - **Ollama Cloud compatibility test fix**: added `"stream": false` to compatibility test requests so the router fetches a single JSON response from Ollama Cloud instead of SSE streaming, which was causing `post_json` to timeout while collecting all chunks.
419
+
420
+ ### 0.1.13
421
+
422
+ - **Ollama streaming proxy**: The router now streams Ollama and Ollama Cloud
423
+ responses through to Claude Code in real time using Anthropic SSE format,
424
+ instead of buffering the entire response before delivery.
425
+ - **Config caching**: `load_config()` now caches the configuration file in
426
+ memory and only re-reads from disk when the file modification time changes.
427
+ This eliminates repeated file I/O and JSON parsing on every router request.
428
+ - **Token estimation caching**: `estimate_tokens()` now accepts an optional
429
+ cache dict to avoid redundant `json.dumps()` calls within a single request.
430
+ `ollama_chat_request` and `cap_output_tokens_for_context` share the same
431
+ cache when computing context window sizing.
432
+
433
+ ### 0.1.12
434
+
435
+ - Refresh docs and demo assets.
436
+
437
+ ### 0.1.11
438
+
439
+ - Validate tool call compatibility.
440
+
441
+ ### 0.1.10
442
+
443
+ - Show runtime context in tests.
444
+
445
+ ### 0.1.9
446
+
447
+ - Cap presets to server context.
448
+
449
+ ### 0.1.8
450
+
451
+ - Localize LLM presets.
452
+
453
+ ## Provider Notes
454
+
455
+ | Provider | Mode | Notes |
456
+ | --- | --- | --- |
457
+ | Anthropic | Native Claude Code | Uses Claude login or Anthropic API key. |
458
+ | Ollama | Native when available, router otherwise | Local Ollama normally needs no API key. Cloud models through local Ollama require `ollama signin` on the Ollama host. |
459
+ | Ollama Cloud | Router | Calls `https://ollama.com/api`; requires an Ollama API key. |
460
+ | vLLM | Native Anthropic-compatible endpoint | Use a vLLM endpoint that exposes Anthropic-compatible `/v1/messages`; match `--tool-call-parser` to the model family. |
461
+ | NVIDIA hosted | Router/proxy | Uses NVIDIA hosted API through the compatibility path. |
462
+ | self-hosted NIM | Native Anthropic-compatible endpoint | Use the self-hosted NIM Anthropic-compatible endpoint. |
463
+
464
+ ## Service Lifecycle
465
+
466
+ Claude Any does not keep every possible backend helper running all the time. The
467
+ normal lifecycle is:
468
+
469
+ - Before launch, managed router/proxy processes can be stopped with
470
+ `claude-any stop`.
471
+ - When `claude-any` starts Claude Code, it starts only the services required by
472
+ the selected provider.
473
+ - Ollama and Ollama Cloud router mode use the Claude Any router on
474
+ `127.0.0.1:8799`.
475
+ - NVIDIA hosted router mode uses the Claude Any router on `127.0.0.1:8799` and
476
+ starts `nvd-claude-proxy` on `127.0.0.1:8788` only when that provider needs it.
477
+ - Switching away from NVIDIA hosted does not require keeping the NVIDIA proxy
478
+ alive; stale sessions should be cleaned with `claude-any stop` before a fresh
479
+ test or launch.
480
+
481
+ This keeps Claude Code pointed at one stable Claude Any entry point while still
482
+ letting provider-specific helpers start on demand.
483
+
484
+ For Qwen3-Coder on vLLM, start the server with a matching tool parser:
485
+
486
+ ```sh
487
+ vllm serve Qwen/Qwen3-Coder-30B-A3B-Instruct \
488
+ --host 0.0.0.0 \
489
+ --port 8000 \
490
+ --served-model-name qwen3-coder-30b \
491
+ --max-model-len 65536 \
492
+ --enable-auto-tool-choice \
493
+ --tool-call-parser qwen3_xml
494
+ ```
495
+
496
+ ## Provider Links
497
+
498
+ - Ollama Cloud: [cloud overview](https://ollama.com/cloud), [API key settings](https://ollama.com/settings/keys), [authentication docs](https://docs.ollama.com/api/authentication).
499
+ - Ollama local Anthropic compatibility: [Ollama Anthropic API docs](https://docs.ollama.com/api/anthropic-compatibility).
500
+ - vLLM: [Claude Code integration](https://docs.vllm.ai/en/latest/serving/integrations/claude_code/), [tool calling](https://docs.vllm.ai/en/stable/features/tool_calling/), [project GitHub](https://github.com/vllm-project/vllm).
501
+ - NVIDIA hosted NIM: [NVIDIA API Catalog](https://build.nvidia.com/), [API Catalog quickstart](https://docs.api.nvidia.com/nim/docs/api-quickstart).
502
+ - Self-hosted NVIDIA NIM: [Claude Code with NIM](https://docs.nvidia.com/nim/large-language-models/latest/ai-assistant-integrations/claude-code.html), [NIM for LLMs getting started](https://docs.nvidia.com/nim/large-language-models/1.14.0/getting-started.html), [NGC personal keys](https://org.ngc.nvidia.com/setup/personal-keys).
503
+
504
+ ## Headless Examples
505
+
506
+ Headless commands skip the pre-launch menu and launch Claude Code immediately.
507
+ Claude Any consumes `--ca-*` setup flags, starts the required router/proxy
508
+ services, then passes the remaining arguments to Claude Code.
509
+
510
+ ```sh
511
+ claude-any --ca-provider ollama-cloud --ca-model glm-5.1
512
+ claude-any --ca-provider ollama --ca-base-url http://127.0.0.1:11434 --ca-model qwen3-coder
513
+ claude-any --ca-provider ollama-cloud --ca-api-key-env OLLAMA_API_KEY --ca-model qwen3-coder:480b:cloud
514
+ claude-any --ca-provider vllm --ca-base-url http://127.0.0.1:8000 --ca-model Qwen/Qwen3-Coder
515
+ claude-any --ca-no-update-check -p "Reply with OK only." --output-format text
516
+ ```
517
+
440
518
  All other arguments are passed through to Claude Code.
441
519
 
442
520
  ## Headless Agent Chat
@@ -463,21 +541,21 @@ curl -s http://127.0.0.1:8799/ca/plan/artifacts \
463
541
  ```
464
542
 
465
543
  ## Security
466
-
467
- Do not commit runtime configuration or API keys. Claude Any stores local runtime
468
- configuration under `~/.config/claude-any/`. NVIDIA hosted credentials used by
469
- the optional proxy are stored under `~/.config/nvd-claude-proxy/`.
470
-
471
- This repository should contain source, documentation, and demo assets only.
472
-
473
- ## Development
474
-
475
- ```sh
476
- python -m py_compile claude_any.py claude-any-menu.py claude-any-tool-guard.py
477
- python -m ruff check .
478
- python scripts/make_demo_assets.py
479
- ```
480
-
481
- ## License
482
-
483
- MIT. See [LICENSE](LICENSE).
544
+
545
+ Do not commit runtime configuration or API keys. Claude Any stores local runtime
546
+ configuration under `~/.config/claude-any/`. NVIDIA hosted credentials used by
547
+ the optional proxy are stored under `~/.config/nvd-claude-proxy/`.
548
+
549
+ This repository should contain source, documentation, and demo assets only.
550
+
551
+ ## Development
552
+
553
+ ```sh
554
+ python -m py_compile claude_any.py claude-any-menu.py claude-any-tool-guard.py
555
+ python -m ruff check .
556
+ python scripts/make_demo_assets.py
557
+ ```
558
+
559
+ ## License
560
+
561
+ MIT. See [LICENSE](LICENSE).