@textcortex/zenocode 0.1.14 → 0.1.16
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 +36 -1
- package/package.json +1 -1
- package/scripts/build-branded-opencode.mjs +292 -215
- package/scripts/build-branded-opencode.test.mjs +85 -59
- package/scripts/opencode-version.mjs +5 -3
- package/scripts/run-zenocode.mjs +600 -763
- package/scripts/run-zenocode.test.mjs +625 -430
- package/scripts/source-branding.mjs +721 -0
- package/scripts/source-branding.test.mjs +106 -0
- package/scripts/branding-patch.mjs +0 -193
- package/scripts/branding-patch.test.mjs +0 -89
package/README.md
CHANGED
|
@@ -16,6 +16,7 @@ If you already use pay-as-you-go and just ran out of wallet credits, top up unde
|
|
|
16
16
|
- Connects the runtime to your TextCortex account
|
|
17
17
|
- Discovers the models available to your TextCortex workspace
|
|
18
18
|
- Configures the underlying coding agent automatically so you can start coding instead of hand-wiring providers and credentials
|
|
19
|
+
- Runs a pinned, source-branded Zenocode runtime; it does not modify OpenCode binaries in npm or pnpm caches
|
|
19
20
|
|
|
20
21
|
## Install
|
|
21
22
|
|
|
@@ -37,9 +38,43 @@ The first `zenocode login` launches Zenocode automatically after browser authent
|
|
|
37
38
|
|
|
38
39
|
If you already have an API key, you can also start Zenocode by setting `TEXTCORTEX_API_KEY` or `TEXTCORTEX_API_TOKEN`.
|
|
39
40
|
|
|
41
|
+
## Update
|
|
42
|
+
|
|
43
|
+
Zenocode releases its launcher and managed runtime together. Update both with:
|
|
44
|
+
|
|
45
|
+
```bash
|
|
46
|
+
npm install -g @textcortex/zenocode@latest
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
The terminal runtime never checks for, offers, or installs upstream OpenCode updates: the startup update check, the in-app "Update Available" prompt, and the runtime's `/global/upgrade` API are all removed at build time. Running `zenocode upgrade` prints the managed update command above.
|
|
50
|
+
|
|
51
|
+
Runtime package versions include a Zenocode revision suffix (for example, `1.18.10-zenocode.2`). Increment that revision when the Zenocode source overlay changes without an upstream version bump, so an immutable npm runtime release can always be replaced deliberately.
|
|
52
|
+
|
|
40
53
|
## Models
|
|
41
54
|
|
|
42
|
-
Zenocode uses **GPT-
|
|
55
|
+
Zenocode uses **GPT-6 Luna** by default. You can switch to any other model available to your TextCortex workspace from the model picker inside the agent. Available models are discovered from the canonical backend catalog on every launch. A newly added model therefore appears as soon as the backend grants the account access; no Zenocode package release or separate model-list update is required. The default falls back to GPT-5.6 Luna, then the next best coding model (for example Kimi K3), when GPT-6 Luna is not available to you.
|
|
56
|
+
|
|
57
|
+
Alongside the Kimi, GLM, and MiniMax coding models, the catalog includes **Kimi K3**, **Claude Sonnet 5**, and **Claude Opus 5** when your workspace has access to them.
|
|
58
|
+
|
|
59
|
+
### Thinking
|
|
60
|
+
|
|
61
|
+
Most models express thinking as a pair of catalog entries — pick `…-thinking` or `…-non-thinking` in the model picker.
|
|
62
|
+
|
|
63
|
+
Claude Sonnet 5 and Claude Opus 5 additionally support a **thinking level**. Inside the agent, press `ctrl+t` to cycle `low → medium → high → default`; the choice is remembered per model across sessions.
|
|
64
|
+
|
|
65
|
+
For non-interactive runs, pass the level explicitly:
|
|
66
|
+
|
|
67
|
+
```bash
|
|
68
|
+
zenocode run --variant high "refactor the auth module"
|
|
69
|
+
```
|
|
70
|
+
|
|
71
|
+
Models without selectable levels ignore the flag and run at their deployment default.
|
|
72
|
+
|
|
73
|
+
## Usage Attribution
|
|
74
|
+
|
|
75
|
+
Zenocode generation is recorded in the existing `model_usage_events` metering pipeline with `source_type = 'direct_generation'` and `client_medium = 'zenocode'`. Super admins can filter or group the Model Cost Analytics view by **Client medium → zenocode**. The same dimension is available from the `/internal/v2/model-cost-analytics/query` backend endpoint.
|
|
76
|
+
|
|
77
|
+
Attribution starts when the backend change is deployed. Older direct-generation events did not carry a reliable Zenocode marker and are not backfilled.
|
|
43
78
|
|
|
44
79
|
## Built For Security And Compliance
|
|
45
80
|
|
package/package.json
CHANGED