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
The input template should NOT be visible to the user, and should essentially act as a 'local' system message for that active conversation. As of the latest build, the input template is visually injected into every message the user sends.
Steps to Reproduce
Enter an input template: Act as a virtual assistant powered by model: '{{model}}', now time is {{time}}, response in {{lang}} lang, my input is:'''{{input}}'''
Write a message in the chatbox
Watch as the input template message is clearly visibly after every sent message.
Expected Behavior
The input template message should not show up for the user, just like the global system message does not get visually injected into the user's messages.
Screenshots
Deployment Method
Docker
Vercel
Server
Desktop OS
Win10
Desktop Browser
Chrome
Desktop Browser Version
No response
Smartphone Device
No response
Smartphone OS
No response
Smartphone Browser
No response
Smartphone Browser Version
No response
Additional Logs
No response
The text was updated successfully, but these errors were encountered:
Bug Description
The input template should NOT be visible to the user, and should essentially act as a 'local' system message for that active conversation. As of the latest build, the input template is visually injected into every message the user sends.
Steps to Reproduce
Act as a virtual assistant powered by model: '{{model}}', now time is {{time}}, response in {{lang}} lang, my input is:'''{{input}}'''
Expected Behavior
The input template message should not show up for the user, just like the global system message does not get visually injected into the user's messages.
Screenshots
Deployment Method
Desktop OS
Win10
Desktop Browser
Chrome
Desktop Browser Version
No response
Smartphone Device
No response
Smartphone OS
No response
Smartphone Browser
No response
Smartphone Browser Version
No response
Additional Logs
No response
The text was updated successfully, but these errors were encountered: