You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4752971
Browse filesBrowse the repository at this point in the historyBrowse files
docs: server-side x-cc-atis experiment blanks Opus 4.8 summaries (2026-07-07)
On claude-opus-4-8 only, a remote experiment assignment cached in
~/.claude.json (experimentKey claude_code_attic_parcel_experiment) is sent
as an x-cc-atis request header, and with it present the API returns thinking
blocks with a valid signature and an empty thinking string even when the
request carries display:"summarized". The launcher's flag injection cannot
override it; single-variable A/B runs (header stripped in flight, and
assignment purged + DISABLE_GROWTHBOOK=1) restore populated summaries.
- README: dated warning in the workaround list, full 2026-07-07 update
section (scope, effect on the fix, expectations, verified two-step
mitigation, status), troubleshooting entry, compatibility note
- TECHNICAL: full mechanism + evidence section, historical note scoping the
pre-2.1.202 root cause, base-URL-proxy replication warning (also noted on
Option 3)
- fixes/thinking-summaries + launcher docs/headers: limitation notes
- No behavior changes; launcher edits are header comments only
Upstream: anthropics/claude-code#63358 (background); dedicated issue pending.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Thinking summaries render empty in the VS Code extension and headless `-p`/SDK paths, even with `showThinkingSummaries` enabled. Fix via the launcher (recommended), a one-line extension patch, or a local proxy.
11
11
-> [details](#workaround-1-thinking-summaries)
12
12
13
+
> **2026-07-07 - new Opus 4.8 regression, upstream and server-side.** On
14
+
> `claude-opus-4-8` only, the API now returns an empty summary even when the
15
+
> request correctly asks for one, so the launcher's flag is no longer sufficient
16
+
> on that single model. It is gated on an experiment-assignment header the CLI
17
+
> sends. Every other model is unaffected and the launcher remains the fix for
issue for this finding: pending (link will be added here once filed).
182
+
90
183
There are technically three workarounds; only the launcher is maintained:
91
184
92
185
1.**Launcher (recommended).** A small wrapper that launches Claude Code and adds the missing flag. It fixes the VS Code extension and headless CLI, and it survives Claude Code updates.
@@ -295,6 +388,7 @@ Setup is otherwise identical to Option 1. This is unrelated to the fixes above.
295
388
296
389
## Troubleshooting
297
390
391
+
* Summaries suddenly empty again, but only on Opus 4.8 (since 2026-07-07): the launcher is not broken and neither is your setup - your install is likely enrolled in a server-side experiment that blanks Opus 4.8 summaries at the API. No launch flag can override it. Diagnose and mitigate per the [2026-07-07 update](#2026-07-07-update-opus-48-and-the-experiment-header).
298
392
* Thinking still empty after setup: Reload the VS Code window after changing the setting. Confirm the setting points to the launcher's full absolute path. On Windows, confirm the path uses double backslashes.
299
393
* Context icon still missing after setup: It may take two reloads the first time (see the first-run note above). Confirm `CC_PATCH_CONTEXT_ICON` is not set to `0` and `CC_WORKAROUNDS` is not set to `0`.
300
394
*`could not find the real 'claude' binary`: Set `CLAUDE_REAL_BIN` to its full path. Use `which claude` on Linux/macOS or `where claude` on Windows.
Confirmed on Opus 4.7 and Opus 4.8 with VS Code extension builds `2.1.169` through `2.1.172` (native-binary CLI), via the `claudeCode.claudeProcessWrapper` setting, on Windows 11 and Ubuntu 24.04.
338
432
339
-
***Thinking fix:** earlier builds (`2.1.165` / `2.1.167`) signaled thinking with `--thinking adaptive`; `2.1.169` and later use `--max-thinking-tokens` on the VS Code path. The launcher keys off either, plus `-p`/`--print` for headless. The `--thinking-display` flag and the request field are stable levers; the Option 2 minified strings can change between releases (the script matches generically and skips if not found).
433
+
***Thinking fix:** earlier builds (`2.1.165` / `2.1.167`) signaled thinking with `--thinking adaptive`; `2.1.169` and later use `--max-thinking-tokens` on the VS Code path. The launcher keys off either, plus `-p`/`--print` for headless. The `--thinking-display` flag and the request field are stable levers; the Option 2 minified strings can change between releases (the script matches generically and skips if not found).**2026-07-07:** extension `2.1.202`+ maps `showThinkingSummaries` into the launch flags itself (the launcher's injection becomes a harmless no-op there), and on `claude-opus-4-8` a server-side experiment can blank summaries regardless of the flag - see the [2026-07-07 update](#2026-07-07-update-opus-48-and-the-experiment-header). The flag remains correct and sufficient for other models and for un-enrolled installs.
340
434
***Context-icon fix:** the `>50% used` gate has been observed with different minified names (`Z/U` in `2.1.108` and `2.1.131`, `t/c` in `2.1.170` and `2.1.172`). The patch matches the guard-pair shape with variable-name captures and records the matched names in its ownership marker, so it patches and reverts cleanly regardless of the names; if a future build changes the guard shape itself, the launcher safely no-ops and the anchor needs updating.
341
435
***Markdown copy/export fix:** the copy controls are appended to the webview bundle and re-applied each launch. The injection is anchored on stable structural markers and skips cleanly if the bundle shape changes.
Both fixes live in one launcher per platform (`launcher/claudemax` and `launcher/claudemax.win.js`), each fix independently switchable by an environment variable (see [`launcher/README.md`](launcher/README.md) for the toggle table). The node launcher compiles to a single `claudemax.exe` with `pkg` - one binary per platform carrying every fix, down from one exe per fix. The standalone per-fix tools under `fixes/` cover the non-launcher delivery paths.
@@ -19,8 +20,21 @@ The Messages API `thinking.display` field decides whether summarized thinking is
19
20
20
21
There is no raw/full thinking mode: the only valid `display` values are `"summarized"` and `"omitted"`.
21
22
23
+
> **2026-07-07:** a second, unrelated mechanism now exists that blanks Opus 4.8
24
+
> summaries **even when the request carries `display: "summarized"`** - a
25
+
> server-side experiment keyed on an `x-cc-atis` request header. The flag below
26
+
> remains necessary-and-sufficient everywhere else, but cannot override that
27
+
> experiment. See [the 2026-07-07 update](#2026-07-07-update-server-side-experiment-blanks-opus-48-summaries).
28
+
22
29
## Root cause (from the installed CLI)
23
30
31
+
> **Historical note (added 2026-07-07):** the analysis in this section
32
+
> describes builds up to `2.1.201`. As of extension `2.1.202` the extension
33
+
> maps `showThinkingSummaries` into `--thinking-display` itself (the string
34
+
> `"summarized"` now appears in `extension.js`), closing the client-side gap
35
+
> below upstream. Kept for reference and for older builds; the launcher's
36
+
> no-double-inject guard makes it a harmless no-op on fixed builds.
37
+
24
38
The request builder inside the CLI picks `display` like this (function names from a native-installer 2.1.x binary; logic is the same across install types):
25
39
26
40
```js
@@ -116,6 +130,8 @@ Toggle idea (untested): changing the line to `l.display || (process.env.CC_THINK
116
130
### Option 3: local proxy (design)
117
131
118
132
> **Unmaintained and untested.** A design and a working starting point, not a turnkey fix; it sits in the path of your live auth token. The launcher (Option 1) is the supported fix.
133
+
>
134
+
> **2026-07-07:** on current builds, overriding `ANTHROPIC_BASE_URL` makes the CLI build a *different* request (it detects a non-first-party base URL), so this proxy is no longer a byte-faithful passthrough - see the [replication warning](#replication-warning-base-url-proxies-change-the-request).
119
135
120
136
The most thorough fix: a small localhost forward proxy that injects the field at the wire level, so it is surface-agnostic (VS Code + CLI + SDK), needs no install edits, and survives updates. It works because every Claude Code surface resolves the API host as:
121
137
@@ -151,6 +167,109 @@ Status: provided as a working starting point but not extensively tested, so vali
151
167
152
168
Confirmed on Opus 4.7/4.8withVS Code extension `2.1.169` (native-binary CLI), via the `claudeCode.claudeProcessWrapper` setting, on Windows 11 and Ubuntu 24.04; earlier confirmations were on `2.1.165`/`2.1.167` (which signaled thinking with`--thinking adaptive`). TheCLI flag and the request field are stable levers, but the exact minified strings used by [`patch-extension.sh`](fixes/thinking-summaries/patch-extension.sh) (Option 2) can change between extension releases (e.g. the array variable `B`->`q`); the script matches the variable generically and, if the surrounding pattern isn't found, skips and tells you to inspect manually. Options 1 and 3 don't depend on internal strings.
153
169
170
+
**2026-07-07:** on `claude-opus-4-8` only, a server-side experiment can blank summaries regardless of the flag; see the next section. The flag remains correct and sufficient for other models and for installs not carrying the assignment.
171
+
172
+
## 2026-07-07 update: server-side experiment blanks Opus 4.8 summaries
173
+
174
+
A second, independent mechanism, discovered 2026-07-07 (times below are HST,
175
+
UTC-10). It is unrelated to the client-side `display` gap above: here the
176
+
request provably carries `display: "summarized"` and the server withholds the
177
+
summary text anyway - on exactly one model.
178
+
179
+
### Symptom and timeline
180
+
181
+
* Same machine, same account, same CLIbinary (`2.1.202` native): sessions
182
+
through 19:12 returned multi-thousand-character summaries on Opus 4.8;
183
+
the next session at 19:58 and everything after returned `thinking` strings of
184
+
length 0with valid signatures. No client component changed in between
185
+
(`2.1.203`/`2.1.204` behave identically; version-chasing was a red herring).
186
+
* Claude Code's feature-flag client (a remote-eval gating client refreshed at
187
+
session start and on a 6-hour timer) cached a new experiment assignment in
188
+
`~/.claude.json` at **19:12:18** - the exact break boundary:
0 commit comments