Unify context picker across template launch and create-agent dialogs - #562
Merged
Conversation
Extract shared ContextPicker component from the template launch dialog and use it in both the create-agent and template launch flows, ensuring consistent UX for file/link/clipboard attachment across the app. Co-Authored-By: Claude Opus 4.6 <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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
ContextPickercomponent from the template launch dialog's inline context picker implementationcreate-agent-dialog.tsx(~400 lines removed) andautomations-launch-dialog.tsx(~500 lines removed) with the shared componentDetails
The template launch dialog and create-agent dialog each had their own full implementation of the context picker UI (clipboard reading, paste-mode fallback, file input, link drafts, add-context popover). This caused visual and behavioral drift between the two flows.
The shared
ContextPickercomponent:onDraftInvalidcallback so parents can gate submit buttons on link draft validitytestIdPrefixprop for E2E test targeting across both layoutsonClipboardTextcallback absence gracefully (shows feedback instead of silently no-oping)Test plan
pnpm run check)pnpm run finalize:web)🤖 Generated with Claude Code