The GitHub context (have not tested slack) currently only supplies this information:
Context: {github title}
Source: {repo#issue number}
Area: {repo?}
State:
URL: https://github.com/...
While this is great to establish a general context, it is not enough to give a more specific guidance to the agent.
I've noticed some edge cases where the agent will be stuck in a quick loop trying to figure out the context via GitHub and then asking questions to me for additional information and guidance, even tho the context should suffice to fix the issue properly.
I've noticed this happens a lot with DeepSeek R4 (via Nano-GPT and OpenCode) and GPT-5.5 (Low).
The context should provide the title separately, the description and optionally the comments.
Ideally I would implement this by having the "Add to context" button add everything, and right clicking (context menu) to skip the comments. Of course with some toggle in settings that reverses this behavior (so Add to context will be "Add to context (Skip Comments)" and rclick "Add to context")
The GitHub context (have not tested slack) currently only supplies this information:
While this is great to establish a general context, it is not enough to give a more specific guidance to the agent.
I've noticed some edge cases where the agent will be stuck in a quick loop trying to figure out the context via GitHub and then asking questions to me for additional information and guidance, even tho the context should suffice to fix the issue properly.
I've noticed this happens a lot with DeepSeek R4 (via Nano-GPT and OpenCode) and GPT-5.5 (Low).
The context should provide the title separately, the description and optionally the comments.
Ideally I would implement this by having the "Add to context" button add everything, and right clicking (context menu) to skip the comments. Of course with some toggle in settings that reverses this behavior (so Add to context will be "Add to context (Skip Comments)" and rclick "Add to context")