upcoming features and improvements - feedback wanted

[dancer]

description

we've been working on some exciting updates to the chatbot and would love your feedback on what features you'd like to see next!

recently completed

• upgraded to ai sdk v5.0.26 with latest stable packages (see #1139)
• fixed all breaking changes and compatibility issues
• added proper type definitions and resolved dependencies

currently in progress

• implementing ai elements component library
• enhanced conversation interface with improved scrolling
• modernized input components with better form handling

planned features

• ai gateway integration for model routing
• improved message rendering and markdown support
• better accessibility and keyboard navigation

what would you like to see?

please comment below with features you'd like to see added:

• new ai model integrations?
• specific ui/ux improvements?
• performance enhancements?
• developer experience improvements?
• other ideas?
• comment anything

your feedback helps us prioritize what to build next!

[yamz8]

Mcp support could be nice

[brandonmcconnell]

Support for different databases and auth providers would be a huge win.

IIRC, using the template today requires setting up a blob store, a Neon database, and using Grok. It would be nice to have some flexibility there.

The biggest blocker for me in using the chat SDK template in the past was the lack of BetterAuth support. Nowadays, that's a deal-breaker for me.

[yamz8]

Library for generated artifacts

[danielmari2]

i was just trying how this works, first time here. already found some errors within less than 5 min playing with it:

Bugs

1. npm i doesnt work properly
2. when asking the chatbot to "createDocument", it opens a popup and starts writing on it, however, this breaks completely the UI, whenever you try to navigate to another chat or click any button, it reopens this popup constantly
3. when "createDocument", you have made it so it can have "revisions" but I'm unable to make it the chatbox edit any of these revisions. ex: Edit section 3. Chatbox response: section 3 doesn't exit..

Nice to have features

• Social login
• "Premium" and "Free" acounts with payment service provider like Stripe, account limitations, etc.
• Folders for chats
• "Team" accounts
• Prompt improver (add button next to the send button to improve the current prompt using AI)

[raky291]

In my case, I would like to see the chatbot updated to Tailwind and Shadcn v4. I've created a PR with these changes; it would be great if you could review it.

#1134

Also other features I would like to see:

• File support (PDF and others)

[AlexanderCGO2]

It should be easy to create an Artifacts UI , for every use case like editing text, image, audio, video, and store artifacts like pages in a book, to a library, so you may go back in history and it would be awesome to support realtime collaboration on artifacts

[jeanbaptiste-portier]

Hey, first off, thank you for the fantastic work on this template. I'm using it as a founder and have some feedback from the perspective of someone who's testing it / modifying it, but doesn't have huge technical depth to truly understand the whole codebase rapidly.

Documentation for a Broader Audience

The existing documentation, especially the two architecture diagrams for the Chat SDK, was incredibly helpful for getting up to speed quickly. Expanding on this would be fantastic.

• For Developers: More detailed guides on common customizations, like adding or removing tools, leveraging artifacts for one or two use cases with explanations on modifications

• For AI/LLMs: Including the Chat SDK documentation in the Vercel MCP and adding a project-specific LLM.txt file would make it much easier to use coding agents for faster customization.

User Experience Ideas

Here are a few small UI/UX thoughts that came up during use:

• Persona Selection: A simple dropdown to set the AI's tone or personality in the chat interface.

• Chat Organization: A way to organize or collapse chats in the sidebar, perhaps with folders.

• Easier Sharing: A one-click option to copy a chat's shareable URL directly from the sidebar seems more intuitive to me if the template is meant for chat sharing. The current multi-step process (dots -> share -> select visibility? ) feels a bit cumbersome in the sidebar, and doesn't actually lead to any sharing, just visibility rules change.

Bugs I've Encountered

Sharing a few recurring bugs I've run into:

• Model Selection Dropdown: The model selection doesn't always seem to apply immediately within an active conversation. For example, if I switch from a "reasoning" model back to a standard "chat" model, I still see "thinking" tokens until I refresh the page.

• Document Creation Glitches: After creating a document, it sometimes reappears when I open unrelated, older conversations.

• Revisions UI: The revisions feature is a great concept, but applying suggestions or polishing text doesn't seem to result in any actual changes to the document.

Thanks again for building such a solid starting point, it's a blessing

[adityamiskin]

Shared chat context with persistence would remove a lot of prop drilling

[spookiaction]

Glad to see progress on a great template!
I would LOVE to see migration from AI v4 to v5. A lot of people forked well before v5.
I attempted a migration and it did Not go well. Some guide that at least starts at v4.x ai with messages parts that describes a migration path to your latest, including artifacts in the DB, would be Most welcome.

[shahabmohi]

Thank you for your work!

Couple of issues I wanted to address:

1- The tool component from the AI SDK seems more suitable for agentic coding sessions, rather than properly displaying the correct information for an artifact.
2- I think it would be great if we could organize the chats into projects, and allow users to search projects and files.
3- The coding artifact could use a total makeover. At the moment, it doesn't even auto-execute the code, and there are no visual cues to guide the user towards it.
4- I think we all understand that it needs easier integration with different auth providers.

Thanks again!

[dancer]

thank you everyone for the feedback i will take all of it into consideration we will be releasing a video soon with the current changes today/tmr and then continue from there

if anyone does make pr's be sure to ping me! i would love to take a look, i have added ai elements and gateway and want to keep adding more so let me know

[xn1cklas]

I've been working with the AI Chatbot as template for a client project for half a year now. It has been an amazing starting point to built rich AI applications with.

The parts I extended heavily focused on tool calls.
I think the repo would benefit from having a centralized approach to move artifacts and tool definitions closer together.

An example could be:
`
ai/
└── tools/
└── weather/
├── get-weather/
├── components/
│ ├── server/
│ └── client/

`

Some artifacts like the sheet are coupled with multiple tool calls. If it makes sense they could all be within ai/tools/sheet or a shared primitives directory could be added.

This would make copying tools from the Chatbot Repo into a local repo straight forward.