Claude Projects: coordinate multiple development tasks

Understand the Projects beta announced on 17 September

The new project experience initially targeted selected Pro and Max subscribers using cloud sessions in Claude Code and without existing web or desktop projects. Anthropic describes gradual expansion, with Team and Enterprise coming later. Existing projects initially keep their previous behavior. This does not establish general availability for every team.

Before adoption, confirm that the relevant account actually has the new coordination experience. Use a bounded test project for evaluation. Do not delete production projects to imitate an eligibility condition. The purpose is to improve a workflow without endangering existing data or routines.

A shared goal needs distinct acceptance criteria

Suppose an internal application should use the same customer identifier across its API, web interface and import script. Describe the end state first: existing data remains readable, new input is validated unambiguously and documentation reflects the current interface. This is more precise than “modernize the project.”

Divide acceptance by work area. The API needs compatibility tests, the interface needs an understandable error state, and the import script needs a dry run without changing real data. Coordination can bring these individual results together, but success in one area must not hide a missing check in another.

Split parallel tasks along real boundaries

Parallel work helps when tasks can be prepared independently. Two agents should not simultaneously rewrite the same central file using different assumptions. Define who owns the interface contract and which work can begin only after it has been reviewed. Give each workstream a clear change boundary.

In this example, first write a short customer-identifier contract with valid and invalid cases. Then the interface and importer can be updated in parallel. Each task records the contract version it used. If that contract changes, affected tests must run again. Speed remains explainable rather than disappearing into difficult merge conflicts later.

A coordinator does not replace code review

The new experience can delegate tasks, assemble results and expose progress. Domain acceptance remains a separate responsibility. Ask each change to state the problem, solution, checks actually run and remaining limitations. “Tests passed” is too vague if it does not identify which tests ran against which revision.

Pay particular attention to authentication, payments, deletion and migrations. Your team should already have named responsibilities for these areas. A project can be asked to produce ready-to-review pull requests, while merging and release follow the normal repository rules. A broad assignment must not silently override those rules.

A coordinator also needs a rule for conflicts between workstreams. If one change renames an interface and another still uses its former name, both results need to be reviewed together. Request a final report listing affected interfaces, tests run on the combined work and remaining uncertainty. Individually successful tasks do not prove that the whole result integrates. The business owner accepts the combined state. Record that decision in the review notes.

Measure value over a complete change cycle

Choose a small maintenance task that is already well understood. Record active review time, clarification requests, conflicts, failing tests and time until the integrated result is ready. Many parallel threads can look productive; what matters is whether the team spends less time coordinating and can still explain the change.

Finish the trial with a handover understandable to a developer who was not involved: which changes belong together, in what order should they be applied, and what is the rollback route? If the coordinator does not reliably provide this overview, reduce project scope. More agents alone will not fix an ambiguous interface contract.

Questions about project coordination

Is this the same as an existing Claude project folder? No. The announcement describes a new coordination experience across tasks and a limited rollout. It does not universally replace existing project capabilities.

Should every ticket start simultaneously? Only independently workable tasks are suitable for parallel execution. What does a project cost? This guide does not quote a fixed project price. Measure account consumption and review effort for the actual assignment. The migration described here is a proposed test case, not a published customer result.