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
{{ message }}
Repository navigation
enable template placeholders in system_prompt message setting #2
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 the copyaid.toml user configuration file.
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.
changed the title [-]enable template placeholders in chat_system message setting[/-][+]enable template placeholders in system_prompt message setting[/+]on Jan 14, 2024
Activity
castedo commentedon Jan 14, 2024
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.
[-]enable template placeholders in chat_system message setting[/-][+]enable template placeholders in system_prompt message setting[/+]castedo commentedon Jan 14, 2024
Add a top-level key
parameterswhich exposes parameters that a calling program can specific. Something likewhere
dialectandformatshow up as Jinja template variables insystem_prompt.