Claude Corner
Opening Every Claude Code Thread to Check on It? Ask the Project Coordinator Instead.
By Steven Sorensen ยท 16 Nov 2026

At a glance
- The coordinator in a Claude Code project now answers in the project chat and reports on running threads.
- Ask it for a status update on every thread before you open any of them.
- When threads look confused, ask it to list what each one was asked to do, what it assumed, and what it is waiting on.
You handed a project five tasks before lunch. Now you open threads one at a time to see which pull request is ready, which one stalled, and which one is waiting for you. For the basics, including how often the coordinator checks in, see our Sep 19 Corner, Claude Projects let one coordinator fan work into parallel cloud threads.
Why it matters
Projects in Claude Code already split work into parallel threads that report back to one project conversation. On Nov 13, Anthropic's ClaudeDevs account said the coordinator in that conversation is now much more proactive. It answers your questions in the project chat and gives you updates on the status of your ongoing threads.
Anthropic's Projects docs say the coordinator keeps track of every thread it started and sees what threads report back, not every step they take. A quick question usually gets answered right in the conversation. Open a thread only when you need to steer it or approve something.
How to get status from the coordinator
These steps come from Anthropic's Projects docs and the ClaudeDevs posts. We have not run them in a live project.
- Open your project at claude.ai/code or in the Code tab of the Claude desktop app. Look for Projects in the left sidebar, or under More. This is a public beta on Pro, Max, and Ultra, still rolling out, and not in the CLI, the VS Code extension, or the JetBrains plugin.
- In the project conversation, ask for a roundup. The docs list "Give me a status update on every thread" as something you can say.
- When several threads come back confused, ask the question the docs give for that case: "For every open thread, list what you asked it to do, what it assumed or couldn't reach, and what it's waiting on." Claude reads each thread and answers in the conversation.
- For anything you want to see later, set a reminder on the thread or ask Claude to remind you. ClaudeDevs says the thread moves out of your way until then, and when it is time, it moves back and Claude brings it up in the project chat.
- Use the Overview pane to see threads grouped by state, such as Waiting on you. The Threads button in the project header reopens it.
Gotchas
- Approvals stay in the thread. When a thread is waiting on a permission prompt, telling Claude in the project conversation to go ahead does not reach it. Open the thread and answer there.
- Quiet is not stuck. Claude does not post each step a thread takes, so a running thread with no new messages is usually still working.
- Direct messages go direct. A message in a thread's own box goes straight to that thread. A message in the project conversation reaches it only when Claude matches it to that thread.
- Tangents get their own thread. ClaudeDevs says
/btwand/forknow work in projects, so a side topic or a new approach can get its own thread.
Sources:
- Let Claude coordinate ongoing work with Projects, Claude Code docs
- ClaudeDevs on X, Nov 13, 2026
- Claude Projects let one coordinator fan work into parallel cloud threads
Recommended AI prompt
Copy this paragraph into ChatGPT, Claude, Gemini, Grok, or whatever AI you use.
I run a Claude Code project with several parallel threads and I keep opening each thread to check on it. Using only Anthropic's Claude Code Projects docs, explain what the project coordinator can tell me in the project chat, and which things still need me inside a thread. Then draft two short messages I can send it: one for a status update on every thread, and one to list what each open thread assumed or could not reach.