Skip to content

feat(projects): a Projects page under Chat, with briefs answered in the background - #601

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: projects (#571) and their coordinator's briefs (#593) worked through the API, MCP and chat, but the web app had no page for them.

After: Projects sits at the top of Chat's conversation list (and lights Chat in the navigation). A project starts with just a name, in the current namespace; the goal and instructions are optional. A project's page shows its goal, a link to its coordinator, and its threads, open ones first, with the ones being answered marked Working. Typing a brief and pressing Enter starts a thread that answers it in the background while you stay on the page; Enter with nothing opens an empty thread. One click on a thread's checkbox marks it done. Edit and Archive sit in the page's menu, Archive with Undo. In Chat, a conversation in a project shows a chip back to it, and a thread being answered in the background shows "Working on it" and fills in when its answer is written.

How: /projects and /projects/[id] pages, components/projects/* on React Query over the generated client, polling only while a thread is answering; useChat polls an answering conversation that isn't streaming here. Third of the projects PRs; scheduled threads follow.

Motivation and Context

Adeel asked for projects that work like this Claude project; the web app is where people set them up and review them.

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 Projects page for setting up and reviewing projects; scheduled threads follow.
  • Agents: everything on the page is already in the API and MCP (feat(projects): projects with a goal, namespaces, a coordinator and threads #571, feat(projects): the coordinator starts threads with a brief, answered in the background #593).
  • Zero setup: no new prerequisite.
  • Fewest clicks and keystrokes: a project needs only a name (namespace defaulted, Name focused, Enter submits); a thread is a brief and Enter; done is one click; Archive has Undo instead of a confirm.
  • Configurable: n/a, no new setting.
  • Light: pages only, no dependency; polling only while something is answering.
  • Private and secure: the page shows only the signed-in person's projects, through the existing API.
  • Cost: no model calls of its own.
  • User decides: nothing starts unless the person types a brief.
  • Upgrades: no stored-data change.
  • Honest: docs and README label it built.
  • Tests, docs and generated files updated (projects.test.tsx, docs/projects.md "In the web app", requirements row).
  • Open standards; no new dependency.
  • "Refine later" items in docs/projects.md.
  • Reuse: the app's dialogs, toasts with Undo, nav and chat components.

Local CI: ci/local-ci.sh passed the backend, Next.js, pre-commit and title jobs before a clean rebase onto the latest main; the projects and chat tests and the type check pass after it.


Generated by Claude Code

…he background

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