Forced Parallel Execution: bypass message queue with modifier shortcut

[pedramamini]

Summary

Add a Forced Parallel Execution mode that allows advanced users to bypass the message queue and send messages to an agent even while it's busy processing. Activated via a configurable shortcut (default: ⌘⇧↩) when the feature toggle is enabled in Settings.

Motivation

Power users managing multiple concurrent tasks sometimes know it's safe to fire off a second message while an agent is working — for example, when the queries touch different files or different parts of the codebase. Currently, all messages are queued when the session is busy. This feature gives advanced users explicit control over parallel execution at their own risk.

Behavior

• Toggle in Settings > General > Input Send Behavior enables the capability (off by default)
• One-time warning modal shown when first enabling, explaining clobber risks
• Modifier shortcut (default ⌘⇧↩, user-configurable) activates forced send per-message
• Regular Enter / ⌘+Enter still queues normally even with the feature enabled
• Bypasses both "session busy" and "AutoRun active" queue gates
• AI mode only (not terminal mode)
• Multiple rapid forced sends all execute (no throttling)

UI

Third card in the "Input Send Behavior" section of Settings > General:

• Shortcut badge + ToggleSwitch (enable/disable)
• Inline warning text with ⚠ icon when enabled
• First-time enable triggers a confirmation modal

Implementation

A detailed playbook is attached covering six phases:

1. Settings, shortcuts, and store wiring
2. One-time warning modal
3. Settings UI (GeneralTab third card)
4. Keyboard handling (processInput options object, useInputKeyDown shortcut detection, shouldQueue bypass)
5. Tests
6. Manual verification checklist

Key files: settingsStore.ts, GeneralTab.tsx, useInputProcessing.ts, useInputKeyDown.ts, shortcuts.ts, modalPriorities.ts

Playbook

📎 See attached forced-parallel-execution.md for the full implementation playbook.

forced-parallel-execution.md

[jSydorowicz21]

Is the goal of this to spawn effectively a separate instance of the same agent with the same history or feed the currently running instance more context / messages?

[scriptease]

Does this work like /btw in Claude and reuse the context and fork the session or does it update the current session?