Skip to content

feat(projects): the coordinator starts threads with a brief, answered in the background - #593

Merged
adeelahmad merged 1 commit into
mainfrom
claude/project-thread-2i3nwt
Oct 18, 2026
Merged

adeelahmad merged 1 commit into
mainfrom
claude/project-thread-2i3nwt

Conversation

@adeelahmad

Copy link
Copy Markdown
Owner

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}/threads with brief) or MCP. A brief left answering when the server stops is marked so after a restart, rather than spinning forever.

How: projects.brief saves 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_thread asking 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

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change; ! in the title)

Checklist:

  • The title is a Conventional Commit.
  • My code follows the code style of this project (make hooks checks it on commit).
  • I added or updated tests.
  • My change requires documentation updates, and I have updated docs/ accordingly.
  • Users need more than the title to understand it, so I extended changelog.d/projects.md.

Done questions (AGENTS.md)

  • Goal: the coordinator starts and finishes threads, briefs answered in the background; the web page and scheduled threads follow (docs/projects.md).
  • Agents: API 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).
  • Zero setup: no new prerequisite.
  • Fewest clicks and keystrokes: n/a in this PR (no UI); one sentence to the coordinator starts a thread.
  • Configurable: n/a, no new setting.
  • Light: a thread per brief, no new service or dependency.
  • Private and secure: briefs run as the owner with their approvals; start_thread asks first once outside text was read (test_starting_threads_after_reading_outside_text_asks_first); threat model row updated.
  • Cost: one answer per brief through the activity ledger and budgets; nothing else calls a model.
  • User decides: nothing starts unless asked; a wary conversation's start_thread waits for approval.
  • Upgrades: new optional fields only.
  • Honest: docs label it built, with what's planned.
  • Tests, docs and generated files updated (make openapi).
  • Open standards; no new dependency.
  • "Refine later" items in docs/projects.md.
  • Reuse: the existing chat answer path, Toolbox approvals and MCP patterns.

Local CI: ci/local-ci.sh passed 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

… 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
@adeelahmad
adeelahmad merged commit 972897f into main Oct 18, 2026
12 checks passed
@adeelahmad
adeelahmad deleted the claude/project-thread-2i3nwt branch October 18, 2026 12:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants