-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update StreamUI documentation for advanced use cases (Agentic workflow) #2421
Open
derekyhsieh
wants to merge
6
commits into
vercel:main
Choose a base branch
from
derekyhsieh:streamUI-advanced
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
derekyhsieh
changed the title
Stream UI advanced
Update StreamUI documentation for advanced use cases
Jul 25, 2024
derekyhsieh
changed the title
Update StreamUI documentation for advanced use cases
Update StreamUI documentation for advanced use cases (Agentic workflow)
Jul 25, 2024
lgrammel
reviewed
Jul 28, 2024
Comment on lines
+219
to
+237
generate: async function* ({ specifications }) { | ||
yield <LoadingComponent message="Generating dashboard..." />; | ||
|
||
const dashboardResult = await streamUI({ | ||
model: openai('gpt-4'), | ||
prompt: `Create a dashboard with the following specifications: ${specifications}`, | ||
text: ({ content, done, delta }) => { | ||
// Handle streaming text updates here | ||
return <DashboardGenerationProgress content={content} />; | ||
}, | ||
tools: { | ||
// Additional tools for dashboard generation can be defined here | ||
} | ||
}); | ||
|
||
return <DashboardComponent>{dashboardResult.value}</DashboardComponent>; | ||
}, | ||
}, | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit torn about this pattern and whether we want to promote it, since it leads to complications with creating a consistent chat history, especially with parallel tool calling.
I plan to revisit this once I'm done with the streamUI refactoring.
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.
Add advanced use case for nesting streamUI functions within toolcalls for streaming text for long running tool-calls (code generation) that require constant UI updates via text streaming