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
Hello,
Would it be possible to remove "WARNING: Custom system prompt override active. This can severely break functionality and cause unpredictable behavior." from the chat tab? I think it would be more appropriate in the Prompts tab. I'm fully aware that I'm overriding system prompts, and I find this permanent warning slightly annoying when working :-)
Describe the proposed solution in detail
To display this warning in the Prompt tab instead.
Technical considerations or implementation details (optional)
No response
Describe alternatives considered (if any)
No response
Additional Context & Mockups
No response
Proposal Checklist
I have searched existing Issues and Discussions to ensure this proposal is not a duplicate.
This proposal is for a specific, actionable change intended for implementation (not a general idea).
I understand that this proposal requires review and approval before any development work begins.
Are you interested in implementing this feature if approved?
Yes, I would like to contribute to implementing this feature.
The text was updated successfully, but these errors were encountered:
What problem does this proposed feature solve?
Hello,
Would it be possible to remove "WARNING: Custom system prompt override active. This can severely break functionality and cause unpredictable behavior." from the chat tab? I think it would be more appropriate in the Prompts tab. I'm fully aware that I'm overriding system prompts, and I find this permanent warning slightly annoying when working :-)
Describe the proposed solution in detail
To display this warning in the Prompt tab instead.
Technical considerations or implementation details (optional)
No response
Describe alternatives considered (if any)
No response
Additional Context & Mockups
No response
Proposal Checklist
Are you interested in implementing this feature if approved?
The text was updated successfully, but these errors were encountered: