Repository navigation
[FEATURE]: Allow forcing immediate reading of queued messages (steering) #24298
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
In the GitHub Copilot VS Code extension, when messages are queued while the agent is busy, users can interact with pending messages to change their delivery mode — specifically, they can "steer" the agent by forcing a message to be read immediately rather than waiting in the FIFO queue (docs).
The Copilot SDK supports two delivery modes:
"enqueue"(default) — message waits in FIFO queue for the next turn"immediate"(steering) — message is injected into the current LLM turn before the next model call
Requested feature:
In OpenCode, when messages are in the queue while the model is processing, allow the user to click on a queued message to force its immediate reading by the model (steering mode). This would convert the message from enqueue to immediate delivery, injecting it into the current turn instead of waiting for FIFO processing.
Use case:
While the agent is working, I realize it's heading in the wrong direction. I've already queued a corrective message. Instead of waiting for the queue to process in order, I want to click that message and have the model read it immediately — redirecting the current turn without losing progress.
Benefits:
- Gives users interactive control over message priority without canceling the current request
- Particularly valuable for agentic workflows where course-correcting mid-task is common
- Matches the steering pattern documented in the Copilot SDK (
mode: "immediate")
Activity
github-actions commentedon Apr 25, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
If you believe this was flagged incorrectly, please let a maintainer know.
omatheusmesmo commentedon Apr 25, 2026
Hello @thdxr, I've edited the issue description, and I believe it now meets the compliance requirements.
github-actions commentedon Jul 3, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
ElJaviLuki commentedon Jul 25, 2026
Wtf, how can this be chosen as "not planned"? Let's make a fork NOW
PurHur commentedon Aug 15, 2026
"Not planned" lol this must be a one sentence prompt to make that happen or why is this so hard? Is the code base so fucked up?
Py528 commentedon Sep 9, 2026
lmao not planned
omatheusmesmo commentedon Sep 9, 2026
hey @thdxr , could you kindly reopen this issue?