Codex App: add a global Pins view for messages, text selections, and generated files

What variant of Codex are you using?

Codex App (macOS)

What feature would you like to see?

Codex currently lets me pin an entire conversation, but the thing I need later is often one message, part of a message, or a generated file inside that conversation.

A recent example: I asked Codex to create a technical document in Markdown. The file still exists, but to find it from Codex I have to remember which thread produced it, open that thread, and locate the original message. The same problem comes up with design decisions, useful explanations, and command output that I know I will need again.

I would like to pin individual items from a message's hover or context menu, then access them from a global Pins view.

Proposed first version

From a conversation, the user can:

• Pin a whole user or assistant message.
• Pin selected text within a message.
• Pin a linked or generated file.

The Pins view would:

• Show items from the current project by default, with an option to view all projects.
• Display pinned text directly. Long messages can be collapsed.
• Show the source project, thread, and date.
• Provide an action to jump back to the exact source message.
• Preview or open the current version of a pinned file.
• Show the file as unavailable if it has been moved or deleted.
• Allow the user to remove a Pin.

A user should be able to Pin an item with one explicit action and return to it later within two or three actions, without having to find and search the original thread.

Why thread pinning and search do not solve this

Pinning a thread keeps the whole conversation accessible, but the user still has to find the relevant message inside it.

Search helps when the user remembers the right words. A Pin records the user's intent at the moment the content is created: "I know I will need this again."

Scope

The first version can stay manual and lightweight:

• No automatic or AI-selected Pins.
• No tags, folders, notes, or knowledge management features.
• No natural-language Pin commands.
• No file copies or backups. A file Pin points to the original file.
• No cross-device or cross-surface sync requirement for the first version.

Pins should persist across app restarts.

Additional information

Related issues:

• #23350 proposes manual bookmarks inside a single thread.
• #26425 proposes a broader timeline and conversation navigator.
• #30790 proposes message-level navigation to a specific turn or item.
• #16672 proposes global search across conversation content.

This request is broader than thread-local bookmarks but narrower than a full conversation timeline. It asks for a manually curated, cross-thread collection of saved messages, selections, and file references.

If the maintainers prefer to extend #23350 instead of tracking this separately, the main behavior I would like to preserve is the project-scoped global Pins view.