[Windows app] Quick Chat omits native edit and regenerate controls
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
App version
Microsoft Store package OpenAI.Codex 26.901.6511.0; desktop application 26.901.51231.
Subscription
Pro 20×
Platform
Windows 11 x64.
Missing behavior
In Quick Chat, user messages expose Copy but no Edit, and completed responses lack the regeneration controls available in the main Chat window. This report asks for parity with the existing Chat actions; it does not assume the omission was unintentional.
Reproduction and implementation finding
Open an existing Chat conversation in Quick Chat and inspect a user message and a completed assistant response. The compact transcript explicitly sets onEditUserMessage to undefined and does not forward onRegenerateResponse into the native turn renderer.
A local implementation opts only Quick Chat into the existing controls. Editing lazily calls the main Chat page's native editor, and regeneration calls the native response handler. It preserves attachment handling, parent message/branch selection, model/effort choices, search options, and retry feedback rather than creating a separate sending protocol.
Actions remain unavailable for Work, busy/submitting, missing server conversations, archived/read-only, and feature-blocked states. A pending request blocks duplicate actions; switching conversations invalidates old callbacks. Other preview callers retain their previous behavior.
Validation and limit
Eight portable action-state cases and eight full-transcript/native-editor cases cover permissions and busy guards, reentry, errors, navigation, branch membership, targeted replies, empty/multimodal messages, attachments, models, and the exact native delegation path.
The user confirmed the controls now appear in the actual Quick Chat window. This control-level acceptance is separate from a real regeneration request; the tests use synthetic conversations and do not consume account quota.
Entry points: assets/local-quick-chat-actions-v1.mjs, tests/quick-actions.mjs, and tests/quick-native.mjs.
Reproducible implementation
Complete English source, English release, and upstream evidence guide. The original project is wjtianze/codex-desktop-repair; its main branch remains in Chinese.
The package contains checked patch fragments and synthetic regression cases, not complete proprietary client bundles or account data. Both language editions passed 242 tests: 76 portable cases and 166 cases executing functions extracted from the supported official app. This is a local repair and evidence submission, not an official source merge.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with assets/local-quick-chat-actions-v1.mjs and compare the Quick Chat transcript behavior with the existing Chat actions. Run tests/quick-actions.mjs and tests/quick-native.mjs first; their listed cases define the required permission, busy-state, navigation, branch, reply, attachment, model, and delegation coverage. Done means the native controls appear in Quick Chat without changing other preview callers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- desktop, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100