Demo: triggerAngie with programmatic and hash deep links - #52
Merged
Conversation
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.
Summary
demo/trigger-angie-prompt/— interactive demo for opening Angie with a pre-filled prompt viasdk.triggerAngie()#angie-prompt=…, optionalangie-new-chat=true)demo/index.htmlTest plan
npm run demoand open/demo/trigger-angie-prompt/✨ PR Description
1. Problem & Context
New demo showcasing
triggerAngie()API with two interaction patterns: programmatic calls from UI and hash-based deep linking for shareable URLs. Demonstrates waitForReady flow and newChat option.2. What Changed (Where)
3. How It Works
Hash params parsed on load via
readPromptFromHash()and consumed before clearing hash. Prompt state flows: input field → getPrompt() → triggerAngie({ prompt, options: { newChat } }). Event listeners on buttons (fill/new-chat), chips (quick prompts), and in-page hash links (preventDefault, parse, trigger). New-tab hash links skip interception. Status element updated with response.requestId on success or error details on failure.4. Risks
None—isolated demo module. Minor: hash link UX assumes users won't manually edit params (gracefully fails with "missing prompt" error). New-tab links don't handle hash consumption, but that's by design (separate session).
Generated by LinearB AI and added by gitStream.
AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Description using Guidelines Learn how