-
Notifications
You must be signed in to change notification settings - Fork 3k
Open
Description
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:
- User types new input while AI is responding
- System detects a "natural break" (after tool result, end of text block, between reasoning steps)
- User's new input is appended to the conversation context
- 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:
- Check for pending queued input at safe breakpoints (after tool calls complete, after text blocks)
- If input exists, append it to the conversation before continuing
- 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.
dibenkobit, EoinOGara, will-marella and tvarbanov
Metadata
Metadata
Assignees
Labels
No labels