Before submitting
Area
apps/web
Problem or use case
When I finish drafting a prompt in an existing thread, I sometimes realize it belongs in a separate thread.
T3 Code currently makes me copy the draft, create a new thread, paste it, and send it. This interrupts the keyboard flow and makes it easy to send unrelated work into the current thread by mistake.
Proposed solution
On desktop, Alt+Enter should send the current composer draft to a new thread in the same project.
Plain Enter should continue sending to the current thread, and Shift+Enter should continue inserting a newline.
T3 should start the turn in the new thread, navigate to it, and avoid briefly showing the source thread as working. The new thread should use the same project and checkout defaults as a normally created thread.
The send button tooltip should mention the shortcut so it is discoverable.
Why this matters
Threads are easier to follow when unrelated work stays separate. This replaces a copy, create, paste, and send workflow with one shortcut while preserving the prompt the user has already written.
Smallest useful scope
Support Alt+Enter in the desktop web composer and desktop app.
The first version does not need a setting, mobile gesture, command-palette action, or configurable keybinding. Existing Enter and Shift+Enter behavior should remain unchanged.
Alternatives considered
The current workaround is to copy the draft, create a thread, paste it, and send it.
A separate button or menu action would work, but it adds UI for an action meant to keep the user in the keyboard flow.
The broader keybinding system could expose this as a configurable command later. A fixed composer shortcut keeps the first version smaller.
Risks or tradeoffs
The shortcut must not interfere with Shift+Enter or modified combinations such as Ctrl+Alt+Enter and Meta+Alt+Enter.
If creating or starting the new thread fails, the current thread should remain usable and show a clear error. The source thread should not briefly enter a working state for a turn that belongs to the new thread.
The shortcut is desktop-only because mobile keyboards do not provide the same modifier behavior.
Examples or references
Prior art: Cortex Code provides an Alt action for sending a draft to a new session.
Related but distinct:
Demo video will be added below.
Contribution
Before submitting
Area
apps/web
Problem or use case
When I finish drafting a prompt in an existing thread, I sometimes realize it belongs in a separate thread.
T3 Code currently makes me copy the draft, create a new thread, paste it, and send it. This interrupts the keyboard flow and makes it easy to send unrelated work into the current thread by mistake.
Proposed solution
On desktop, Alt+Enter should send the current composer draft to a new thread in the same project.
Plain Enter should continue sending to the current thread, and Shift+Enter should continue inserting a newline.
T3 should start the turn in the new thread, navigate to it, and avoid briefly showing the source thread as working. The new thread should use the same project and checkout defaults as a normally created thread.
The send button tooltip should mention the shortcut so it is discoverable.
Why this matters
Threads are easier to follow when unrelated work stays separate. This replaces a copy, create, paste, and send workflow with one shortcut while preserving the prompt the user has already written.
Smallest useful scope
Support Alt+Enter in the desktop web composer and desktop app.
The first version does not need a setting, mobile gesture, command-palette action, or configurable keybinding. Existing Enter and Shift+Enter behavior should remain unchanged.
Alternatives considered
The current workaround is to copy the draft, create a thread, paste it, and send it.
A separate button or menu action would work, but it adds UI for an action meant to keep the user in the keyboard flow.
The broader keybinding system could expose this as a configurable command later. A fixed composer shortcut keeps the first version smaller.
Risks or tradeoffs
The shortcut must not interfere with Shift+Enter or modified combinations such as Ctrl+Alt+Enter and Meta+Alt+Enter.
If creating or starting the new thread fails, the current thread should remain usable and show a clear error. The source thread should not briefly enter a working state for a turn that belongs to the new thread.
The shortcut is desktop-only because mobile keyboards do not provide the same modifier behavior.
Examples or references
Prior art: Cortex Code provides an Alt action for sending a draft to a new session.
Related but distinct:
Demo video will be added below.
Contribution