Carlo
My feedback
3 results found
-
1,075 votes
Carlo
supported this idea
·
-
2 votes
Carlo
shared this idea
·
-
17 votes
Carlo
supported this idea
·
An error occurred while saving the comment
I support this — and would add that moving chats into a project
only solves half the problem. Even with chats filed inside a
project, the conversation content of individual chats is not
shared between them.
My scenario: I work with one living chat per topic within a
project. When I accidentally continue in an older, archived
chat — or open one to look something up and a discussion
develops there — any problem solved in that chat stays there.
My living chat has no knowledge of it. The only workaround is
manually asking for a summary, copying it, and pasting it into
the project instructions. That works, but it's exactly the kind
of manual step where things get lost silently.
What makes this confusing: the Lumo 1.3 announcement states that
"Lumo remembers all conversations and files associated with the
project" and "can immediately pick up where you left off because
it remembers all the context." In practice, the Project
Instructions and linked files are shared, but the conversation
content of individual chats is not.
So besides a "Move to Project" action, it would help enormously
if chats within a project could share context — either by
having access to each other's summarized history, or via a
per-project status section that chats can write conclusions to.
Either would make Projects feel like the workspace they are
positioned to be. Thank you for considering.