Queued messages should be executed together, not separately

Resolved 💬 1 comment Opened Nov 20, 2025 by guidedways Closed Jan 19, 2026

What feature would you like to see?

When Codex is performing work and you add more instructions, those should be grouped and executed together, not separately. The only time where separate execution would make sense is if I were allowed to queue a /review followed by additional instructions, but since that isn't possible, I cannot think of a reason why queued messages should be executed in sequence. ClaudeCode (a) tries to execute the command immediately while it's working, but if you do manage to queue them up quickly, these get executed together. GeminiCLI does the same. I feel that is the correct approach.

For instance a lot of times I queue up a message only to remember to add more, then then don't realize these are going to get executed one after another, which means it'll undo some work in the second step because my first message in the queue isn't complete.

• Verifying boolean behavior (4m 33s • esc to interrupt)
  ↳ `defaultStartMinutes` and `defaultDurationMinutes` belong to `Preferences.TaskPreferenceKeys` not `Preferences.PreferenceKeys`
  ↳ You can see all the various enum types here Preferences.swift some keys exclusively belong to a different type
    ⌥ + ↑ edit

Additional information

Unfortunately I have to dequeue additional messages, copy them, remove them and dequeue the first one, paste them together every time.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗