Claude Infinite Context: Doubled Limits, Multi-Agents

/* dl-build */ .kl-styled-img { max-width: 62%; margin: 20px auto; display: block; } .kl-styled-img img { width: 100%; height: auto; border-radius: 12px; box-shadow: 0 8px 32px rgba(0,0,0,0.5), 0 0 0 1px rgba(255,255,255,0.06); display: block; } .kl-styled-img figcaption { font-size: 13px; line-height: 1.5; color: #8b949e; font-style: italic; padding: 12px 4px 0 14px; border-left: 2px solid rgba(34, 211, 238, 0.4); margin-top: 12px; text-align: left; max-width: 90%; } .kl-text-img-row { display: flex; align-items: center; gap: 32px; margin: 24px 0; } .kl-text-img-left { flex: 1 1 58%; min-width: 0; } .kl-text-img-left h3 { font-size: 18px; font-weight: 700; color: #22d3ee; margin-bottom: 12px; } .kl-text-img-left p { font-size: 14.5px; line-height: 1.75; color: #c9c3b8; } .kl-text-img-right { flex: 0 0 38%; max-width: 38%; } .kl-text-img-right img { width: 100%; height: auto; border-radius: 12px; box-shadow: 0 8px 32px rgba(0,0,0,0.5), 0 0 0 1px rgba(255,255,255,0.06); object-fit: cover; aspect-ratio: 16/11; } .kl-text-img-row-reverse { flex-direction: row-reverse; } .kl-gallery-2-natural { display: grid; grid-template-columns: 1fr 1fr; gap: 16px; margin: 24px 0; align-items: start; } .kl-gallery-2-natural figure { margin: 0; display: flex; flex-direction: column; background: #0d1117; border: 1px solid #30363d; border-radius: 12px; padding: 12px; } .kl-gallery-2-natural img { width: 100%; height: auto; display: block; border-radius: 8px; box-shadow: 0 4px 16px rgba(0,0,0,0.4); } .kl-gallery-2-natural figcaption { font-size: 12.5px; line-height: 1.5; color: #8b949e; font-style: italic; padding: 10px 4px 0 12px; border-left: 2px solid rgba(34, 211, 238, 0.4); margin-top: 10px; text-align: left; } .entry-content h2, .wp-block-heading[class*= »wp-block-heading »] { font-size: 24px; font-weight: 800; color: #f0f6fc; margin-bottom: 20px; padding-bottom: 12px; border-bottom: 3px solid; border-image: linear-gradient(90deg, #22d3ee, #f97316) 1; } .entry-content h3 { font-size: 18px; font-weight: 700; color: #22d3ee; margin-bottom: 14px; padding-bottom: 8px; border-bottom: 2px solid rgba(34, 211, 238, 0.25); } @media (max-width: 768px) { .kl-styled-img { max-width: 100%; } .kl-text-img-row { flex-direction: column-reverse; gap: 18px; } .kl-text-img-row-reverse { flex-direction: column-reverse; } .kl-text-img-right { flex: none; max-width: 100%; width: 100%; } .kl-gallery-2-natural { grid-template-columns: 1fr; } }
Claude infinite context: unlimited memory window and multi-agent orchestration

Article by Kami

Anthropic held its « Code with Claude » conference this week, entirely focused on AI agents and the future of software development. The announcements were substantial: new multi-agent workflows, doubled usage limits for Claude Code, and a compute partnership with SpaceX to handle the demands of intensive agentic workloads. And at the heart of it all — Claude infinite context, the capability that may redefine what an AI coding assistant can actually do.

What really stands out is the direction Anthropic is taking for the next generation of models: Claude infinite context, advanced multi-agent orchestration, and persistent long-term reasoning. The stated goal is unambiguous — Claude should be far more than a chat assistant, and should function as a genuinely autonomous software engineering system.

Three pillars for the next generation of Claude

At the conference, Anthropic laid out three core priorities for their next flagship model — whether that’s the Claude 5 family or the Mythos system already referenced in several recent leaks. Three concrete axes, not marketing fluff.

Code taste, Claude infinite context and parallel execution

First axis: improving engineering judgment and « code taste ». The goal is no longer chasing benchmarks, but training a model that genuinely understands system architecture, thinks about maintainability, and reasons like a senior developer.

Second axis: Claude infinite context — a memory window that never saturates. In practice, an agent could hold an entire repository, multiple active projects, past sessions, and external tool data in mind simultaneously, without ever losing the thread.

Third axis: multi-agent orchestration. A lead agent delegates tasks to specialized sub-agents running in parallel — frontend, backend, debugging, research — all coordinated in real time.

Claude infinite context: Anthropic's three priorities for the next-generation model presented at the conference

On the performance side, the early numbers circulating around the Mythos preview are already striking. On SWE-bench Pro and Terminal-Bench 2.0, Mythos pulls a clear lead over Opus 4.6 — roughly 25 points ahead. As for timing, Polymarket speculation is in full swing: a September release looks more realistic than a May or June launch.

If Anthropic manages to combine all three pillars — code taste, Claude infinite context, and multi-agent orchestration — the result would be a one-person dev team that never loses context and delegates intelligently. Sonnet and Haiku haven’t been updated in a while, which suggests a version bump for both models could follow soon, as early hints spotted in Anthropic’s codebase already suggested.

Doubled limits thanks to the SpaceX deal

Anthropic has doubled Claude Code usage limits across all paid plans (Pro, Max, Teams and Enterprise). The 5-hour usage cap is now twice as high, and the capacity reduction during peak hours — which penalized Pro and Max subscribers — has been removed. API rate limits for Claude Opus models, already benchmark leaders, have also been significantly raised.

New Claude Opus API rate limits: Tier 1 to 4, input and output tokens per minute
New API caps by tier: a Tier 4 account goes from 2 million to 10 million input tokens per minute. Plenty of headroom for heavy agentic workflows.

This jump is made possible by a deal signed with SpaceX. Anthropic now has access to the full capacity of the Colossus 1 data center — over 300 megawatts of compute power and more than 220,000 Nvidia GPUs, available within the coming month. The company says this new capacity will directly improve availability and performance for all Claude users. And there’s more: Anthropic also revealed several infrastructure partnerships already underway, including a multi-gigawatt agreement involving Google, Amazon, Broadcom, Microsoft, Nvidia, and Fluid Stack.

SpaceX xAI announces Colossus 1 data center access for Anthropic
The official xAI announcement: Anthropic gains access to Colossus 1, one of the largest AI supercomputers ever deployed.

The most unexpected project remains Anthropic’s mention of developing orbital AI compute infrastructure with SpaceX. Servers in space powering AI — it’s no longer science fiction.

Managed Agents: orchestration, dreaming and webhooks

Anthropic used this update to significantly expand the capabilities of managed agents launched in beta earlier this year. The goal is clear: enabling Claude to handle long, complex tasks in a genuinely autonomous way, without constant human intervention. Combined with Claude infinite context, these agents can now sustain coherent multi-session work across large codebases.

Multi-agent Claude configuration: agent_config.yaml with coordinator and sub-agents

Four key new capabilities

The first major addition is multi-agent orchestration. A lead agent coordinates multiple specialized agents working in parallel. The config file shown alongside sets the tone: an Engineering Lead that delegates code review to a reviewer agent and test writing to a test writer agent.

Anthropic also introduces an outcome loop — a self-correction cycle. The agent evaluates its own outputs against defined criteria, then iterates until it hits the expected quality bar. The dreaming feature follows the same logic: agents can review their past sessions, analyze mistakes, and adjust their behavior over time.

Support for webhooks rounds out the picture. Developers can connect Claude directly to their tools, applications, and automated workflows, without complex configuration.

Taken together, these additions fundamentally change what managed agents are. This is no longer a simple assistant responding to queries — it’s a system capable of operating as a persistent, autonomous team: one that learns, self-corrects, and integrates into real working environments. With Claude infinite context as the backbone, the gap between AI assistant and AI engineer keeps narrowing.