openai / openai/codex

Support a highlighter tool and a status summary for the chat

Open
#45,758 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app enhancement
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What variant of Codex are you using?

Desktop App

What feature would you like to see?

This relates to the desktop App and mainly the Chat section.

Chats run long and important bits of output are embedded in a lot of other text.
Let the user highlight the important bits, similar to how they would do so while reviewing a long document.
Let the user annotate the highlights with notes, similar to post-it notes attached to a long document.
Let the user edit or remove the notes and highlights as needed.

This can serve multiple purposes:

  1. user can easily scroll back over output of multiple turns (that span multiple months or even years) and find the important bits
  2. chat can be compressed to hide turns that did not produce anything highlighted or even sections of turn output without highlights
  3. a summary box can be built that briefly restates the highlighted bits. This will give the user an accessible summary of all important things generated during the chat. The summary should link to the relevant places of the chat log. It should also show if notes were attached and perhaps summarize the notes as well. Maybe allow quick access to the notes without actually jumping back into the chat log.

Extension - use the Notes as a way for user to provide in-context feedback on the output.
For example, the user might ask a question about that portion or provide an additional detail objecting to it.
This will be easier than copying that text to quote it. But the main value is that it can be done while reading the output and not jumping back and forth between the output and the chat box. The only caveat is that notes used this way should not result in a highlight and should not become part of the chat summary because they are likely to have a poor overlap with the truly important things the user wants to make accessible as a long term result.

Also filed as feedback under id no-active-thread-01a0a653-8b85-7603-965a-b72c0a68d64f, but with a bit less detail.

Additional information

No response

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

No files, tests, or entry points are named. Start by scoping the Desktop App's Chat section against the requested highlights, editable notes, collapsed content, and linked status summary; done would require an agreed design and implementation plan for these behaviors.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.