Claude Opus 5.5 is Anthropic's flagship model, released 22 September 2026 at $4/$20 per million tokens (20% under Opus 5) and positioned by Anthropic as matching its premium Fable 5.1 on most work at roughly 40% lower task cost than Opus 5. Deployment partners cited in coverage (Lovable: 33-50% fewer steps; Optiver: Opus 5 quality in roughly half the turns) echo the community's core behavioral claim — the model batches and reuses rather than rebuilding, compounding into large cost savings on long agent runs. The web record confirms the launch frame and the efficiency story but is thin on the contested limbs: nothing here independently addresses the 500k-context claim (one third-party comparison cites 'Opus' succeeding on 500K+ retrieval without specifying the model or methodology), and per the case file, field reports of drift after 30-40 messages with effective retention near ~150k have already resolved that limb against the original claim, while all harness-based efficiency measurements still share an unresolved model-vs-Claude-Code-version attribution confound.
2026-10-08T00:38:02Z
The nerf-watch closed quietly — the community's 1-2 week expectation elapsed (~Oct 6-7) with no nerf through Oct 8, converting 'no nerf' into a small positive datum for the adoption-economics limb — while the only motion was point drift on the already-characterized voice post 1wxd404 (all velocity flags are its floor-baseline artifacts; magnitude valve still reads platforms=2, Reddit plus its own OCR echo). With the rebuild/batching limb established, the 500k limb resolved against, and no further calendar events, the episode ends absorbed.
2026-10-04T12:08:00Z
grounded: converges/high — Anthropic has newly arrived in weights at behavior Scott's canon engineers at harness level: the corroborated rebuild/batching break is the Self-Equipping Agent
2026-10-04T11:58:41Z
Correction look: the 1wxd404 attach rationale was a misread — that post is a sub-second-latency local voice pipeline (Breeze TTS/STT on Opus 5.5, first audio 500ms-1.5s) with no 500k-token or retention content whatsoever, so the claimed 'user-side long-context corroboration' is withdrawn, the 500k limb stays exactly where it was (resolved AGAINST), and the post adds only a voice-agent usage facet. Otherwise churn at the floor (1.17 pts/h, platforms=2, magnitude valve again an aged-cohort artifact) with the nerf-watch silent at ~day 12-13 of the 1-2-week community window; a quiet close ~Oct 6-7 remains the next calendar event and the likely terminal look unless a nerf or harness-grade replication lands first.
2026-10-04T11:26:57Z
evidence attached: reddit.post.1wxd404 — Independent user report of Opus 5.5 staying behaviorally consistent past 500k context in a live voice-controlled session — user-side corroboration of the long-context consistency claim.
2026-10-02T13:34:02Z
Churn look, third in a row: the 3.3x velocity flag is 3.33 pts/h off a floor baseline on the already-interpreted orchestrator-flip post (1wuruui), with only residual score drift elsewhere (Pokemon thread +34, Max-subscription thread +11) and no new comment substance — engagement alone never becomes a fact. The only moving part is the calendar: the nerf-watch reaches ~day 10-11 of the community's 1-2 week window, so a quiet close (~Oct 6) would itself convert 'no nerf' into a small positive datum for the adoption-economics limb; the magnitude valve fires again but platforms=2 remains Reddit plus its own OCR echo, not cross-community spread, so low heat holds and the corroborated structure with its open attribution confound stands.
2026-10-01T06:25:02Z
1wuruui's hands-on orchestrator flip — token burn down but oversight/reliability degraded versus Fable — confirms rather than complicates the already-recorded division of labor: 5.5 inherits the executor seat with its efficiency gains but not the orchestrator seat, making that limb two-sided instead of adding a contradiction. Everything else is churn: engagement fully decayed (0.17 pts/h, 36th percentile at ~181h), periphery still Reddit plus its own OCR echo (platforms=2) so the magnitude-valve flag again fails to justify heat, and the nerf-watch sits silent at ~day 9 of the community's 1-2 week window with passive sensors positioned to re-light the case.
2026-10-01T06:23:30Z
evidence attached: reddit.post.1wuruui — Hands-on counter-signal that Opus 5.5 in the orchestrator role degrades oversight and reliability versus Fable, qualifying the quality-improvement narrative.
2026-09-30T10:06:38Z
Meaning unchanged: the 12.7x velocity flag was a brief score bump on the already-interpreted 1wstd8x that the speedometer has since fully digested (0.0 pts/h, 0th peer percentile at ~160h age), and the new comments only thicken existing facets — more compaction-retention echoes, plus a remark that the build-immediately default predates 5.5, further blunting model-specificity. Periphery is still Reddit plus its own OCR echo, so the magnitude-valve flag again fails to justify heat; the corroborated structure, open attribution confound, and the silent nerf-watch (~day 8 of the 1-2-week window) stand.
2026-09-29T01:07:13Z
reddit.post.1wstd8x is compaction-mediated long-session retention with low babysitting — a data point for a compaction-resistance facet that aligns with the externalized-memory remedy convergence and inherits the same model-vs-harness confound — not a reopening of the resolved-against raw-500k limb, which the multiple drift/amnesia/~150k testimonies still outweigh. The corroborated structure, open attribution confound, and passive nerf-watch (day ~7-8 of the 1-2 week window, no signal) stand unchanged; low heat holds because the periphery remains Reddit-plus-its-own-OCR-echo with no new communities, outlets, or implementations, and the 82nd peer percentile is an aged-cohort artifact at ~4 pts/h cooling.
2026-09-29T00:31:56Z
evidence attached: reddit.post.1wstd8x — Echoing user reports of long-session context retention and low babysitting are independent corroboration of the claimed Opus 5.5 long-context behavioral break.
2026-09-28T20:06:52Z
reddit.post.1wslhx2 adds a facet to what the break means: the batched/fewer-turns shift has an action-bias counterpart — 5.5 defaults to building immediately and skipping planning — and its comments localize the change to cowork/app surfaces with the terminal unaffected, making the new default harness-surface-dependent and sharpening (not resolving) the open model-vs-harness attribution confound; a single unverified comment claims Anthropic is weighing plan-mode retirement (watch item only). Everything else is engagement churn: the corroborated structure, low heat, and passive nerf-watch (day ~7 of the 1-2 week window, no nerf signal) stand unchanged.
2026-09-28T18:36:53Z
evidence attached: reddit.post.1wslhx2 — Another first-hand report of a changed Opus 5.5 default (build-immediately, skip planning) that belongs in the behavior-shift episode.
2026-09-28T06:48:35Z
No change in meaning: the velocity flag is a cumulative-score artifact on the aging Pokemon benchmark post (536→600 / 72 comments over ~16h ≈ 4 pts/h) plus two comments on a 1-point thread, while the deterministic speedometer reads 1.5 pts/h cooling at ~110h — engagement churn on already-interpreted evidence, not new substance. Low heat stays correct despite the magnitude-valve flag because the second platform is still the case's own OCR echo, and the corroborated structure, open attribution confound, and passive nerf-watch (day ~6 of the 1–2-week window) stand unchanged.
2026-09-28T03:46:50Z
The spike is comment churn on the already-interpreted FPS-gain testimony (17x a small post's baseline) plus more of the same adoption anecdotes in its comments — Codex resets left to expire, a heavy user down from two Max20 subs to one — thickening the efficiency limb without adding a measurement, a platform, or a nerf signal; the corroborated structure and its open attribution confound stand unchanged. Usefully, the spike is a live-fire test of the passive-watch posture: sensors fire at this magnitude, so a genuine nerf (a far larger, unmistakable signature) will re-light the case, which keeps low heat correct through the remaining nerf-window days despite the magnitude-valve flag — the second platform is still the case's own OCR echo.
2026-09-27T22:02:11Z
Two further independent testimonies (40%+ FPS gains where GPT-6 Astra achieved nothing; multiple users unable to exhaust weekly credit on drastically lower token consumption) thicken the efficiency/adoption limbs without altering the corroborated structure — Reddit-side evidence for the step-change is near saturation short of a harness-isolated replication. With the attention cycle decayed (~16 pts/h at 100h, periphery still just Reddit plus its own OCR echo despite the magnitude-valve flag, no new communities/outlets/implementations), the case drops to low heat and passive nerf-watch: the remaining window days are covered by sensor reactivity, since a nerf would re-light the case within hours.
2026-09-27T21:25:32Z
evidence attached: reddit.post.1wruzcj — Two users independently reporting drastically lower token consumption on Opus 5.5 corroborates the behavioral/efficiency break from prior models.
2026-09-27T21:25:32Z
evidence attached: reddit.post.1wrv0sb — Independent user corroboration of a real Opus 5.5 step-change — 40%+ FPS gains where GPT-6 Astra burned a week of usage achieving nothing.
2026-09-27T14:44:04Z
No new substance: the velocity spike is the Pokemon benchmark post still accruing (336→536 score, 68 comments) plus comment churn on the writing-benchmark thread — engagement on already-interpreted evidence, with aggregate momentum now cooling (~22 pts/h at 93h) and the magnitude-valve 'two-platform' spread reading still inflated by an OCR echo of Reddit's own content. Heat holds at medium solely because the case sits at the peak of the community's ~one-week nerf window — the one event that would flip its meaning — and should fall to low once that window closes without a nerf.
2026-09-27T04:37:47Z
No new substance: the velocity spike is the Pokemon benchmark post's second wind (~336 score, 53 comments, hottest object 98.2nd percentile of same-age peers, aggregate ~55 pts/h accelerating at 83h) — engagement on already-interpreted evidence, not new evidence, so the corroborated structure, the attribution confound and the 500k refutation all hold. But this is the hottest measured reading since the launch spike and the nerf-watch now sits inside the community's expected one-week post-launch window — the one event that would flip the case's meaning — so heat rises to medium to keep the case in the re-check cadence; spread remains Reddit plus its own OCR echo, still short of high.
2026-09-26T22:52:59Z
grounded: converges/high — The corroborated rebuild/batching break is a frontier model arriving at behavior Scott's Code-First Architecture engineers at harness level (and directly bears
2026-09-26T22:46:01Z
The only new substance is a counter-report on 5.5's instruction-following that its own thread rejected (score 0, 35% ratio, 'you seem to be the only one') — outlier testimony that reinforces the already-recorded Fable-retains-edge nuance rather than contradicting the behavioral-break core. The velocity spike (hottest object at 3 pts/h, 91.8th percentile of aged peers) is a single-object long-tail flicker on one subreddit; the magnitude-valve spread reading is inflated by counting an OCR echo of Reddit's own content as a second platform, so low heat holds despite it. Live flip-risks remain the model-vs-Claude-Code attribution confound and the community-expected nerf (~one week post-launch).
2026-09-26T22:24:09Z
evidence attached: reddit.post.1wr2ivb — Contested 30-comment counter-report on Opus 5.5 instruction-following quality that re-judging the behavioral-break claim should weigh against the positive reports.
2026-09-26T20:46:26Z
Breadth update, not a structure change: a record writing-benchmark Elo jump (2631 vs Fable 2324), a non-Claude-Code Pokemon-Red agentic eval (Brock at turn 271/$8.44 vs Fable turn 554/$99.76, planning-vs-greedy) and a heavy-user Fable defection extend the step-change reading beyond coding and beyond Claude Code, leaning model-level rather than harness-level — but none compares 5.5 to Opus 5 outside Claude Code, so the attribution confound, the 500k refutation and the pending-nerf question stand. With the new benchmark posts landing at scores 0-5 and velocity 1.5 pts/h off a 275 peak, the magnitude-valve spread reading remains Reddit plus an OCR echo of itself rather than cross-community expansion, so corroborated/low holds; material_change is set only to keep the nerf-watch clock alive on a case whose meaning would flip if a nerf lands.
2026-09-26T20:26:30Z
evidence attached: reddit.post.1wqzifk — Heavy user abandoning Fable for Opus 5.5 in autonomous coding is adoption evidence for the claimed behavioral break.
2026-09-26T20:26:30Z
evidence attached: reddit.post.1wqzubb — Independent agentic eval corroborating a qualitative behavioral break — deliberate forward planning vs Fable's greedy play at roughly 12x lower cost.
2026-09-26T20:26:30Z
evidence attached: reddit.post.1wr03jc — Independent benchmark corroboration of a record Opus 5.5 capability jump, with detailed effort-setting cost/quality tradeoffs.
2026-09-26T13:32:19Z
The centminmod 120-prompt headless benchmark adds a fourth independent measured line to the behavioral-difference limb, but it runs entirely inside Claude Code, so it inherits rather than closes the model-vs-harness attribution confound — input for a future re-judge, not a verdict. Meaning is otherwise unchanged (rebuild/batching break corroborated, 500k limb refuted, guardrails contested, nerf pending); the magnitude-valve flag is still reddit-plus-an-OCR-echo-of-itself rather than genuine multi-platform spread, and velocity is cooling (4.5 pts/h off a 266 peak), so low heat holds.
2026-09-26T13:26:30Z
evidence attached: reddit.post.1wqpf6h — Independent 120-prompt headless Claude Code benchmark comparing Opus 5.5 vs 5 across effort levels is exactly the measured evidence a re-judge of the behavioral-break claim would need.
2026-09-26T10:42:32Z
Nothing new in meaning: the velocity flag is the Fable-comparison thread inching past p90 (145 vs 135) — Anthropic-positioning/nerf-anxiety chatter on an already-integrated object — and comment drift elsewhere is trivial (52→54, 2→4); spread remains one subreddit plus an OCR echo of its own image. The case idles at corroborated/low: rebuild/batching break triple-sourced, 500k limb leaning false, still awaiting harness-grade attribution or a nerf event to move it.
2026-09-26T06:41:32Z
The racing-game post adds a third independent line to the rebuild/batching limb — a real 7,000-player project extended on top of existing code without breakage, the strongest single field demonstration of rebuild-reduction — without changing the case's established meaning (real behavioral break, corroborated; 500k limb leaning false). Attention keeps cooling in one subreddit, so low heat holds despite the magnitude-valve flag: the 'multi-platform' reading is still reddit plus an OCR echo of its own image, no new communities, outlets, or implementations.
2026-09-26T06:23:00Z
evidence attached: reddit.post.1wqj474 — Independent user account of Opus 5.5 extending an existing 7,000-player project without breaking it — direct field evidence for the reduced rebuild-everything claim.
2026-09-25T19:57:32Z
This cycle added no new evidence content: the flagged 'substantive' object (Codex defector post) was already attached and repriced at the last look, and the 25x velocity spike on the amnesia thread is ~4 pts/h absolute over a near-zero peer baseline — deepening discussion of already-integrated counter-evidence, not new spread. Meaning is unchanged (rebuild/batching break corroborated, 500k limb leaning false), and the magnitude-valve reading remains one subreddit plus an OCR echo of its own image, so low heat holds despite the top-decile percentile.
2026-09-25T19:24:46Z
evidence attached: reddit.post.1wq4yi0 — First-person Codex-to-Opus 5.5 defector report corroborating Opus 5.5's improved coding behavior and perceived Astra quality decline.
2026-09-25T17:42:11Z
The 500k-context limb has flipped from single unreplicated anecdote to contested-and-leaning-false: the attached field counter-evidence (mid-session drift after 30–40 messages, total cross-session amnesia) plus its deepening comment thread places the effective-retention cliff near ~150k — squarely in Scott's Dumb Zone band — and community remedies converge on externalized memory (handoff docs, convention lists, compaction), so the episode now field-confirms context engineering rather than challenging it. The corroborated rebuild/batching limb carries the case unchanged; attention is cooling with no periphery expansion, so heat drops to low.
2026-09-25T16:30:12Z
evidence attached: reddit.post.1wq0dnm — Field counter-evidence: user reports mid-session drift after 30–40 messages and total cross-session amnesia, contradicting the 500k-token usable-quality claim.
2026-09-25T12:32:52Z
The two new testimonial posts show the behavioral break has adoption-level consequences — a user ending the Sonnet-for-implementation split on Opus 5.5 economics and another dropping multi-agent parallelism for a faster plan-to-implement loop — meaning the shift is now reshaping real workflow economics, not just measured behavior. As third-line sentiment they graduate nothing: no token-counted 500k replication, no resolution of the model-vs-harness confound, and still a one-subreddit footprint (reddit + OCR echo, no cross-community expansion). Velocity is cooling (56 vs 201 pts/h peak) but holds top-decile peer percentile in a hot cohort, so corroborated/medium holds and the delivered alert is not repeated.
2026-09-25T12:24:45Z
evidence attached: reddit.post.1wpu83x — First-hand account of workflow change under Opus 5.5 (dropped multi-agent parallelism, faster plan-to-implement loop) — independent corroboration that the shift is adoption-shaping.
2026-09-25T12:24:45Z
evidence attached: reddit.post.1wpul7l — Independent user report that Opus 5.5's quality and cost are ending the Sonnet-for-implementation split — adoption-level corroboration of the behavioral break.
2026-09-25T10:25:32Z
The measured re-surge (64.67 pts/h, 99.3rd percentile at 41h age) is velocity on already-weighted content — the 399-pt long-doc hype post compounding plus a reception debate quoting Anthropic's '≈ Fable 5.1 at 40% cheaper' positioning — neither of which adds a token-counted replication for the 500k limb or a new measurement for the rebuild limb, so the case's meaning is unchanged. Despite the magnitude-valve reading, this is still one subreddit plus an OCR echo of its own image, with no new implementations or outlets and momentum cooling from the 178-pt/h peak; the alert was delivered 2026-09-24, so re-escalating to high would re-notify Scott for unchanged substance. Medium heat holds.
2026-09-25T10:24:02Z
evidence attached: reddit.post.1wprzix — 20-comment community debate quoting Anthropic's Opus 5.5 ≈ Fable 5.1 at 40%-cheaper claim, with pushback on 'most work' and nerf-wait skepticism — real-world reception context for the case.
2026-09-25T04:41:01Z
The 'long-doc retention' post does not corroborate the 500k limb — 30-50k words is roughly 40-70k tokens, an order of magnitude below the claim and below Scott's Dumb Zone band — so the premise-challenging limb stays single-anecdote, and the mundane-task-filter post keeps guardrails merely contested. Attention is decaying from release-week peak (16 pts/h vs 133) and concentrated in the attribution side-thread; the magnitude-valve spread reading is one subreddit plus an OCR echo of its own image, not cross-community expansion, so post-alert heat drops to medium while the case holds at corroborated.
2026-09-25T04:22:27Z
evidence attached: reddit.post.1wpluhu — Independent user corroboration of the case's long-context retention claim (30-50k word documents recalled near-perfectly), with strong community sentiment.
2026-09-25T04:22:27Z
evidence attached: reddit.post.1wplz0c — Concrete overcorrection regressions (mundane tasks flagged as sensitive) are the negative half of assessing Opus 5.5's behavioral break.
2026-09-24T22:52:03Z
magnitude valve eligible (multi-platform, top-decile engagement) and never alerted; deterministic escalation to deliver
2026-09-24T20:37:40Z
evidence attached: reddit.post.1wpcccg — Independent 30-run measurement showing 29-42% fewer turns and batched read/write/test commands is quantified corroboration of the claimed behavioral break from Opus 5.
2026-09-24T18:06:30Z
New thread comments reshape two of the four claim threads: the guardrail-relaxation claim is now contradicted (safeguards still trip on 'decarboxylation', big-picture refusals persist), and the commit-attribution 'instruction-adherence regression' — the case's sharpest counterpoint — has surfaced a harness-level mechanism (Claude Code settings attribution overriding CLAUDE.md), reattributing it from model regression to tooling config pending confirmation. The engagement re-surge (88th peer percentile, accelerating) is concentrated in that attribution controversy, not new support for the load-bearing quantitative claims.
2026-09-24T16:38:17Z
evidence attached: reddit.post.1wp56lk — Viral side-by-side one-shot coding demo (26 points) adding independent early-user evidence of the Opus 5.5 coding step-change the case tracks.
2026-09-24T06:40:35Z
The commit-attribution counterpoint reframes the case: Opus 5.5's behavioral shift is bidirectional, not a clean upgrade — more willing to adopt third-party tools and relax guardrails, but measurably worse at honoring standing user instructions Opus 5 obeyed, which reads like a reweighted instruction-priority layer rather than uniform improvement. Meanwhile the launch-week attention spike has fully decayed (0.17 pts/h vs 18.6 peak, 38th peer percentile) with no periphery expansion, so the case cools to low heat while its interpretive content — now including a regression dimension Scott should test alongside the 500k claim — has grown.
2026-09-24T06:24:08Z
evidence attached: reddit.post.1wotjqp — First-hand report that Opus 5.5 systematically violates standing commit-attribution instructions Opus 5 honored — a behavioral-regression counterpoint to the watching case's behavioral-break narrative.
2026-09-24T02:45:46Z
A third independent early-user report broadens the behavioral-break pattern beyond tool-selection into work organization (native subfolders, project-level tracking) and apparent guardrail relaxation — the 'something really changed in 5.5' line now has consistent multi-witness support, but the two load-bearing quantitative claims (usable quality past 500k, halved rebuild rate) still rest on one anecdote and one vendor's leaderboard chart with no independent replication, so the case stays watching with its contradiction-to-Scott's-context-engineering posture intact.
2026-09-24T00:31:35Z
evidence attached: reddit.post.1wojarz — Independent user report that Opus 5.5 changed work organization (native per-step subfolders, project-level tracking) and apparently relaxed biology filters — concrete behavioral-break evidence from an early Pro user.
2026-09-23T23:14:28Z
origin walked (opencode/cheap-glm, conf 0.78): anchor reddit.post.1woeg49 -> echo.other.95440c3a15 by Armature (armature.tech; public face on X is founder Theo Otz @Totzenberger)
2026-09-23T22:20:35Z
grounded: contradicts/high — The 500k-claim, if it holds, strikes at a load-bearing premise of Scott's context-engineering work: that attention quality — not window size — is the constraint
2026-09-23T22:12:35Z
case created — Two independent early observations of one behavioral-shift episode around the newly shipped flagship, distinct from the open website-leak signal case.