chutes-build 2.0.3 → 2.0.5

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 (2) hide show
  1. package/CHANGELOG.md +67 -0
  2. package/package.json +7 -7
package/CHANGELOG.md CHANGED
@@ -4,6 +4,73 @@ All notable changes to Chutes Build will be documented in this file. The format
4
4
  is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this
5
5
  project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
6
6
 
7
+ ## [2.0.5] - 2026-10-25
8
+
9
+ ### Fixed
10
+
11
+ - **External-provider 402s no longer masquerade as the weekly limit.** New
12
+ non-TEE catalog entries such as `deepseek-ai/DeepSeek-V4-Pro-0813` and
13
+ `Qwen/Qwen3.8-Max-0902` run on external providers and require a positive PAYG
14
+ balance; Chutes answers `402 A positive balance is required for external
15
+ provider execution`. The pager treated every 402 as a credit-limit denial and
16
+ opened "You hit your weekly limit" even when the subscription window was
17
+ nearly empty. Now that specific 402 is shown with the provider's message, and
18
+ non-TEE models carry a `PAYG` warning notice in the model picker. The
19
+ subscription/weekly quota is not involved.
20
+
21
+ ## [2.0.4] - 2026-10-25
22
+
23
+ ### Added
24
+
25
+ - **A native `chutes-build-harness` skill explains the CLI to the model.** It
26
+ covers the tool inventory, permission modes, slash commands, configuration
27
+ and session locations, diagnostic commands, and a troubleshooting matrix for
28
+ missing tools, denied calls, 401/403/429, chute-id and media payload errors,
29
+ document/media capacity failures, missing skills, npm updates, output limits,
30
+ and loops. The system prompt points at it only when a tool, command,
31
+ permission, session, or capability fails, or when harness detail is needed.
32
+
33
+ ### Changed
34
+
35
+ - **New sessions default to Chutes Auto in API-key builds.** The live catalog
36
+ replaces the bundled model list, which dropped the compiled Auto entry, so the
37
+ default silently fell back to the first listed model. Chutes Build now rebuilds
38
+ Auto from the visible chat models as a latency-routed inline pool
39
+ (`modelA,modelB,...:latency`), because the saved `default` alias needs a
40
+ dashboard pool that API-key-only accounts do not have. The pool includes every
41
+ visible chat model that explicitly advertises tool support in
42
+ `supported_features` and has at least a 32k context, so Auto cannot route an
43
+ agent turn to a model that cannot call the harness tools. Entries that omit the
44
+ feature list are excluded rather than assumed capable.
45
+ `models` and the picker show `model-router` / Chutes Auto again, and a concrete
46
+ model still bypasses routing.
47
+
48
+ ### Fixed
49
+
50
+ - **`update --check` follows the npm registry, and self-update explains the npm
51
+ path.** This fork ships through npm and GitHub releases, so the upstream GCS
52
+ release-channel pointer is absent and the old check failed with HTTP 404 (or a
53
+ missing npm executable on Windows). `--check` now reads the `latest` dist-tag
54
+ over the registry HTTPS API and prints the npm update command; a non-check
55
+ `update` reports that self-update is disabled in this build and points at
56
+ `npm install -g chutes-build@latest`. The upstream installer path remains behind
57
+ the maintainer-only `CHUTES_BUILD_LEGACY_SELF_UPDATE` escape hatch.
58
+ - **`ocr_page` is advertised again.** The tool was registered but never added to
59
+ the ecosystem toolsets, so models could not call it even though the guide
60
+ documented it. Every toolset that offers `extract_document` now offers it too.
61
+ - **Document, embedding, and speech tools resolve public slugs to chute ids.**
62
+ `extract_document`, `embed_texts`, and `transcribe_audio` passed the catalog
63
+ slug to the account describe API, which only accepts the chute id, so they
64
+ failed with "Chute not found" even when the model was live. They now resolve
65
+ through the live catalog first, like `generate_media`.
66
+ - **Media calls place the prompt inside v2 `args` wrappers.** Cords whose schema
67
+ requires a single `args`/`input_args` object without resolvable nested
68
+ properties now receive `{args: {prompt}}` instead of failing with "nothing to
69
+ send". Published schemas that reference missing definitions no longer block
70
+ the call: local validation is best-effort and the server stays authoritative.
71
+ - **The tool catalog budget reflects the restored `ocr_page` schema** (30 tools,
72
+ 10,517 estimated tokens, ceiling 10,600).
73
+
7
74
  ## [2.0.3] - 2026-10-24
8
75
 
9
76
  ### Added
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "chutes-build",
3
- "version": "2.0.3",
3
+ "version": "2.0.5",
4
4
  "description": "Privacy-first, open-source coding agent for the Chutes ecosystem",
5
5
  "license": "Apache-2.0",
6
6
  "author": { "name": "Michael Gasperini", "email": "michael@mikesoft.it", "url": "https://mikesoft.it" },
@@ -37,12 +37,12 @@
37
37
  "check": "npm test && npm run verify:release && npm pack --dry-run"
38
38
  },
39
39
  "optionalDependencies": {
40
- "chutes-build-darwin-arm64": "2.0.3",
41
- "chutes-build-darwin-x64": "2.0.3",
42
- "chutes-build-linux-arm64-gnu": "2.0.3",
43
- "chutes-build-linux-x64-gnu": "2.0.3",
44
- "chutes-build-win32-arm64": "2.0.3",
45
- "chutes-build-win32-x64": "2.0.3"
40
+ "chutes-build-darwin-arm64": "2.0.5",
41
+ "chutes-build-darwin-x64": "2.0.5",
42
+ "chutes-build-linux-arm64-gnu": "2.0.5",
43
+ "chutes-build-linux-x64-gnu": "2.0.5",
44
+ "chutes-build-win32-arm64": "2.0.5",
45
+ "chutes-build-win32-x64": "2.0.5"
46
46
  },
47
47
  "keywords": [
48
48
  "ai",