CLAUDE CODE AFTER OPUS 4.6: NEW DEFAULTS, NOISY REGRESSIONS, NPM CHANGE, AND A BRIEF OUTAGE
Claude Code flipped key defaults with Opus 4.6, prompting mixed results as install paths changed and Claude had a brief outage.
Claude Code flipped key defaults with Opus 4.6, prompting mixed results as install paths changed and Claude had a brief outage.
Default behavior shifted to adaptive thinking and medium effort, which can change latency, cost, and output quality without teams noticing.
Operational reliability and governance risks surfaced between a reported code leak, takedowns, and a real outage.
-
terminal
Run the same repo‑scale task with adaptive thinking on vs off (CLAUDE_CODE_DISABLE_ADAPTIVE_THINKING) and effort=85 vs high; measure correctness, diffs, and latency.
-
terminal
Trial parallel agent runs on a safe project to validate speedups and race conditions using patterns from this guide: towardsdatascience.com.
Legacy codebase integration strategies...
- 01.
If you installed via npm, migrate to the new installers and update images/AMIs accordingly: github.com.
- 02.
Set org‑level defaults (effort, adaptive thinking, thinking visibility) and document opt‑outs so upgrades don’t silently change workflow behavior.
Fresh architecture paradigms...
- 01.
Start with Opus 4.6 defaults but bake in observability: log effort, adaptive flags, and token use per task to tune cost/perf.
- 02.
Design agent workflows to tolerate outages and model changes with fallbacks, retries, and circuit breakers.