Open castedo opened 10 months ago
I am thinking of enabling Jinja templates for a key called "system_prompt" which will obsolete "chat_system". "chat_system" which will not support template syntax gets deprecated. "system_prompt" is always interpreted as a Jinja template.
Add a top-level key parameters
which exposes parameters that a calling program can specific. Something like
[parameters.lang_tag]
default = "en-US"
[parameters.lang_tag.map]
"en-US" = { dialect = "American" }
"en-GB" = { dialect = "British" }
[parameters.mime_type.map]
default = "text/markdown"
[parameters.mime_type.map]
"text/markdown" = { format = "Markdown and HTML" }
"application/x-latex" = { format = "LaTeX" }
where dialect
and format
show up as Jinja template variables in system_prompt
.
Some parts of prompts change slightly depending on scenario. In particular, making corrections based on American vs British English. Another example is editing Markdown vs LaTeX formatted source text.
This feature is to enable the
chat_system
settings inside a prompt request settings file to contain a template with a placeholder for English dialect and a way to select between American and British in thecopyaid.toml
user configuration file.