●FABLE 5 — Claude Fable 5 is available again to users worldwide from July 1 after US export controls were lifted●SCIENCE — Claude Science, a workbench for researchers, is in beta; the AI for Science credit program is open through July 15●CODE — Claude Code adds dynamic workflows (research preview) and raises weekly usage limits by 50% through July 13●MODEL — Claude Sonnet 5 is the default across all plans at $2/$10 per million tokens through August 31●GATEWAY — A self-hosted Claude apps gateway arrives for Amazon Bedrock and Google Cloud (SSO, policy, cost control)●SECURITY — A new cybersecurity classifier ships alongside the Fable 5 redeployment●FABLE 5 — Claude Fable 5 is available again to users worldwide from July 1 after US export controls were lifted●SCIENCE — Claude Science, a workbench for researchers, is in beta; the AI for Science credit program is open through July 15●CODE — Claude Code adds dynamic workflows (research preview) and raises weekly usage limits by 50% through July 13●MODEL — Claude Sonnet 5 is the default across all plans at $2/$10 per million tokens through August 31●GATEWAY — A self-hosted Claude apps gateway arrives for Amazon Bedrock and Google Cloud (SSO, policy, cost control)●SECURITY — A new cybersecurity classifier ships alongside the Fable 5 redeployment

TAG

1M

1 articles

← Back to all tags

Claude Code¹ Sonnet 5¹ context¹ cost optimization¹

⟐ Claude Code/2026-07-05Advanced

When to Use Claude Code's Native 1M Context — and When Not To: A Cost-Based Rule

With Sonnet 5 as the default, Claude Code now handles a native 1M-token context. A big window is convenient, but every token you park in it is billed again each turn. Should you load the whole repo, or feed slices? Here is an estimable token model and a decision rule that gives a concrete answer per situation, with working code and the traps to avoid.