VS Code extension 0.4.79: repeated thread-stream-state-changed warnings, missing tool-step streaming #13583

What version of the IDE extension are you using?

openai.chatgpt-0.4.79-win32-x64

What subscription do you have?

plus

Which IDE are you using?

VS Code: 1.90.x (exact build available if needed)

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

During agent runs, chat often shows only thinking... instead of live tool-step updates.
Log is spammed with:
[warning] [IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed
In some sessions, this appears every ~50–200ms while Codex is working.
Related error seen earlier:

Error fetching ... "local-environments is not supported in the extension" ... url=vscode://codex/local-environments

What steps can reproduce the bug?

Start VS Code with extension 0.4.79.
Open Codex sidebar and run a coding task with tool usage.
Observe missing incremental tool-step rendering in UI.
Check openai.chatgpt.Codex.log -> repeated thread-stream-state-changed warning.

What is the expected behavior?

Extension should handle stream-state broadcasts and render live progress/tool steps reliably.

Additional information

Developer: Reload Window ->no change.
Full VS Code restart.
Renamed ~/.codex (C:\Users\Ar.codex) to force clean state -> no change.
Restored old .codex -> behavior unchanged.
This suggests issue is not caused by user config/state.
Expected:
Actual:

Broadcast warnings repeat, handler appears missing, UI streaming degrades.
Logs (sample):

2026-03-05 15:24:13.945 [error] Error fetching errorMessage="local-environments is not supported in the extension" ... url=vscode://codex/local-environments
2026-03-05 15:24:41.185 [warning] [IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed
2026-03-05 15:24:41.218 [warning] [IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed
2026-03-05 15:24:41.254 [warning] ...
Impact:

Significant UX degradation for agent mode in VS Code (can’t reliably observe execution progress in chat).