openai / openai/codex

Chrome extension: add an Insert button for focused page editors

Open
#38,764 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement extension
Dominant language
Rust
Stars
125k
Forks
19.5k
PR merge metrics
PR metrics pending

Description

What variant of Codex are you using?

ChatGPT/Codex Chrome extension version 1.2.27259.19709 on macOS.

What feature would you like to see?

Add an Insert button to assistant responses in the Chrome extension side panel. Pressing it should place the selected response into the currently focused editor on the current webpage, without submitting or sending anything.

The primary use case is drafting customer replies in Jira Service Desk. After Codex prepares a response, the user should be able to insert it into Jira's reply editor, review or revise it, and send it manually.

Suggested behavior:

  • Insert only; never submit the form or send the message.
  • Support standard text areas, contenteditable fields, and common rich-text editors such as ProseMirror and TinyMCE.
  • Preserve line breaks and basic formatting where possible.
  • Disable the action or show a clear message when no compatible editor is focused.
  • Show a confirmation such as "Inserted — review before sending."
Additional information

Example workflow:

  1. Focus the reply editor on a webpage.
  2. Ask Codex to draft a response using the page context.
  3. Click Insert on the desired assistant response.
  4. Review and send the response manually.

This would make browser-assisted drafting much faster while preserving the user's final review and control.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no repository files, tests, or entry points; begin by locating the Chrome extension side-panel response UI and the path used to interact with the focused webpage. Check how text areas, contenteditable fields, and rich-text editors are handled. Done means inserting without submission, preserving line breaks where possible, handling no focused editor clearly, and confirming the insertion.

Written by the indexing model from the issue text.

Assessment

Domain
frontend, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.