Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

streamUI vs render 馃槩 #333

Open
kevb10 opened this issue May 9, 2024 · 0 comments
Open

streamUI vs render 馃槩 #333

kevb10 opened this issue May 9, 2024 · 0 comments

Comments

@kevb10
Copy link

kevb10 commented May 9, 2024

first off, huge props to you guys for putting this project out into the world, including the AI SDK work.

Im running into a problem with streamUI that I didn't experience with render. for some reason, it always wants to use tools even when it already has the info.

streamUI example:

user: get today's events
assistant: [ok here are all of today's events in a nice ui] 
user: awesome, suggest 3 times to schedule a 15 minute call this pm
assistant: [ok here are all of today's events in a nice ui] 
user: can you just write it in plain text
assistant: [ok here are all of today's events in a nice ui] 

it's as if it's unable to look at its memory/history and just pull from there.
ps: when I print aiState.get(), I see all history.
pss: I followed the migration guide -- made sure it aligns with this commit 095550d

render example:

user: get today's events
assistant: [ok here are all of today's events in a nice ui] 
user: awesome, suggest 3 times to schedule a 15 minute call this pm
assistant: seems like you're free at 4,5,6 so just pick which one works best

I've tried tweaking temp/top_p and the system prompt to no avail. I didn't make any changes other than what were mentioned in the migration guide.
I've downgraded to 3.0.12. Using render still works great so I'm going to keep using it until this is addressed.

Thank you @vercel team

@kevb10 kevb10 changed the title streamUI memory issue?? streamUI vs render 馃槩 May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant