Add manual bookmarks for important sections within a thread
What variant of Codex are you using?
App (macOS)
What feature would you like to see?
Codex threads should support user-created bookmarks: lightweight saved points inside a conversation that act like named return locations.
The goal is not a full table of contents or automatic thread outline. Instead, this would let users explicitly mark moments they know they will need again, such as:
- the original ask
- an approved plan
- a key command output
- a design decision
- a handoff summary
- the point where a bug was identified
One possible interaction:
- Hover a message or section and choose
Bookmarkicon beside the currentCopyicon. - Optionally give the bookmark a short name.
- Show saved bookmarks in the existing right-side panel area, alongside
OutputsandSources. - Selecting a bookmark scrolls the thread back to that saved location.
- Bookmarks remain attached to the thread across app restarts.
This would make bookmarks more like persistent conversation anchors than search results or generated navigation. It would be especially useful when working through long tasks where a few specific moments matter more than the overall thread structure.
<img width="1643" height="957" alt="Image" src="https://github.com/user-attachments/assets/08d25db3-eebe-41e4-9f3b-1b17f2d81a57" />
<img width="2168" height="725" alt="Image" src="https://github.com/user-attachments/assets/6fad6175-e659-4638-aa6b-70b191e230e2" />
Related issue: #22627 - this request is unique in that it is user-created bookmarks but could exist alongside a generated ToC.
Additional information
_No response_
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Adding a narrower +1 here: the specific version I want is a copyable permalink/reference to a specific response, not just a bookmark list.
Today the documented
codex://links seem to support opening a thread, e.g.codex://threads/<session UUID>, but I don't see a documented way to link to a particular turn or response inside that thread. It would be useful if the app exposed something like “Copy response link/reference” on a message, producing a stable local permalink that can be pasted into a later prompt.The important behavior is: click copy on a response, paste the reference later, and Codex can resolve it back to that exact response. If the response is already in context, the agent can use it directly; if not, the app/agent can load it from the local session history using the thread/turn/item identity. This avoids repasting large response text into the same thread and preserves the original location.
This feels adjacent to existing app URL/deep-link support: thread-level links already navigate to a conversation, but this would extend that idea to a specific response within the thread. It also pairs naturally with bookmarks, because a bookmarked message should probably have a copyable permalink.
Related: #20651 covers jump-to-response navigation, and #21779 covers stable
codex://links to conversations. This request is specifically for a copyable per-response permalink/reference that can be pasted back into a prompt and resolved to that response.