Repository navigation
Response trimming, filtering and context control #181
Description
Activity
This blocks a use case of using the GH mcp with GH copilot agent mode, which I'd expect to integrate well.
Example of what happens now:
I give GHC Agent mode in vscode the GH mcp server, ask it for summarizing issues with a label, it queries github, receives 200k tokens as a response, everything else falls out of the context window and it forgets what is it doing.mark👀
- changed the title
[-]Response trimming options[/-][+]Response trimming, filtering & context management[/+]on Apr 23, 2025 - changed the title
[-]Response trimming, filtering & context management[/-][+]Response trimming, filtering and context control[/+]on Apr 23, 2025 This issue is stale because it has been open for 60 days with no activity. Leave a comment to avoid closing this issue in 10 days.
This issue was closed because it has been inactive for 60 days since being marked as stale.
Many of the responses from the API are very large and eat valuable context window. We should think through strategies on how to give the model options for smaller results. That might be
*_smalltools that return trimmed results or possibly the option for the model to pass in a nested set of keys to select.