Skip to content

Conversation

@shubh73
Copy link
Contributor

@shubh73 shubh73 commented Jan 18, 2026

Why

When a message is queued while the session is busy, there's no way to force it to process immediately. The only workaround is to:

  1. Press esc twice to interrupt
  2. Undo the queued message
  3. Re-enter and submit it

This is quite cumbersome.

Fixes #5770
Related: #5333, #8685

How

Added a force function that:

  1. Deletes session state before aborting (so the old loop's defer() cleanup finds nothing)
  2. Aborts the current operation
  3. Starts a fresh loop that picks up the queued user message from the database

The UI shows an "enter force" hint when a queued message exists, and pressing Enter triggers the force.

Test Plan

Screen.Recording.2026-01-18.at.6.07.29.PM.mov

Note

This PR was written entirely using AI.

Allow users to interrupt current generation and immediately process
a queued message by pressing Enter with an empty prompt.

- Add SessionPrompt.force() to abort and restart loop with queued message
- Add POST /session/:sessionID/force API endpoint
- Show 'enter force' hint when a queued message exists

Closes anomalyco#5770
@github-actions
Copy link
Contributor

The following comment was made by an LLM, it may be inaccurate:

No duplicate PRs found

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

force push message keybind

1 participant