Inform user of Duo Chat's capabilities before the user types a question
Context
Duo Chat is accessible from anywhere in GitLab but its functionality differs depending on where the user is in the UI. Example:
The call to action for the chat remains the same regardless of its functionality.
Problem to solve
It could be confusing to the user that Duo Chat's capabilities change depending on where the user is in GitLab. For example, the user may not expect that they can only ask a documentation question while viewing their to-do's.
This problem will increase in scope if we move forward with a proposal to have Duo Chat always accessible, regardless if AI features have been banned or not. In this proposal, Duo Chat is always available, but only to answer documentation questions. This could be confusing for a user who asks specific issue questions in one project, and in the next project they cannot ask those questions.
How might we better communicate the chat's capabilities to reduce user confusion?