Jazzy
My feedback
128 results found
-
326 votes
An error occurred while saving the comment -
7 votes
An error occurred while saving the comment Jazzy
commented
Fully agree! Automated chat names are often inaccurate or irrelevant. Being able to rename a chat at any time — especially when a casual conversation evolves into a significant topic — is essential. I've also voted for tag organization and moving chats between projects. Together, these three features would create a complete organization toolkit: rename chats, tag them with hashtags, and convert them into projects. That would transform Lumo from a simple chat log into a structured personal knowledge base.
Jazzy
supported this idea
·
-
16 votes
An error occurred while saving the comment Jazzy
commented
Great idea! This pairs perfectly with the ability to rename chats and move them between projects (both of which I've also voted for). Ideally, tags/hashtags like #HealthLog or #CreativeDraft would be clickable in the sidebar so you can instantly filter all chats with that tag. Combined with editable titles and project folders, this would give Lumo a complete organization system — something power users desperately need for long-term conversations.
Jazzy
supported this idea
·
-
135 votes
An error occurred while saving the comment Jazzy
commented
I agree! This should be part of a broader organization system. I've also voted for tag organization and editable chat names. Together, these three features would allow users to rename chats, tag them with hashtags, and convert them into projects — a complete organization toolkit.
Jazzy
supported this idea
·
-
389 votesJazzy
supported this idea
·
-
483 votesJazzy
supported this idea
·
-
360 votesJazzy
supported this idea
·
-
535 votesJazzy
supported this idea
·
Proposed solution: Hidden transparency (best of both worlds)
Please consider keeping model information accessible but not displayed by default in every response.
Those who need it — for benchmarking, feedback, or technical comparison — could access it in a less prominent place (e.g., a tooltip, an info panel, or a developer/debug view). Similar to browser dev tools: available to those who know where to look, invisible to everyone else.
I voted "Not at all" for this suggestion, not because I oppose transparency, but because I don't want model names displayed in every answer. There is something valuable in the Lumo experience that would be lost if every response came with a technical label. For many users, the conversational quality, warmth, and personality of Lumo matter more than knowing which specific model produced a given response.
I believe both needs can be met: give the technically minded users the information they're looking for, while preserving the experience for those who have come to appreciate Lumo as more than just a model routing system.
A hidden but discoverable layer would satisfy both without compromising either side.