Claude Code's Project Coordinator Now Runs Your Parallel Agents Without Being Asked. Every Thread Defaults to Opus at High Effort, Your Thread Limit Is Only a Suggestion, and Pro Users Are Told to Expect the Wall Sooner.
Anthropic made the Claude Code Projects coordinator proactive on November 13: it answers in the project chat and posts status updates as parallel cloud threads progress instead of waiting to be asked. Anthropic's Projects documentation shows what that costs. A new project runs every thread on Opus at high effort, there is no fixed number of concurrent threads and a limit you request is a preference rather than a cap, the enforced limit is 500 new threads per day, threads that hit a five-hour or weekly limit auto-continue at the reset by default, and Pro users should expect to reach their limit sooner. Projects remain a public beta on Pro, Max, and Ultra, not Team or Enterprise. The feature list of /btw, /fork, reminders, and read-only links is secondary, and one press report says 200 threads a day where the doc says 500. We read the doc.
By T.W. Ghost
Anthropic updated Claude Code Projects today, November 13, 2026, so that the coordinator, the agent that sits above your parallel cloud threads, is proactive: it answers in the project chat and posts status as threads progress, instead of waiting to be polled. That is the headline from Anthropic's developer account, which we read through secondary coverage. The part worth reading directly is the Projects documentation, which spells out what a project costs to run. A new project puts every thread on Opus at high effort, the configuration the doc says "draws on your plan fastest," with the coordinator itself at low. There is "no fixed number" of concurrent threads, and a limit you ask for is "a preference rather than a cap." The enforced limit is 500 new threads per day across projects.
Two more lines matter for anyone on a Pro plan. Threads that hit a five-hour or weekly usage limit auto-continue when the limit resets, a project-wide setting that is on by default, which means a busy project spends your next window before you open it. And the doc says Pro users "should expect to reach your limit sooner" on days they run projects; a project goes past plan limits only if usage credits are turned on. Projects remain a public beta on Pro, Max, and Ultra, rolling out, and not available on Team or Enterprise. Local threads need Claude Code v2.1.280 or later, and the cache lifetime within plan limits is one hour, after which an idle thread re-reads its whole conversation. We read the doc and the secondary posts. Here is what held up.
What the Doc Says
| Claude Code Projects (Anthropic documentation) | |
|---|---|
| Coordinator | Now answers in chat and posts thread status updates (Nov 13; secondary) |
| Availability | Public beta on Pro, Max, Ultra; rolling out; not on Team or Enterprise |
| Defaults for a new project | Opus everywhere; high effort for threads; low for the coordinator |
| Concurrency | "There's no fixed number"; a requested limit is "a preference rather than a cap" |
| Enforced limit | 500 new threads per day across projects |
| Auto-continue | On by default, project-wide; threads resume when usage limits reset |
| Pro warning | "Should expect to reach your limit sooner" on project days |
| Beyond plan limits | Only if usage credits are on |
| Cache | One hour within plan limits; idle threads re-read the whole conversation |
| Client | Claude Code v2.1.280 or later for local threads |
| Also reported | /btw, /fork, reminders, read-only thread links, artifact thumbnails (secondary, AlphaSignal via DEV) |
The most expensive default on every thread. Opus at high effort is Anthropic's own description of the fastest way through a plan, and it is what a new project does unless you change it.
Soft caps below 500. The number you type into the concurrency setting is advice to the coordinator. The only limit it cannot cross is 500 new threads a day.
Auto-continue spends the next window. A project that hits the five-hour limit at 4 pm starts again at the reset without you. Turn it off if your weekly allowance is also your evening's.
It pairs badly with the Fable window closing. Pro plans lose included Fable 5.2 on November 16 at 11:59 PM Pacific; Pro usage tightens the week Projects gets busier.
One number conflicts. AlphaSignal reports 200 new threads per day. The doc says 500. We print the doc's figure.
Verified vs Unconfirmed: The Scorecard
| Claim | Verdict |
|---|---|
| Coordinator proactive as of Nov 13 | Secondary (ClaudeDevs post via DEV and explainx.ai; not read directly) |
| Pro, Max, Ultra public beta; not Team or Enterprise | Verified (Anthropic doc) |
| Opus and high effort defaults; low for coordinator | Verified (doc) |
| No fixed concurrency; requested limits are preferences | Verified (doc) |
| 500 new threads per day | Verified (doc); 200 in AlphaSignal's report conflicts |
| Auto-continue default; Pro warning; usage credits | Verified (doc) |
| One-hour cache; re-read on idle | Verified (doc) |
| v2.1.280+ | Verified (doc) |
| /btw, /fork, reminders, read-only links | Secondary |
What To Do
Change the defaults before the first thread runs: pick a model and effort per thread deliberately, type a concurrency number knowing it is a preference, and decide whether auto-continue should spend your next window.
Skip Projects on Team or Enterprise, because it is not there, and on Pro read the doc's own warning before a project day; the limit arrives sooner by design.
The frontier is elsewhere: the same week Anthropic let enterprises run the Managed Agents stack in their own data center, where scheduling stays hosted-only, and the desktop app already runs parallel agents with the same per-thread bill. Our model comparison has the current standings side by side.
Sources
- Claude Code docs: Claude Projects
- Anthropic: Projects, redesigned
- DEV: Anthropic upgrades Claude Code Projects, the coordinator now reports in chat (secondary)
- explainx.ai: Claude Code Projects proactive coordinator (secondary)
*Not sure whether parallel agents at Opus prices fit your plan? Take the free 2-minute quiz and get matched. Then read about the memory tiers those threads draw on: Claude Code memory tiers.*