Codex App “Copy as Markdown” omits response annotations (selected text and user comments)

Open
#33,763 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
macos, markdown, rust
Domain
desktop

Research direction

Start by reproducing the annotation workflow in the Codex App and tracing the Copy → Copy as Markdown entry point. Check how user messages and response annotations are represented during export. Done means copied Markdown preserves each selected response excerpt, optional comment, association with its user message, and original order.

Written by the indexing model from the issue text.

Description

app bug
What version of the Codex App are you using (From “About Codex” dialog)?

Codex App 26.707.71524 (5263)

What subscription do you have?

ChatGPT Pro ($200/month)

What platform is your computer?

macOS 26.5.2 (25F84), Apple Silicon (arm64)

What issue are you seeing?

Codex App lets me select text from an earlier assistant response, choose Add to chat, and optionally attach a comment to the selected text. The resulting user message displays an annotation indicator in the conversation.

However, when I use Copy → Copy as Markdown, the copied transcript omits the response annotation entirely.

Both of these are missing:

  1. The text selected from the earlier assistant response.
  2. The comment I wrote about that selected text.

For example, the annotation visible in the Codex App contained:

  • Selected response text: browser annotations
  • User comment: not browser annotations

Neither appears as an annotation in the copied Markdown for the corresponding user message.

The ordinary text I typed is copied, but the annotation that provides context for that message is not.

What steps can reproduce the bug?
  1. Open a task containing an assistant response.
  2. Select some text from the assistant response.
  3. Choose Add to chat.
  4. Add a comment to the selected text.
  5. Send the resulting user message.
  6. Confirm that the message displays an annotation indicator in the Codex App.
  7. Open the task menu and select Copy → Copy as Markdown.
  8. Paste the copied Markdown into a text editor.
  9. Find the user message that contained the response annotation.
What is the expected behavior?

The copied Markdown should preserve every response annotation and keep it associated with the user message in which it was submitted.

It should include:

  • The selected assistant-response text.
  • The user’s comment, when one was provided.
  • Multiple annotations in their original order when a message contains more than one.

The exact formatting can vary. For example:

#### Response annotation

> browser annotations

User comment: not browser annotations
What is the actual behavior?

The copied Markdown contains the ordinary typed portion of the user message, but no representation of its response annotations.

The selected text or comment may appear later if the assistant happens to repeat them in a subsequent response, but that does not preserve the original annotation or its association with the user message.

Why this matters

A response annotation can contain the main context for a follow-up message. Without it, the copied conversation may appear incomplete, unrelated, or misleading.

This affects using copied tasks for:

  • Bug reports
  • Documentation
  • Handoffs
  • Archiving
  • Continuing a conversation elsewhere
Additional information

Feedback ID: 019f6e06-8d18-70d0-b61f-cbabaa6bc189

Related but not duplicate:

  • #22894 concerns image handling in Copy as Markdown.
  • #25641 concerns the Add to chat selection toolbar failing to appear.

I can provide the copied Markdown output privately if needed.

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

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.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.