Anthropic redesigned Projects in Claude Code. The old project was a folder: some files plus one chat. The new one is a single ongoing conversation where Claude acts as coordinator. You describe work, and Claude decides what becomes a thread. Each thread is a full Claude Code cloud session running on its own branch and its own copy of the repository. Threads run in parallel, report back to the conversation, and keep going after you close your laptop. Anthropic’s launch post calls it one conversation that splits itself into parallel cloud sessions.
Coordinator and threads
The architecture has two layers. The project conversation is the coordinator. It reads what you send, answers quick questions in place, and starts threads for actual work. It sees what threads report back, not every step they take. Threads are the workers. A thread opens a pull request when the work calls for one, then watches that pull request with auto-fix enabled. It pushes fixes when CI fails and replies when checks pass.
Threads delegate too. Each can split its assignment further using subagents, loops and workflows.
Anthropic’s own example: set a goal to reduce checkout p75 latency, then ask Claude to profile each endpoint, test optimizations and open pull requests in parallel threads. A second example retires a deprecated v1 endpoint across API, web and mobile repositories, one thread each, with Claude reporting which pull requests merge first.
When two threads touch the same code, the overlap surfaces as an ordinary git merge conflict.
#mtp-ccproj-embed{background:#F0EEE6 !important;color:#141413 !important;border:1px solid #D6D1C4 !important;border-radius:12px !important;padding:0 !important;margin:26px 0 !important;overflow:hidden !important;font-family:-apple-system,BlinkMacSystemFont,”Segoe UI”,Helvetica,Arial,sans-serif !important;}
#mtp-ccproj-embed hr,#mtp-ccproj-embed p:empty,#mtp-ccproj-embed del,#mtp-ccproj-embed s{display:none !important;}
#mtp-ccproj-embed .mtp-ccproj-head{background:#141413 !important;color:#F0EEE6 !important;border:0 !important;padding:14px 18px !important;}
#mtp-ccproj-embed .mtp-ccproj-head strong{color:#D97757 !important;font-weight:600 !important;}
#mtp-ccproj-embed .mtp-ccproj-head span{display:block !important;color:#B8B4A8 !important;font-size:12.5px !important;margin-top:3px !important;line-height:1.5 !important;}
#mtp-ccproj-embed iframe{display:block !important;width:100% !important;height:600px !important;border:0 !important;background:#F0EEE6 !important;}
#mtp-ccproj-embed .mtp-ccproj-foot{background:#E6E2D6 !important;color:#6B6862 !important;border-top:1px solid #D6D1C4 !important;padding:9px 18px !important;font-size:11.5px !important;line-height:1.5 !important;}
#mtp-ccproj-embed .mtp-ccproj-foot a{color:#B4562F !important;text-decoration:underline !important;}
@media (max-width:640px){
#mtp-ccproj-embed .mtp-ccproj-head{padding:12px 13px !important;}
#mtp-ccproj-embed .mtp-ccproj-foot{padding:9px 13px !important;}
#mtp-ccproj-embed iframe{height:920px !important;}
}
Interactive: how a Claude Code project routes workClick a task. Watch the coordinator answer in place, save memory, or open a cloud thread on its own branch.
Modeled on Anthropic’s Claude Code projects documentation. Thread timings are illustrative. © Marktechpost
(function(){
var f=document.getElementById(“mtp-ccproj-frame”);
if(!f)return;
window.addEventListener(“message”,function(e){
if(!e.data||!e.data.mtpHeight||e.data.id!==”mtp-claude-projects”)return;
if(e.source!==f.contentWindow)return;
var h=parseInt(e.data.mtpHeight,10);
if(h>200&&h