github / github/copilot-cli

Queued prompts occasionally remain stuck after the session becomes idle

Open
#4,705 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area:input-keyboard area:sessions
Dominant language
Shell
Stars
11.2k
Forks
1.9k
Avg merge
14h 16m
Merged PRs (30d)
6

Description

Describe the bug

Queued prompts are not dequeued consistently. Occasionally, after pressing Ctrl+Q to enqueue a prompt while Copilot CLI is busy, the prompt remains listed under Queued (1) Ctrl+Q to manage even after the session becomes idle.

The queue manager allows the queued prompt to be edited or deleted, but it does not provide a "Send now" action, and the prompt never dispatches automatically. Deleting the queued prompt and submitting the same text manually works.

Affected version

1.0.83-3

Steps to reproduce the behavior
  1. Start an interactive Copilot CLI session and submit a prompt that keeps the session busy.
  2. While it is busy, type another prompt and press Ctrl+Q to enqueue it.
  3. Wait for the active work to finish and for the session to become idle.
  4. Observe that, intermittently, the status continues to show Queued (1) Ctrl+Q to manage and the prompt is never sent.
  5. Press Ctrl+Q to manage the queue. The prompt can be edited or deleted, but there is no option to send it immediately.
  6. Delete the queued prompt and submit the same text manually; it sends successfully.

This is intermittent and does not happen for every queued prompt.

Expected behavior

A queued prompt should automatically dispatch when the session becomes idle. The queue manager should also provide a "Send now" action as a fallback when automatic dequeueing does not occur.

Additional context
  • Operating system: Windows
  • Reproducibility: Intermittent
  • UI remains responsive; queued prompts can still be edited or deleted.
  • Manually resubmitting the same prompt succeeds.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in an interactive Copilot CLI session using Ctrl+Q while active work is running, then inspect the queue manager and the transition to an idle session. Verify the queued prompt is dispatched automatically after the session becomes idle, and that the queue manager provides a "Send now" fallback when needed.

Written by the indexing model from the issue text.

Assessment

Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.