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
Open Question: If project-info or other variables such as context summary in agent prompts do not exist, the variable remains unresolved like this "{{prompt:project-info}}"
We might consider to change this behavior:
We generally remove unresolved variables (and functions) => might be an issue for debugging
We remove prompt fragment only that cannot be resolved (i.e. return "")
We introduce a syntax like {{prompt:project-info}}? to make things that are optional
We generally remove unresolved variables (and functions) => might be an issue for debugging
Yeah, I'd not be in favor of that. Also if it would unexpectedly remove any text that matches the function or variable pattern from prompts.
We remove prompt fragment only that cannot be resolved (i.e. return "")
I think this is the best option. I'd output a log warning that prompt:abc wasn't found and then return an empty string. This also has the advantage that we are leaving that corner case to decide for the variable provider.
We introduce a syntax like {{prompt:project-info}}? to make things that are optional
Open Question: If project-info or other variables such as context summary in agent prompts do not exist, the variable remains unresolved like this "{{prompt:project-info}}"
We might consider to change this behavior:
We generally remove unresolved variables (and functions) => might be an issue for debugging
We remove prompt fragment only that cannot be resolved (i.e. return "")
We introduce a syntax like {{prompt:project-info}}? to make things that are optional
@planger WDYT?
The text was updated successfully, but these errors were encountered: