Tracking some of the reviewer feedback, question and assumptions made on https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/4540+ to be sure they doesn't get lost. 1. Using chevron icons for collapsible context items section [link](https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/4540#note_2071930273) 1. Should we prevent collapsing context items in the user message like the original implementation? How should we decide when to collapse? [link](https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/4540#note_2069391456) 1. Related, should the context even appear on the assistant message? It's just repeated info since it's already displayed on the user message [link](https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/4540#note_2071772222), [same feedback again](https://gitlab.com/groups/gitlab-org/-/work_items/14783#note_2070423588) 1. Related agaim `do we really need to show the context in the prompt after it has been sent out? What's the point? Isn't the information in the answer enough?` [link](https://gitlab.com/groups/gitlab-org/-/work_items/14783#note_2070423588) 1. Should we try to extract the GitLab markdown issue/MR popup and use that when hovering an issue/MR context item? [link](https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/4540#note_2070557164) 1. `From the perspective of a user, how is the added context, if used by AI in the answer, different from "Source"?` Should we treat context/sources as related concepts, we display them quite separately in this initial implementation [link](https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/4540#note_2071247702)