From 12be6036902ba9fa1b403310422e5f6f3e6c1875 Mon Sep 17 00:00:00 2001 From: Grail Finder Date: Sat, 17 Jan 2026 10:23:06 +0300 Subject: Chore: add alice-bob-carl card --- char-specific-context.md | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'char-specific-context.md') diff --git a/char-specific-context.md b/char-specific-context.md index d56a0cf..93c08c5 100644 --- a/char-specific-context.md +++ b/char-specific-context.md @@ -27,5 +27,10 @@ Bob: I also have a secret for you Alice __known_to_chars__Alice__ tag can be anywhere in the message. Sender should be also included in KnownTo, so we should parse sender name and add them to KnownTo. also need to consider user case (as in human chatting with llm). User also can assume any char identity to write the message and ideally the same rules should affect user's chars. +user has "Writing as {char}" (vars: persona and cfg.UserRole) +on persona change we should update tui text view to have atual for that character chat history Again, this is not going to work with openais /v1/chat endpoint since it converts all characters to user/assistant; so it is completion only feature. It also might cause unwanted effects, so we better have an option in config to switch this context editing on/off. + + +alternative approach to the tag string would be to have a judge agent to determine after each message what characters should hae access to it. but it means to make an additional call to llm after each msg. -- cgit v1.2.3