Make Slash Commands Respect the "Queue Messages" Setting

Ideas Feature Requests
1

Feature request for product/service

Cursor IDE

Describe the request

Feature Request: Make Slash Commands Respect the “Queue Messages” Setting

I’d like to request that slash commands (such as /summarize) respect the existing Queue messages setting.

Current behavior

When a slash command like /summarize is executed while another request is running, it immediately interrupts the active request instead of following the configured queue behavior.

This is inconsistent with the Queue messages setting and can result in wasted time and tokens if the interrupted request was close to completion.

Proposed behavior

If Queue messages is enabled, slash commands should behave exactly like normal prompts:

  • They should be placed in the request queue.
  • They should execute automatically once previous requests have completed.
  • They should not interrupt the currently running request.

If Queue messages is disabled, the current behavior (immediate execution) can remain unchanged.

Benefits

  • Consistent behavior across all request types.
  • No special-case logic for individual commands such as /summarize.
  • Prevents accidental interruption of long-running tasks.
  • Reduces wasted tokens and compute.
  • Automatically applies to future slash commands without requiring additional implementation.

In general, slash commands should inherit the behavior defined by the Queue messages setting rather than implementing their own queueing logic.

5

Hey there! Thanks for the clear write-up. You’re right that with Queue Messages on, slash commands like /summarize should queue like a normal prompt instead of cutting off the active request. We’ve let the team know and this is something we’re tracking. No timeline to share yet, but I’ll post here when there’s an update.