Repository navigation
feat(web): reference other threads from the composer @ menu - #86
Merged
Merged
Conversation
The @ menu listed only sibling chat tabs. It now also lists other unarchived threads in the environment, and the summary chip works in new draft threads. The handoff endpoint accepts any thread except the one composing. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
The composer's
@menu could only pull in a summary of a sibling chat tab. To carry context from any other chat, you had to copy and paste it by hand.What changed
@menu (apps/web/src/components/chat/ChatComposer.tsx,composerThreadReferences.ts): after sibling tabs, the menu lists unarchived threads in the same environment, from any project, matched by title and newest first. It shows 3 before you type and up to 6 once you type. The project name is the row description. The thread list is read once per query rather than subscribed, so streaming turns elsewhere don't re-render the composer.apps/server/src/threadTabs/http.ts): the handoff endpoint no longer requires sources to share a tab group with the composing thread, and the composing thread may still be a draft. Only referencing the thread itself is refused. The summary's title comes from the source thread.chat: <title>instead ofchat tab: <title>. The context kind is stillthread-tab, so contracts are unchanged.@chip. The docs already say so.docs/fork-differences.mdanddocs/user/thread-sidebar.md.UX
Typing
@subagentin a new thread lists matching threads from other chats above files:Picking one inserts its summary as a chip at the cursor:
Testing
composerThreadReferences.test.ts: filtering (environment, archived, excluded, query), ordering, and limits.server.test.ts: a draft can summarize another thread, and self-reference returns 400.Done by Claude Opus 5.5 in Claude Code (via T3 Code).
🤖 Generated with Claude Code