Repository navigation
feat(web): continue from a subagent's work in a new chat tab - #109
Merged
Merged
Conversation
Continue in chat, in the agent detail view and the Agents list's right-click menu, opens a new chat tab of the thread whose draft carries the agent's task, result or error, and latest tool calls as a chat-summary chip. It starts a fresh conversation with that context rather than resuming the agent's provider session. 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 Agents panel makes delegated work easy to inspect, but there was no way to carry on an agent's line of work in its own conversation. Say an agent investigates three possible causes: you could read its findings, but not open a chat about the most promising one.
Continue in chat (a new icon in the agent detail header, and an item in the list's right-click menu) opens a new chat tab of the same thread, on the thread's model. The tab's draft starts with a chat-summary chip that holds:
subagentContinuationContextinpackages/client-runtimebuilds that text. It is pure and has tests. The tab is created by the existingforkThreadTabpath, which now accepts caller-supplied context in place of the source chat's summary. The context reuses thethread-tabrecord kind, so the chip, its preview, and how it is sent to the provider work as they already do. No contract or server changes.This first version starts a fresh conversation with the captured context. It does not resume the agent's provider session.
Surfaces: web and desktop. Mobile has no Agents panel, so it is not affected. All providers that populate the Agents panel are covered, since this only uses the client-side agent fold. Docs:
docs/user/thread-sidebar.mdanddocs/fork-differences.mdupdated.Verification:
vp test run packages/client-runtime/src/state/agentPanelView.test.ts(25 passed), web and client-runtime typecheck, and lint on the touched files. I have not tested it in a real client yet, so there are no screenshots.🤖 Generated with Claude Code (Claude Opus 5.5)