Extend the chat response with a property that tracks the used context and provide an API for agents, chat service and tool functions to track which context variables they've actually resolved while creating the response. Then show this used context as part of the response.

I think it's very important for the release that we have a clear and understandable UX for the context as otherwise we will get a lot of issues reported that the feature is not working.

I absolutely agree. Doing this upfront, however, may require a lot of flags that each agent needs to provide. I think one option that is easier to do generically is to add an indicator in the response which context was processed.

We could track the variable resolution for a request in the chat service and the tool functions could notify the chat model that they've consumed a specific context. We could add an additional processedContext property in the chat response model that is written to by the chat service on variable resolution and by the tool functions and show the tracked context accesses in the chat response.

Originally posted by @planger in #14787 (comment)