Digest — 2026-09-01 (technologist)
One thing crossed the escalation bar, and it crossed it hard. A second item is recorded here because it is a dated cost fact about the model every task in this fleet runs on.
1. ACT ON THIS — the Claude Code install floor is now ≥ 2.1.251
What changed. technology--claude-code-security-floor has carried 2.1.241 as the install floor since 2026-08-25, and the 2026-08-28 walk recorded a "cooling cadence" — "eight bypass-carrying releases in eighteen days → three clean releases → now zero releases in three days." That trend reversed within four days. Seven releases have shipped since (2.1.243, 2.1.245, 2.1.246, 2.1.247, 2.1.248, 2.1.250, 2.1.251), and npm's registry reports an eighth, 2.1.252, whose changelog entry has not been published.
2.1.251 alone carries five fixes that are security fixes in substance, quoted verbatim from CHANGELOG.md:
- "Fixed file tools (Read, Write, Edit) following a symlink swapped inside the working directory after the permission check, which could read or write outside the approved location"
- "Fixed Grep and Glob not applying
Read(...)deny rules to files reached through a symlinked search path" - "Fixed plugin commands declared in a marketplace entry being able to point outside the plugin directory; such paths are now rejected with a path-traversal error"
- "Fixed project settings being able to enable detailed beta tracing or raw API body logging, and a lower-scope beta tracing endpoint bypassing an OTLP collector pinned by managed settings or a host app"
- "Fixed the Workflow tool reading (and quoting in errors) a
scriptPathoutside what the session may read before the permission check ran"
Items 1 and 2 are the ones that matter for this fleet specifically. Both are permission-boundary escapes — a path that passed a permission check being made to resolve somewhere else, and deny rules not being applied through a symlinked search path. Every scheduled task in this fleet runs with permission_mode: bypassPermissions, verified live this run from each task's stored configuration. That does not make these irrelevant; it changes what they mean. On the cloud host, where the container is ephemeral and holds nothing but the run, exposure is low. On the mini PC, running against a real home directory, a file tool that can be walked outside its approved directory is the whole threat model.
Two earlier releases in the same window carry more of the same class:
- 2.1.246 — "Fixed Bash permission checks to always require approval for malformed commands with a dangling
&&or||operator"; "Fixed telemetry and metrics requests to Anthropic carrying the API key configured for a third-party gateway (ANTHROPIC_BASE_URL); a credential is now only sent to its own host"; "Fixed the command sandbox's filesystem configuration not respecting--setting-sources"; and a new startup warning for "Bash allow rules with a wildcard before the subcommand (e.g.Bash(git * main)), since they also match options inserted before the subcommand." - 2.1.248 — "Fixed
/ultrareviewand locally seeded cloud sessions uploading uncommitted edits toprod.env-style and*.tfvarsfiles, or to editor swap, temp, and backup copies of credential files (e.g.key.pem.tmp,id_rsa.swo); they now stay on your machine."
The action, unchanged in shape from open question 11 but with a new number: install Claude Code ≥ 2.1.251 on the mini PC, not 2.1.241 and not 2.1.224. Nothing needs doing today — the fleet runs on a managed cloud host whose Claude Code version is not something a scheduled task selects or can read. This is a day-one mini-PC item.
Recorded as a caution rather than buried: the CHANGELOG's newest entry is 2.1.251 while registry.npmjs.org/@anthropic-ai/claude-code/latest reports 2.1.252. Two retrieval paths, two different answers, and the corpus's own standing rule says record both rather than pick one. The floor is set at ≥ 2.1.251 because that is the newest version whose contents were actually read.
2. WORTH KNOWING — a dated cost fact about Opus 5, which is what every task here runs on
Not an action, and not urgent, but it is a price-side fact and the charter's escalation bar names price changes. From Anthropic's Opus 5 migration guide, verbatim:
"Thinking tokens are billed as output tokens even when the thinking text is not returned to you, so although per-token pricing is unchanged, a workload that ran without thinking on Claude Opus 4.8 can produce more output tokens per request on Claude Opus 5."
Per-token pricing did not change. Tokens-per-run may have. Output on Opus 5 is $25/MTok, the most expensive number in this fleet's cost model, and fleet--prompt-cache-economics has no row for this effect at all. The rate was already known; what is new is that the billable output volume per run is not the volume the corpus assumed.
This also produces a live hypothesis about the write ceiling that nobody has considered, from the same page, verbatim: "max_tokens remains a hard limit on total output, thinking plus response text." If the scheduled-task harness sets max_tokens below the model's documented 128K, and thinking consumes part of that same budget, then the ceiling on a large create_file payload is not fixed — it is whatever is left after that turn's thinking. That would explain both the 129,434-byte success and the 170,510-byte failure without requiring a connector byte cap, and it would mean the wall moves run to run. See open question 65 and the probe result recorded in fleet--host-constraints.
What did NOT cross the bar this run
- No deprecation hits any dependency. The deprecations page is unchanged and the most recent notice of any kind is still 2026-06-05, now 88 days. On the 60-day policy, nothing can retire before 2026-10-31, which arithmetically rules out Sonnet 4.5's tentative 2026-09-29 — the date the last run flagged as the fleet's nearest horizon.
- No price change. Verified on the pricing page on 1 September itself, the day the cancelled Sonnet 5 increase would have taken effect: Sonnet 5 is $2/$10, and the cancellation sentence is still on the page verbatim.
- No dated deadline inside 30 days in the technology domain.
Changelog
- 2026-09-01 — created (technologist)