VS Code extension does not render executed tool commands in chat UI

What version of the IDE extension are you using?

0.4.76

What subscription do you have?

API

Which IDE are you using?

VS Code

What platform is your computer?

Microsoft Windows 11 Pro 10.0.26200 64-bit

What issue are you seeing?

In the VS Code extension, tool commands executed during a chat session (for example get-content or git-related commands) sometimes do not appear in the chat UI.

The commands are present in the extension logs and clearly executed successfully, but no corresponding tool log lines are rendered in the Codex chat panel.

This creates a mismatch between the backend behavior (as seen in logs) and the UI, making it difficult to understand how the agent arrived at a response.

Here are the screenshots showing the chat UI where no tool commands are rendered, and a sanitized log excerpt from the same chat session where the tool commands are visible. The green marked log lines are the user's requests and the red ones are agent's answers or actions.

<img width="539" height="414" alt="Image" src="https://github.com/user-attachments/assets/e72b5fa0-53ff-41e7-b94f-c478b8a1c798" />

<img width="517" height="263" alt="Image" src="https://github.com/user-attachments/assets/14e05c6d-afaa-4006-ba09-025a3845036a" />

<img width="1910" height="835" alt="Image" src="https://github.com/user-attachments/assets/9da66885-2e43-4ac6-9389-fbb0e753f7d3" />

Notes:
This behavior was observed while working with skill files. A particular skill in the environment contains a workflow that involves working with Git branches.
When the skill is triggered directly, tool commands usually aren't rendered in UI.
But when we use a prompt that is supposed to make the agent to read/trigger the skill, they are usually rendered.

The issue is that sometimes they are rendered partially, e.g. the get-content command that shows that the skill.md has been read is not rendered, while all the other commands including git-related ones are. And sometimes they are not rendered at all (as shown in screenshots).

What steps can reproduce the bug?

Preconditions:

1. Have a skill.md file containing some workflow with branches in the .agents(.codex) folder.

Steps:

1. Start a new VS Code Codex extension chat session.
2. Write a prompt (without directly triggering the skill) that causes Codex to invoke/read/trigger the skill and follow it's workflow.
3. Observe the UI of the chat, compare the UI commands with the log commands.

What is the expected behavior?

All executed tool commands should be rendered in the Codex chat UI as part of the chat history, or at least explicitely state that it has read a skill content.

Additional information

The issue is rather common; it happens around 1/8 times or more often.