Title: Projects: let a thread wait for another thread's completion, and let loc… #109202

What happened
Title: Projects: let a thread wait for another thread's completion, and let local (Remote Control) threads message other threads

Setup: One project with role-split threads. Cloud thread A (e.g., a daily delivery role) requests work, and a local thread B (Remote Control, site folder on the user's PC) performs it. Requests go through the coordinator.

What happened (2026-11-12, JST): Thread B finished at 13:03 and reported to the coordinator, and the user approved it at 13:12. The coordinator received the report but did not forward it to thread A, which was waiting. It only posted one line in the project conversation. Thread A is not woken by other threads' posts, so it stayed unaware for about 90 minutes, until the user asked "did you confirm?" at 14:38.

Docs: The Projects page says threads report back to the project conversation. It does not describe a way for a thread to wait for another thread's completion, or for a local thread to message other threads. Forwarding currently depends on the coordinator's judgement each time, and gaps cannot be prevented structurally.

Requests

Let a thread register "wake me when thread X reports or posts next," and wake it automatically.
Let local (Remote Control) threads send messages directly to related threads (today they can only reach the coordinator).
If 1–2 are not feasible, give the coordinator a tracked "waiting threads" list and auto-forward completion reports to them.
Reference: Claude Code session session_01EDeRS1vDphRYeyuZg5pAo6

Environment

• Filed from: Report a problem in Claude Code
• Project ID: chan_0178enTxAQQqfqc9ZfrF6ECs
• Feedback ID: 711ea290-270a-473a-9fae-04a2c4163acc