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
Context control refers to the ability for the user to control which parts of the input file gets sent to the LLM as part of the input prompt (the context).
Current Status
In Prapti, the default behavior is that text prior to the first message heading belongs to the hidden @_head message which, like all hidden messages, is not sent to the LLM. All other non-hidden, non-disabled messages are sent to the LLM. (Recall, hidden messages have roles starting with an underscore, e.g. ### @_user and disabled messages have the form ### //@user see the docs for more info.)
Ideas
Some combination of the following context control commands are desirable (i.e. our users, or users of other systems have requested them or found them useful).
%reset / %clear / %restart / %discard:
discard all previous prompts (not sure of good name)
%isolate:
only submit the current message
%isolate-push isolate-pop
conduct a nested isolated conversation that begins with isolate-push and ends with isolate-pop. while isolate-push is active only messages in that conversation are sent to the LLM. after isolate-pop, those messages are no longer sent to the LLM
%always-isolate
a persistent mode where every input message is isolated (submitted by itself)
Typically the above would only control ### @user messages you'd want to retain the system prompt. But maybe there are cases where you'd want to control the system prompt too?
The text was updated successfully, but these errors were encountered:
Context control refers to the ability for the user to control which parts of the input file gets sent to the LLM as part of the input prompt (the context).
Current Status
In Prapti, the default behavior is that text prior to the first message heading belongs to the hidden
@_head
message which, like all hidden messages, is not sent to the LLM. All other non-hidden, non-disabled messages are sent to the LLM. (Recall, hidden messages have roles starting with an underscore, e.g.### @_user
and disabled messages have the form### //@user
see the docs for more info.)Ideas
Some combination of the following context control commands are desirable (i.e. our users, or users of other systems have requested them or found them useful).
%reset / %clear / %restart / %discard:
discard all previous prompts (not sure of good name)
%isolate:
only submit the current message
%isolate-push isolate-pop
conduct a nested isolated conversation that begins with isolate-push and ends with isolate-pop. while isolate-push is active only messages in that conversation are sent to the LLM. after isolate-pop, those messages are no longer sent to the LLM
%always-isolate
a persistent mode where every input message is isolated (submitted by itself)
Typically the above would only control
### @user
messages you'd want to retain the system prompt. But maybe there are cases where you'd want to control the system prompt too?The text was updated successfully, but these errors were encountered: