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

System Prompt Library #69

Open
Rossi1337 opened this issue Jun 23, 2024 · 3 comments
Open

System Prompt Library #69

Rossi1337 opened this issue Jun 23, 2024 · 3 comments
Assignees
Labels
Department: Backend Issues related to the logic of the code Priority: Low Status: On Hold Type: Enhancement Request to change or add a feature

Comments

@Rossi1337
Copy link
Collaborator

I use different models for different purpose. I realized that I would like to be able to switch quickly the "system prompt" for a model.
For example use one prompt for "Java Programming" and another one for "Flutter Programming", one for casual chatting and one to solve reasoning problems. With that you could give your models different personalities and switch between them.

My implementation idea is the following.
Add a feature to create a prompt library. Each of them should have a unique name and the "prompt text".
We could add a new page "Prompts" to manage these (create, edit, delete).
In the chat window next to the model selection we would then allow to select from a drop down list the "prompt" to use.
If none are in the library or nothing is selected we use the "default prompt" or if overriden the "model specific default prompt".

@Rossi1337 Rossi1337 added the Type: Enhancement Request to change or add a feature label Jun 23, 2024
@WilliamKarolDiCioccio
Copy link
Owner

WilliamKarolDiCioccio commented Jun 24, 2024

I agree with you. I was about to open a new discussion to understand which path to take. As you know docs search is a feature the app will provide. I was thinking of a "Vault" section to upload images, documents (pdf, plain text, code...) and eventually prompt templates. Those assets would be categorized and used for RAG or to provide general customization. Let me know what you think of my idea. Anyways I think it would be wise to delay that a bit, the app still needs some architectural refinements to make it more flexible and performant (rework providers according to a cleaner strategy and make some widgets like ChatMessage more readable). After that we can go on to the next development phase adding web (already done some research) and docs search

@Rossi1337
Copy link
Collaborator Author

For documents I would see it like this.
You drag a document into your chat and it is indexed on the fly into a "in memory" or embedded vector database. Then it will be available in your current chat session (via RAG).
If you start a new session all images and additional documents should be removed and the vectory store should be cleared.
I do not want to index all my local files or documents or something like that. I would do this on the fly for documents I want to work with. Not sure how fast this is.

@WilliamKarolDiCioccio
Copy link
Owner

@Rossi1337 I completed the exams with pretty good results 😎. I'll be back working on the app by tomorrow

@WilliamKarolDiCioccio WilliamKarolDiCioccio added Priority: Low Department: Backend Issues related to the logic of the code labels Aug 14, 2024
@WilliamKarolDiCioccio WilliamKarolDiCioccio self-assigned this Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Department: Backend Issues related to the logic of the code Priority: Low Status: On Hold Type: Enhancement Request to change or add a feature
Projects
None yet
Development

No branches or pull requests

2 participants