Feel free to submit feature requests and bug reports :)

A few quick asks on our part:
1. Search before posting! Your feedback has likely been submitted already
2. If you have multiple features to request, please create separate requests for each.

3. If submitting a bug, PLEASE SELECT “BUG REPORT” WHEN REPORTING

Gathering Interest

Suggest updated models to replace old favourites

Currently, when new model versions release, users must manually unfavourite outdated models and favourite the new ones. This is repetitive and easy to forget. Proposed Solution: Add a subtle update indicator to the model selector that surfaces when newer versions are available. UI Placement: A button with an update icon positioned next to the filter button. Clicking it reveals a checklist of updatable models with checkboxes to select which ones to update in the list. State Visual New updates available Accent-coloured icon, subtle pulse or badge Viewed but not updated Muted text colour, static icon All models current Hidden entirely This keeps the interface clean while making the update path discoverable without being pushy.

💡

Feature Request

In Progress

We hit an unexpected error - Vercel Security Checkpoint - VPN

Every now and then (I haven’t measured the exact time, but it seems every 15-30 minutes), the T3 Chat UI shows the above error message. The “Reload App” button doesn’t do anything when clicked. Pressing F5 to refresh the browser shows the Vercel Security Checkpoint for a bit, then the T3 Chat UI works again. This started last week or so, that’s also the first time I’ve seen the Vercel Security Checkpoint UI. The error seems to be related to that as well, given that the technical details are Vercel’s HTML document?! I should note that this only happens when I access T3 Chat from my company’s network. That also causes other problems like LLM answers only appearing after they’ve been fully “typed out”. In the network tab, I can see a lot of “429 too many requests errors” for some requests like “api/server-version” and “api/status”, which could be related.

🐛

Bug Reports

1