MarkTechPost ★ 98 5 min

Anthropic Launches Claude Code Projects in Beta: Parallel Cloud Sessions That Keep Running After You Close Your Laptop

Agentic AIAI AgentsFor DevsSoftware EngineeringUncategorized

🔗 https://www.marktechpost.com/2026/09/17/anthropic-launches-claude-code-projects-in-beta-parallel-cloud-sessions-that-keep-running-after-you-close-your-laptop/

📌 拆解Claude Code Projects:協調器怎麼把工作拆給雲端Thread

TL;DR:Anthropic重新設計的Claude Code Projects用「協調器+雲端Thread」兩層架構,讓工作在你關上筆電後依然繼續跑。

一個對話,自己分裂成多個平行的雲端session,還能各自開PR、自己修CI失敗——這是MarkTechPost對Claude Code Projects新架構的描述。

🤔 舊版Project只是資料夾,新版是一段持續進行的對話

舊版的Project本質上是一個資料夾:放一些檔案加一段對話。新版則變成一段持續進行的對話,由Claude擔任協調器(coordinator)角色。你描述要做的工作,由Claude決定哪些內容應該變成一個獨立的thread。每個thread都是一個完整的Claude Code雲端session,執行在自己的分支與自己的一份程式碼庫副本上,平行執行、向對話回報進度,並且在你關上筆電後仍會持續執行。

🧩 兩層架構:協調器負責統籌,Thread負責幹活

Project conversation是協調器層,負責讀取你傳來的內容,就地回答簡單問題,並啟動thread去做實際的工作;它看得到的是thread回報的結果,而不是thread執行的每一個步驟。Thread則是實際幹活的工作單位,工作需要時會開出pull request,並在開啟auto-fix的情況下持續盯著這個PR——CI失敗就推送修正,檢查通過就回覆。每個thread還能再往下拆:透過subagent、loop與workflow把自己的任務進一步分派下去。官方舉的例子包括:設定「降低結帳頁p75延遲」這個目標,讓Claude對每個端點做profiling、測試最佳化方案,並在平行的thread裡分別開PR;另一個例子是跨API、網頁、行動裝置三個repository汰換已棄用的v1端點,每個repository各自一個thread,由Claude回報哪個PR先合併。當兩個thread改到同一段程式碼,衝突會以一般的git merge conflict形式浮現。

專案層級會設定一次「standing context」,並傳遞給每一個新啟動的thread,包括專案的repository與上傳檔案、最多16,000字元的專案說明,以及Claude透過MEMORY.md索引讀寫的專案記憶——例如「發布時間改到週五」或「碰觸帳務系統前要先問誰」。每個thread也會複製專案裡的每一個repository,並載入所有repository裡的CLAUDE.md、skills與plugin。權限規則、hook與環境變數的行為則有差異:它們只作用於thread啟動所在的目錄,因此單一repository的專案能正常套用,多repository的專案則不會。MCP工具透過你claude.ai帳號上的connector接入,project conversation本身沒有connector,因此涉及connector的工作必須交給thread執行。

📊 從Overview面板到200個thread的每日上限

Overview面板依狀態把thread分組:Ready for review、Waiting on you、Working、Landing、Idle與Resolved;Library分頁則彙整上傳的檔案以及thread產出的檔案。一個新專案預設在所有地方使用Opus模型,thread採高努力(high effort)、對話則採低努力(low effort),Anthropic也提供每個專案獨立的Usage分頁,以及分別給協調器與thread設定的模型與努力程度選項。系統設有硬性上限:每個帳號旗下所有專案每天最多能啟動200個新thread,若某個thread用完額度會自動等待並在額度恢復後接續執行。

⚠️ 一個專案吃額度的速度比單一session快

因為每個執行中的thread都是一個完整的session,一個專案消耗方案額度的速度會比單一session快得多。閒置中的thread也不是完全沉睡:一旦CI失敗或有人留下review comment,它們就會重新喚醒並繼續消耗額度。

🎯 實務啟示

在真正把大範圍重構丟給多個並行thread之前,值得先確認你的repository結構是否適合「單一thread對應單一目錄」的權限與hook套用邏輯,並在Usage分頁盯緊額度消耗,避免多個thread同時甦醒時把當月額度提前用完。

🔗 來源

#ClaudeCode #Anthropic #AIAgent #CloudComputing #DevTools #SoftwareEngineering #CodingAgent #MCP #GitWorkflow #Automation

原始資料 MarkTechPost · 收集於 2026-09-18
來源原標題
Anthropic Launches Claude Code Projects in Beta: Parallel Cloud Sessions That Keep Running After You Close Your Laptop
作者
Michal Sutter
原始標籤
Agentic AI · AI Agents · AI Shorts · Applications · Artificial Intelligence · Editors Pick · For Devs · New Releases · Software Engineering · Staff · Tech News · Technology · Uncategorized
原始連結
https://www.marktechpost.com/2026/09/17/anthropic-launches-claude-code-projects-in-beta-parallel-cloud-sessions-that-keep-running-after-you-close-your-laptop/

摘要原文

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. 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. Standing context is set once and reaches each new thread: the project's repositories and uploaded files, its project instructions of up to 16,000 characters, and project memory that Claude writes and reads through a MEMORY.md index. Memory in practice: the release moved to Friday, or who to check with before touching billing. Each thread also clones every project repository and loads CLAUDE.md , skills and plugins from all of them. Permission rules, hooks and env behave differently. They apply only from the directory the thread starts in, so a single repository project honors them and a multi repository project does not. MCP tools arrive through the connectors on your claude.ai account. The project conversation itself has no connectors, so connector work must go to a thread. The Overview pane groups threads by state: Ready for review, Waiting on you, Working, Landing, Idle and Resolved. A Library tab collects uploaded files and files the threads produced. A project uses plan limits faster than a single session, because every running thread is a full session. Anthropic exposes a per project Usage tab plus separate model and effort settings for the coordinator and for threads. A new project runs Opus everywhere, high effort for threads and low effort for the conversation. Idle threads also wake and spend again when CI fails or a review comment lands. The enforced ceiling is 200 new threads per day across your projects, and a thread that hits a usage limit waits and resumes on its own. Check out the Anthropic announcement , Claude Code projects documentation and @ClaudeDevs launch pos t . All credit goes to the researcher of this project. Also, feel free to follow us on Twitter and don’t forget to join our 150k+ML SubReddit and Subscribe to our Newsletter . Wait! are you on telegram? now you can join us on telegram as well. Need to partner with us for promoting your GitHub Repo OR Hugging Face Page OR Product Release OR Webinar etc.? Connect with us The post Anthropic Launches Claude Code Projects in Beta: Parallel Cloud Sessions That Keep Running After You Close Your Laptop appeared first on MarkTechPost .

由 claude-code/sonnet 自動生成