anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Feature: Mid-stream context injection at natural breaks (like Claude Code) #3337

New Issue
Open
opened 2026-02-16 17:39:42 -05:00 by yindo · 5 comments
yindo commented 2026-02-16 17:39:42 -05:00
Owner
Copy Link
Copy Source

Originally created by @sudoxreboot on GitHub (Dec 5, 2025).

Feature Request

Current Behavior

When typing while the AI is responding, messages are queued and only processed after the current response completes. This means if I remember something important mid-response, I have to wait for completion or cancel entirely.

Desired Behavior

Allow queued user input to be injected at natural breaks during response generation, similar to how Claude Code handles this:

  1. User types new input while AI is responding
  2. System detects a "natural break" (after tool result, end of text block, between reasoning steps)
  3. User's new input is appended to the conversation context
  4. AI continues but now sees the new info and can incorporate it

Why This Matters

  • Sometimes you forget context and remember mid-response
  • Canceling loses progress and costs tokens
  • Current queue waits until completion, missing the chance to influence the current response

Implementation Notes

The agent loop would need to:

  1. Check for pending queued input at safe breakpoints (after tool calls complete, after text blocks)
  2. If input exists, append it to the conversation before continuing
  3. Let the model naturally incorporate the new context in its next step

This is different from interrupt (which breaks tool_use/tool_result pairing) - it's a graceful context merge at safe points.

Reference

Claude Code does this - you can type mid-response and it finds a natural break to pop in your new message before continuing.

Originally created by @sudoxreboot on GitHub (Dec 5, 2025). ## Feature Request ### Current Behavior When typing while the AI is responding, messages are queued and only processed after the current response completes. This means if I remember something important mid-response, I have to wait for completion or cancel entirely. ### Desired Behavior Allow queued user input to be **injected at natural breaks** during response generation, similar to how Claude Code handles this: 1. User types new input while AI is responding 2. System detects a "natural break" (after tool result, end of text block, between reasoning steps) 3. User's new input is appended to the conversation context 4. AI continues but now sees the new info and can incorporate it ### Why This Matters - Sometimes you forget context and remember mid-response - Canceling loses progress and costs tokens - Current queue waits until completion, missing the chance to influence the current response ### Implementation Notes The agent loop would need to: 1. Check for pending queued input at safe breakpoints (after tool calls complete, after text blocks) 2. If input exists, append it to the conversation before continuing 3. Let the model naturally incorporate the new context in its next step This is different from interrupt (which breaks tool_use/tool_result pairing) - it's a graceful context merge at safe points. ### Reference Claude Code does this - you can type mid-response and it finds a natural break to pop in your new message before continuing.
yindo commented 2026-02-16 17:39:42 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Dec 5, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #4821: Add ability to unqueue messages (related queue management)
  • #4822: RFC: add an "interject" answer to the "ask" permissions responses (similar goal of injecting user input during AI processing)
  • #3378: Silent Message Insertion API (directly addresses injecting context without interrupting current response)
  • #4156: Plan/build for queued prompts are unintuitive (related to queue behavior)

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Dec 5, 2025): This issue might be a duplicate of existing issues. Please check: - #4821: Add ability to unqueue messages (related queue management) - #4822: RFC: add an "interject" answer to the "ask" permissions responses (similar goal of injecting user input during AI processing) - #3378: Silent Message Insertion API (directly addresses injecting context without interrupting current response) - #4156: Plan/build for queued prompts are unintuitive (related to queue behavior) Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:39:42 -05:00
Author
Owner
Copy Link
Copy Source

@will-marella commented on GitHub (Dec 5, 2025):

I think that would be pretty neat. I'm gonna take a look and see what might be feasible

@will-marella commented on GitHub (Dec 5, 2025): I think that would be pretty neat. I'm gonna take a look and see what might be feasible
yindo commented 2026-02-16 17:39:42 -05:00
Author
Owner
Copy Link
Copy Source

@will-marella commented on GitHub (Dec 5, 2025):

I think that would be pretty neat. I'm gonna take a look and see what might be feasible

It's very feasible. Working on implementing this.

@will-marella commented on GitHub (Dec 5, 2025): > I think that would be pretty neat. I'm gonna take a look and see what might be feasible It's very feasible. Working on implementing this.
yindo commented 2026-02-16 17:39:42 -05:00
Author
Owner
Copy Link
Copy Source

@will-marella commented on GitHub (Dec 5, 2025):

I think that would be pretty neat. I'm gonna take a look and see what might be feasible

It's very feasible. Working on implementing this.

I was experiencing this earlier but can't reproduce now. It seems to be working fine. Anyone else still seeing it?

@will-marella commented on GitHub (Dec 5, 2025): > > I think that would be pretty neat. I'm gonna take a look and see what might be feasible > > It's very feasible. Working on implementing this. I was experiencing this earlier but can't reproduce now. It seems to be working fine. Anyone else still seeing it?
yindo commented 2026-02-16 17:39:42 -05:00
Author
Owner
Copy Link
Copy Source

@henry701 commented on GitHub (Jan 12, 2026):

Anyone looking at this yet? Main blocker from moving from Cursor to OpenCode.

@henry701 commented on GitHub (Jan 12, 2026): Anyone looking at this yet? Main blocker from moving from Cursor to OpenCode.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#3337
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?