Skip to content

feat(projects): projects with a goal, namespaces, a coordinator and threads - #571

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

adeelahmad merged 9 commits into
mainfrom
claude/project-thread-2i3nwt

Conversation

@adeelahmad

Copy link
Copy Markdown
Owner

Requested by Adeel · project thread

Description

Before: every conversation stood alone. To work toward something bigger (a treehouse with your son, a move, a client's case) you explained the goal again in each chat, and nothing held the pieces together.

After: a project has a name, a goal in your words, instructions and one or more namespaces. It comes with a coordinator conversation about the project as a whole, which is told about every thread, and threads: conversations scoped to the project's namespaces, marked done when finished. Every answer in a project reads its goal and instructions. Your own conversations can be brought in or taken out, and deleting a project keeps them.

How: a project table (SCHEMALESS, applied at start), a project field on chats, app/domain/projects.py, /api/v1/projects and four MCP tools (list_projects, read_project, create_project, update_project). The Toolbox adds the project's note to the system prompt, wrapping the thread list with untrusted.wrap. This is the first of a few small PRs: the coordinator starting threads with a brief, the web page and scheduled threads follow.

Motivation and Context

Adeel asked for projects that work like this Claude project: a goal, namespaces, conversations through any channel, a coordinator, and threads (scheduled ones later).

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 wrote it under ## Unreleased in CHANGELOG.md.

Done questions (AGENTS.md)

  • Goal: the backend core of projects; briefs, the web page and scheduled threads follow in their own PRs (listed in docs/projects.md).
  • Agents: REST API and MCP tools (test_agents_use_projects_over_mcp).
  • Zero setup: no new prerequisite; the table is created at start.
  • Fewest clicks and keystrokes: n/a in this PR (no UI yet); a project needs only a name and a namespace.
  • Configurable: n/a, no new setting.
  • Light: no new dependency or service.
  • Private and secure: owner-only, draws only on namespaces the owner can read; thread titles reach the coordinator as data; threat model row added.
  • Cost: no extra model calls; answers go through the existing chat path and activity ledger.
  • User decides: nothing runs on its own; existing chats are unchanged unless brought in.
  • Upgrades: new table and optional fields only; existing chats read as not in a project.
  • Honest: docs and README label it built, with planned parts listed.
  • Tests, docs and generated files updated (make openapi).
  • Open standards; no new dependency.
  • "Refine later" items in docs/projects.md.
  • Reuse: threads are ordinary chats; scope, Toolbox and MCP patterns reused.

Local CI: ci/local-ci.sh passed the backend, Next.js, pre-commit and title jobs on this commit; the server and upgrade jobs are re-running (one server test failed only under load and passes on its own).


Generated by Claude Code

@adeelahmad adeelahmad self-assigned this Oct 18, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015ZmJ29Kc4iXuyKqCRifAH5
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015ZmJ29Kc4iXuyKqCRifAH5
…leased)

The same change as #575, so the requirements check passes here.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015ZmJ29Kc4iXuyKqCRifAH5

Copy link
Copy Markdown
Owner Author

pre-commit failed on the requirements hook: "README › In progress: #400 is released (CHANGELOG.md); list it as built, with its checks". That isn't this PR's change. v0.15.0 released #400, so main has the same failure. I ported #575's fix for it (#400 moves to the built list, with its row in docs/requirements.md) in 90f686f. It does nothing once main has it.


Generated by Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015ZmJ29Kc4iXuyKqCRifAH5
The changelog paragraph moves to changelog.d/projects.md (#581).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015ZmJ29Kc4iXuyKqCRifAH5
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015ZmJ29Kc4iXuyKqCRifAH5
@adeelahmad
adeelahmad merged commit 2355aa7 into main Oct 18, 2026
12 checks passed
@adeelahmad
adeelahmad deleted the claude/project-thread-2i3nwt branch October 18, 2026 11:43
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