chutes-build 1.5.0 → 1.6.0

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,72 @@ 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
+ ## [1.6.0] - 2026-10-16
8
+
9
+ ### Added
10
+
11
+ - **Account dashboard from the API key alone.** `chutes-build account` (human
12
+ or `--json`) and the TUI `/account` command show the key's Chutes plan,
13
+ quotas, usage windows, and PAYG credit, normalized from the account
14
+ endpoints. No key, no network, or an API error reports honestly instead of
15
+ rendering fake zeros.
16
+ - **Inference speed after every turn.** Completed turns report output tokens
17
+ per API second next to the elapsed time (`Worked for 12.4s · 38.2 tok/s`),
18
+ the session usage totals gain a Speed row (per model when several were
19
+ used), and API timing persists in the usage file. Missing timing renders
20
+ no speed, never `0`.
21
+
22
+ ### Fixed
23
+
24
+ - The re-authentication banner no longer points at `/login` (which this
25
+ build refuses): it names the rejected credential and the API key.
26
+ - **Docs describe shipped behavior again** (spec §5.1): the opt-in browser
27
+ OAuth section, the `login --api-key-stdin` flag, and the login/logout
28
+ command rows — none of which can run in this build — are replaced with
29
+ the API-key-only truth, and `/account` is documented everywhere `/usage`
30
+ is.
31
+
32
+ ### Tests
33
+
34
+ - New pins: account CLI dashboard (full and degraded), `/account` slash
35
+ dispatch plus the fetch/render/honest-error pipeline, the re-auth text
36
+ contract, and the `tok/s` footer plus Speed-row snapshots.
37
+ - Known pre-existing: `manual_meta_false_clears_display_name` and
38
+ `manual_meta_false_empty_summary_keeps_leftover_auto_title` fail
39
+ identically on the clean tree (verified by stash comparison); unrelated
40
+ to this release.
41
+
42
+ ## [1.5.1] - 2026-10-15
43
+
44
+ ### Fixed
45
+
46
+ - **Authentication is API-key-only: no login screen, ever.** Starting without
47
+ a key showed a `Login with Chutes Build` option that could only fail with
48
+ `No OAuth2 configuration available. Run 'chutes-build login'`. The Chutes
49
+ distribution now withholds account login end to end: no login method is
50
+ advertised, no session (inline env or `auth.json`) is served or honored,
51
+ the blocked screen names the one credential (`CHUTES_API_KEY`) instead of
52
+ a dead login option, and `chutes-build login` / `logout` explain the
53
+ setup instead of starting an OAuth flow. All headless, ACP, and sampling
54
+ auth errors point at the API key too.
55
+ - **Terminal tab no longer says `grok`.** The TUI title string is now
56
+ `chutes-build` (or `<title> - chutes-build`), still within the 80-column
57
+ guarantee.
58
+
59
+ ### Tests
60
+
61
+ - New pins: API-key-only method advertising (with and without a key, across
62
+ all `preferred_method` pins), ignored legacy session env, ignored session
63
+ in the `models` banner precedence, and the blocked-screen API-key setup
64
+ text with no login option.
65
+ - Known limitation: the `xai-grok-login` session-store machinery tests
66
+ (~106: manager refresh/recovery, OIDC refresher, device code) fail in
67
+ this build because the login store they exercise is intentionally absent
68
+ — reads find nothing and writes are refused by the pre-existing
69
+ distribution gate. They are not run by CI; the injected-distribution
70
+ storage tests pin both sides (STOCK reads/writes, withheld finds
71
+ nothing and refuses writes).
72
+
7
73
  ## [1.5.0] - 2026-10-15
8
74
 
9
75
  ### Changed
package/README.md CHANGED
@@ -109,10 +109,10 @@ cargo check --workspace # fast validation
109
109
  ```
110
110
 
111
111
  The binary artifact is named `xai-grok-pager`; official installs ship it as
112
- `chutes-build`. On first launch it asks for a Chutes API key — the primary
113
- credential, created at [chutes.ai/app/api](https://chutes.ai/app/api) and also
114
- readable from `CHUTES_API_KEY`. Browser login is opt-in and needs an OAuth app you
115
- register yourself; see the
112
+ `chutes-build`. The only credential is a Chutes API key, created at
113
+ [chutes.ai/app/api](https://chutes.ai/app/api) and read from `CHUTES_API_KEY`.
114
+ There is no browser login: `chutes-build login` only prints the API-key setup
115
+ guidance; see the
116
116
  [authentication guide](crates/codegen/xai-grok-pager/docs/user-guide/02-authentication.md).
117
117
 
118
118
  ## Documentation
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "chutes-build",
3
- "version": "1.5.0",
3
+ "version": "1.6.0",
4
4
  "description": "Privacy-first, open-source coding agent for the Chutes ecosystem",
5
5
  "license": "Apache-2.0",
6
6
  "author": "Michael Gasperini (Mikesoft)",
@@ -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": "1.5.0",
41
- "chutes-build-darwin-x64": "1.5.0",
42
- "chutes-build-linux-arm64-gnu": "1.5.0",
43
- "chutes-build-linux-x64-gnu": "1.5.0",
44
- "chutes-build-win32-arm64": "1.5.0",
45
- "chutes-build-win32-x64": "1.5.0"
40
+ "chutes-build-darwin-arm64": "1.6.0",
41
+ "chutes-build-darwin-x64": "1.6.0",
42
+ "chutes-build-linux-arm64-gnu": "1.6.0",
43
+ "chutes-build-linux-x64-gnu": "1.6.0",
44
+ "chutes-build-win32-arm64": "1.6.0",
45
+ "chutes-build-win32-x64": "1.6.0"
46
46
  },
47
47
  "keywords": [
48
48
  "ai",