IDE completion notifications should identify and open the exact chat

Start by reviewing the VS Code/Cursor Codex extension's documented commands and current completion/input notification handling. Trace how the originating threadId could reach a public command or URI, then verify exact-chat focus, fallback behavior, shared identity, configuration, and multi-window or remote-session behavior across the listed platforms.

What feature would you like to see?

In the VS Code/Cursor Codex extension, completion and input notifications should carry the originating thread ID. Clicking the notification should open and focus the exact Codex chat that produced it, rather than only activating the editor or opening the generic Codex sidebar.

Each parallel chat should also have a consistent, accessible identity across the chat list, chat header, and notification. A useful identity could combine the chat title with workspace/repository and Git branch, plus an optional accent or icon (but never color alone).

Expected behavior:

1. Completion/input notification payloads retain the originating threadId.
2. The notification's default action invokes a documented public command or URI contract, such as chatgpt.openChat(threadId).
3. Codex focuses the correct editor window and exact local chat, with a sidebar fallback if the thread is unavailable.
4. The same chat identity appears in the notification, chat list, and header.
5. The behavior works across Linux, macOS, Windows, remote/WSL sessions, and multiple editor windows.
6. Users can configure built-in completion notifications so companion extensions do not have to produce duplicate alerts.

Why is this needed?

With multiple Codex chats running in parallel, they often finish out of order. A generic “done” notification makes the user visually hunt through chats to find the one that completed. Exact routing and stable identity would make parallel work much easier to follow.

Additional information

The IDE extension currently documents commands such as opening the sidebar and starting a new chat, but does not document an exact-thread navigation command or URI. Companion extensions can observe a thread ID from the Codex app-server, but should not have to depend on a private webview route. A stable public API would let notifications and other integrations route safely.

Observed with Codex IDE extension openai.chatgpt version 26.721.41059 in VS Code on Linux.