Repository navigation
[Idea] One-click ▶ Continue: turn Send into Continue when a turn stopped and the composer is empty (like Codex) #9269
furkancak1r
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Proposal
When a turn has stopped (interrupted by the user, or ended on its own e.g. max-tokens) and the composer is empty, turn the primary Send button into a ▶ Continue button. One click sends
continue(ideally a localized / configurable text) so the agent resumes where it left off. This is how the Codex app behaves, and it removes the most common "type continue + Enter" loop.Visibility rules
Why built-in
It can be done as a plugin today, but only awkwardly:
conversation.input.rightcan add a separate button, while the primary Send button itself is not a slot. To make Send become Continue, my local plugin has to find the*_primarybutton in the DOM, hide it, and portal a replacement into its row. That relies on a hashed CSS class name and will break silently on UI updates.Minimal ask (either is fine)
conversation.input.primary), so plugins can do this cleanly.Tested locally on 0.2.0-rc.2 (desktop) with
useSession/useInput/inputActions.setDraft+submitfrom the slot props; the logic is ~40 lines.Related: #3303 and #1166 (turns ending on max-tokens wait for a manual "continue").
All reactions