After restarting the Codex extension in VS Code, it no longer displays detailed tool invocation information such as command-line calls and file changes during the reasoning process. Only the complete reasoning process is shown.

What version of the VS Code extension are you using?

0.5.61

What subscription do you have?

API key

Which IDE are you using?

VS Code

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?

After restarting the window or the Codex extension in VS Code, the detailed command-line invocations and file modifications from the thought process are not displayed; only a complete thought process remains. The consolidated output after restarting combines previous sessions, but omits all command-line executions and corresponding outputs from prior sessions, along with file modifications (I suspect this can be categorized as missing all tool invocations). Refer to the screenshot for specifics. Is this normal behavior, or can it be adjusted via configuration files? Is there a way to preserve the original output display after restarting?

Below is a partial excerpt from my current config.toml:

model = "gpt-5.2"
model_reasoning_effort = "xhigh"
approval_policy = "never"
sandbox_mode = "danger-full-access"
network_access = "enabled"
disable_response_storage = true
model_reasoning_summary = "detailed"
model_supports_reasoning_summaries = true
hide_agent_reasoning = false
show_raw_agent_reasoning = true

[features]
web_search_request = true
unified_exec = true
shell_snapshot = true

Screenshots before and after restarting are as follows:

<img width="991" height="907" alt="Image" src="https://github.com/user-attachments/assets/8fd54564-34e9-4d93-bb36-bd12f64e8ab7" />
<img width="989" height="282" alt="Image" src="https://github.com/user-attachments/assets/c3d75c58-2d7a-475e-88bf-116e3ad2c7db" />

What steps can reproduce the bug?

I'm not sure how to explain this “bug.” Since I really need to see his complete thought process and tool invocation sequence, I consider this issue quite serious. At the same time, I'm uncertain whether my own configuration might be causing this problem.

And here‘s another simple example：

Before restarting:

<img width="930" height="540" alt="Image" src="https://github.com/user-attachments/assets/487b06d0-5a67-48dd-9bf1-45b7d77726ff" />

After restarting:

<img width="931" height="468" alt="Image" src="https://github.com/user-attachments/assets/621d1ab5-921e-47ef-959a-c4af0d82c5ab" />

What is the expected behavior?

_No response_

Additional information

_No response_