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

Enhancement: Allow for character card 'personality' 'injection' into chat pipeline #486

Open
Tracked by #519
rmusser01 opened this issue Jan 14, 2025 · 0 comments
Open
Tracked by #519
Assignees
Labels
enhancement New feature or request Feature-Addition
Milestone

Comments

@rmusser01
Copy link
Owner

As a user, I would like to have my chats with my LLM 'flavored', so that I may use a persona for chatting, but without the baggage of a full character card.

I start a chat, and select a personality to be injected as the AI 'profile'. The core profile is always as an assistant who does what the user asks, but takes on the persona and mannerisms of the injected character profile.

The injected character profile would be user-defined and optional. It would replace/extend the existing chat prompt, and would be injectable during the summarize() or chat() pipelines.

This would be separate in whole from the character card DB/storage and would be treated as a 'RAG Chat' item.

Solution would be that as a user I may select from a predefined list of characters, from my character card selection, and have the selected character persona injected into the chat/RAG system prompt, so that the response is flavored as if it was coming from that character/persona.
This remains injected for the entirety of the conversation, unless the user changes it, at which point the newly selected character persona replaces the existing one, and future chat messages will take place from the persona of the newly selected character.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Feature-Addition
Projects
None yet
Development

No branches or pull requests

1 participant