Thanks for stopping by to let us know something could be better!
Is your feature request related to a problem? Please describe.
I'm always frustrated when preparing a payload i have to always use the user role both for user messages and for applciation messages. Why don't we have a "developer" role for application generated (e.g. RAG) content. Like for example, you have the normal "conversation/history" model/user/model/user but then on every turn, you want to include a message that is generated by the client application containing things like the content of some files in the filesystem, a screenshot or some runtime metrics like 'Heap Memory Usage". Wouldn't it be semantically more clear for Gemini if there was a 3rd role like the openai "developer" role?
Describe the solution you'd like
Have another role called "developer"
Describe alternatives you've considered
putting like big banners in the application generated context like "THIS IS NOT A REAL MESSAGE FROM THE USER, THIS IS DYNAMICALLY GENERATED CONTENT, THE USER DOESN'T SEE THIS MESSAGE ON THE HISTORY, IT HAS BEEN CREATED BY THE APPLICATION"
Additional context
Add any other context or screenshots about the feature request here.
Thanks for stopping by to let us know something could be better!
Is your feature request related to a problem? Please describe.
I'm always frustrated when preparing a payload i have to always use the user role both for user messages and for applciation messages. Why don't we have a "developer" role for application generated (e.g. RAG) content. Like for example, you have the normal "conversation/history" model/user/model/user but then on every turn, you want to include a message that is generated by the client application containing things like the content of some files in the filesystem, a screenshot or some runtime metrics like 'Heap Memory Usage". Wouldn't it be semantically more clear for Gemini if there was a 3rd role like the openai "developer" role?
Describe the solution you'd like
Have another role called "developer"
Describe alternatives you've considered
putting like big banners in the application generated context like "THIS IS NOT A REAL MESSAGE FROM THE USER, THIS IS DYNAMICALLY GENERATED CONTENT, THE USER DOESN'T SEE THIS MESSAGE ON THE HISTORY, IT HAS BEEN CREATED BY THE APPLICATION"
Additional context
Add any other context or screenshots about the feature request here.