VS Code background-agent activity chips are unresponsive

Reproduce the issue in the Codex VS Code extension using Windows with a remote Linux workspace, then trace the click handling for the “Execution telemetry” background-agent activity chip. Done means clicking the chip opens the corresponding agent or telemetry details, or the chip is clearly non-interactive and provides appropriate feedback.

What version of the IDE extension are you using?

openai.chatgpt@26.721.41059

What subscription do you have?

ChatGPT Pro

Which IDE are you using?

VS Code 1.131.0, connecting from Windows to a remote Linux workspace

What platform is your computer?

Client: Windows x64

Remote workspace:

Linux 6.8.0-1061-aws x86_64 x86_64

What issue are you seeing?

The Codex chat shows background-agent activity chips while agents are running or after their status updates, but clicking those chips does nothing.

For example, the conversation displays an “Execution telemetry 3 — updated” chip with a spinning/background-agent icon. Clicking the chip produces no visible response:

• No agent details or execution telemetry view opens.
• The chat does not navigate to the background agent.
• No popover, panel, status information, or error message appears.
• There is no visual feedback indicating whether the click was handled.

The chip looks interactive and appears intended to expose the background agent or its telemetry, but it behaves like inert text.

What steps can reproduce the bug?

1. On Windows, open VS Code and connect to a remote Linux workspace.
2. Open the Codex IDE extension and start a task that uses background agents.
3. Wait for a background-agent activity chip to appear in the conversation.
4. Locate a chip such as “Execution telemetry 3 — updated”.
5. Click the chip while the background agent is running and/or after its status changes to “updated”.
6. Observe that nothing opens and no feedback is displayed.

What is the expected behavior?

Clicking a background-agent activity chip should open the corresponding agent, execution telemetry, or status details.

If the chip is not intended to be interactive, it should not use button-like styling or hover/click affordances. If its target is temporarily unavailable, the extension should show a clear message instead of silently ignoring the click.

Additional information

This makes it difficult to inspect or follow background-agent work from the main conversation. The issue is reproducible with the Execution telemetry chip shown while background agents are active.

A screenshot was captured showing repeated “Execution telemetry 3 — updated” chips in the conversation that do not respond when clicked.