Repository navigation
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Suggested replies stay visible beneath the latest completed assistant response while the user types. Selecting one fills an empty composer or replaces the text already there. Attachments, references and skills stay in the draft, and focus returns to the editor so the user can revise the suggestion or undo the replacement. Only Send or Enter submits the final draft.
All six runtimes receive the same instructions for an optional list of 3–5 suggestions. The frontend recognizes the final Markdown definition
[opendirector-replies]: #and filters out individual suggestions longer than 80 characters. If the list is malformed or fewer than three eligible items remain, it displays the original list. The conversation keeps the original reply and tool offsets. Draft saving and turn submission use the existing paths.Linked issue
#429
Labels
type:feat,area:agent,area:harness,area:i18nandarea:docs.Test plan
WinError 5during lock-directory permission setup before the first prompt.Evidence that it works
In the current Chrome session test, the user selects a storyboard suggestion, adds an exclamation mark and presses Send. The saved user message contains the added punctuation. Before Send, selecting and editing the suggestion changed only the draft.


More examples from DeepSeek Harness and Codex
DeepSeek Harness


Codex


Provider verification
Live models were tested on Default, Codex, and DeepSeek Harness with two prompts each (creative direction and image description). Default and Codex showed four suggestions for both prompts; DeepSeek Harness showed four and five respectively. Those runs predate the switch to draft editing.
For first-turn and resumed-turn prompt delivery, CLI doubles checked the received input across all six runtimes: stdin for Default, OpenCode, Codex, and Claude Code; the ACP session/prompt context block for DeepSeek; and the --run-jsonl request input for JiuwenSwarm. Live-provider verification for OpenCode, Claude Code, and JiuwenSwarm was not run.
Bilingual UI