Conversation
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
1 participant
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.
ChatGPT messages in Lizard Studio could not be edited. Add an Edit message button with Save & send and Cancel for new messages and loaded history. Saving stops the current turn, rolls the Codex history back to the selected turn, and sends the changed prompt with its original attachments and page/file context.
The panel keeps later messages until the host confirms the rollback. Failed edits keep the draft. Stable turn IDs and retained history boundaries keep older pages editable, while queued prompts wait until the replacement answer finishes. File changes remain in place; the editor states this before sending.
Validation: 159 unit tests pass (
npm test); 20 checks pass in the real panel with a mocked host (test/e2e/panel.html?regressions=edit), covering loaded history, live edits, cancellation, IME input, failed rollback, duplicate submission, queues and disconnects. Checked the editor in the browser and matched the RPC fields against the installed Codex protocol. No live account turn or production session was changed.Uses
thread/rollback, which the installed Codex protocol supports but marks deprecated. An unsupported method leaves the draft and visible history intact. For imported turns with several user corrections, editing must start from the first user message in that turn.Merging changes the host package and triggers its npm release workflow.