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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unwanted past memories interfering when working in present for future! #2025

Open
JeetKaria06 opened this issue Nov 13, 2024 · 0 comments
Open

Comments

@JeetKaria06
Copy link

🚀 The feature

Motivation
When you are a developer and you are working on multiple side projects, bugs then you don't want some memories to interfere while working on some other things.

Problem
When I am working on some side project, I searched somethings like free tools for some usecase in one of the chatgpt conversations, now when I open new conversation and working on something else, I don't want those memories to interfere and alter my answers on chatgpt when I am working on something else.

Possible Solution
How about creating global memories and some local (or maybe categorizing it) and after dividing memories giving option in extension to select some of it when you think is relevant for current work you are doing.

And also initially create default memories according to where you are having conversation, if on chatgpt then chatgpt_some_unique_id, and then placing memories of that conversation inside that memory, then manually user goes and click some of them to be universal while some in a different category.

Conclusion
This may require some more brain storming on what the solution can be, but I think this might be a problem for many, not only for a developer like me.

Motivation, pitch

When you are a developer and you are working on multiple side projects, bugs then you don't want some memories to interfere while working on some other things.

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