Repository navigation
feat(projects): the coordinator starts threads with a brief, answered in the background - #593
Merged
Merged
Conversation
… in the background The coordinator's start_thread tool, the API and MCP take a brief: the thread's first question, answered in the background as the project's owner, with their tools, approvals and budgets. The coordinator reads threads and marks them done; stale briefs are swept. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015ZmJ29Kc4iXuyKqCRifAH5
This was referenced Oct 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Adeel · project thread
Description
Before: a project's coordinator could talk about the project, but every thread had to be started and asked by hand.
After: the coordinator starts threads itself with a brief, the thread's first question, and the thread answers it in the background as the project's owner, with their tools, approvals and budgets. The coordinator also reads threads and marks them done. You or an agent can start a thread with a brief the same way, over the API (
POST /api/v1/projects/{id}/threadswithbrief) or MCP. A brief left answering when the server stops is marked so after a restart, rather than spinning forever.How:
projects.briefsaves the question (via: "project") and answers it on a daemon thread through the existing chat path; four Toolbox tools (project_threads,read_thread,start_thread,finish_thread) are offered in a project's coordinator,start_threadasking first when the conversation has read outside text. Second of the projects PRs after #571; the web page and scheduled threads follow.Motivation and Context
Adeel asked for projects that work like this Claude project: a coordinator that starts threads and threads that do the work.
Types of changes
!in the title)Checklist:
make hookschecks it on commit).docs/accordingly.changelog.d/projects.md.Done questions (AGENTS.md)
brief, MCP and the coordinator's own Toolbox tools (test_the_coordinator_starts_threads_with_a_brief,test_a_brief_from_the_api_or_an_agent_is_answered_in_the_background).start_threadasks first once outside text was read (test_starting_threads_after_reading_outside_text_asks_first); threat model row updated.start_threadwaits for approval.make openapi).Local CI:
ci/local-ci.shpassed the backend, Next.js, pre-commit and title jobs on this change before its rebase onto the latest main; the projects and MCP tests pass after it.Generated by Claude Code