Leadership1 publisher2 min readPublished
Anthropic defaults every parallel Claude Code worker to Opus at high effort
Anthropic's redesigned Projects beta enforces one ceiling, 200 new threads a day, and it has not published a usage figure for a single thread. Subscribers see what a project drew only afterwards, in the Usage tab.
The Board Room · Leadership desk
What happened
- Anthropic put a redesigned Projects system for Claude Code into beta on September 17, with a coordinator that splits a goal into parallel threads, each a full cloud session on its own branch.
- Every worker thread defaults to Opus at high effort, while the coordinating conversation that dispatches the work runs at low effort.
- A thread limit a user asks Claude for is saved as a preference Claude follows, and the only enforced ceiling is 200 new threads a day across a subscriber's projects.
- The beta covers select Pro and Max subscribers who have used cloud sessions and have no existing projects, with a waitlist for others and Team and Enterprise access coming later.
Compiled by The Board RoomSomething wrong?How this is made
Why it matters
- decision A team deciding how many workers to launch does so without a unit price for any of them.
- constraint Consumption is broken out by thread and model in a Usage tab. The first accurate account of what a project drew arrives once the plan is already spent.
- cost On a plan without paid usage credits, the expensive default shows up as delay: the thread that hits the limit waits for the reset, and the work queued behind it waits with it.
- contradiction Plaintiffs in the expanded Max complaint say a separate weekly ceiling restricts total use, so a beta whose default draws on the plan fastest arrives in the middle of an argument about how much use a plan buys.
Two settings decide how fast a project draws down a plan: which model runs, and at what effort. Anthropic's documentation says the thread default "draws on your plan fastest" [3]. Each thread draws on the subscriber's own plan, so a project reaches usage limits faster than one session would [4].
The 200-a-day ceiling counts starts. Two hundred new threads a day works out to as many as 6,000 starts in a thirty-day month [20], and going idle does not end a thread's draw: one watching a pull request wakes and consumes again when a test fails or a reviewer comments [6]. The system keeps running after a laptop closes and can be steered from a phone [22]. A thread that a routine started stops its turn with a limit error when the plan runs out, and the user has to message it after the reset [10].
One part of the design is auditable. Decisions carry between sessions as files, indexed by a MEMORY.md that every new thread reads, and users can inspect, edit or delete those files in Project settings [13].
The board-deck version is that this is a throughput release for individual power users, and for this quarter that is accurate. David Gewirtz, a ZDNET senior contributing editor who runs Claude Code in a terminal against local files, said the redesign does not create new parallelism because he already uses subagent swarms [16]. He also said overlapping work postpones conflicts instead of preventing them [17]. His setup supports the point: threads run only in the cloud for now, with no access to local files or private networks [11]. Anthropic's own example is different work, a deprecated v1 endpoint retired across separate API, web and mobile repositories, where Claude opens a thread for each repository and reports which pull requests must merge first [14]. Where two workers edit the same code, Projects surfaces the overlap as a merge conflict like any other pull request [15].
The release lands while the plans it draws on are in dispute. Anthropic argued in a motion to dismiss an earlier version of the Max subscription complaint that buyers could reach details about the limits through links in the purchase flow [19]. The beta shipped nine days after the expanded complaint was filed [21].
What to watch
- Whether Team and Enterprise access arrives with enforceable per-project thread caps or the same preference model.
- Any Anthropic figure for what one Opus high-effort thread consumes, available to a subscriber before a run.
- A ruling on the motion to dismiss in the expanded Max subscription class action.