You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ability for Perplexity to have in app stored personal memory for the user customizations and knowledge.
🔍 Problem Statement
I am finding that I have to continuously inform Perplexity of things I have already stated in previous messages. Also, I like perplexity voice to speak at 1.5x the normal speed which you can do, but you have to do this in each new voice chat. Things like this should be stored into customizations so it’s an ever evolving system that gets better and more refined as you use it.
💡 Proposed Solution
Develop a user customization configuration to allow users to ‘store into memory’ on command, and allow perplexity to use these customizations with each new chat initiated. Also, the user should be able to allow perplexity to use previous threads in the knowledge-base when answering questions so that key details and information do not need to be repeated in subsequent discussions.
🚀 Feature Request
Ability for Perplexity to have in app stored personal memory for the user customizations and knowledge.
🔍 Problem Statement
I am finding that I have to continuously inform Perplexity of things I have already stated in previous messages. Also, I like perplexity voice to speak at 1.5x the normal speed which you can do, but you have to do this in each new voice chat. Things like this should be stored into customizations so it’s an ever evolving system that gets better and more refined as you use it.
💡 Proposed Solution
Develop a user customization configuration to allow users to ‘store into memory’ on command, and allow perplexity to use these customizations with each new chat initiated. Also, the user should be able to allow perplexity to use previous threads in the knowledge-base when answering questions so that key details and information do not need to be repeated in subsequent discussions.
📌 API Impact
No idea, I’m not a developer.
🔄 Alternatives Considered
No
📎 Additional Context
No
📧 For direct inquiries, please reach out to
david.beaton@me.com
The text was updated successfully, but these errors were encountered: