Windows desktop app does not expose local exec tools to any chat

Summary

The Codex Windows desktop app no longer exposes local command execution tools to chats. The integrated PowerShell terminal works and can access the project files, but all new and existing chats receive only js and js_reset; they do not receive the local exec tool.

This previously worked in the same desktop app and project. I did not manually change the configuration before the problem appeared.

Environment

• OS: Windows
• Codex desktop app package version: 26.903.9818.0
• Project directory: D:\w-桌面\大论文
• Feedback session ID: 01a09127-9d53-71c3-a940-ff7eeb410003

Expected behavior

A local chat opened for this project should receive the local command execution tool and should be able to read and modify files in the selected project directory.

Actual behavior

All new and existing chats report that no local file or command execution tool is available. They receive only browser/computer-use tools such as js and js_reset.

The integrated terminal itself works correctly:

• PowerShell opens inside the Codex desktop app.
• The current directory can be set to D:\w-桌面\大论文.
• Test-Path returns True for the target local Word document.
• The file is therefore present and readable from the integrated terminal.

Diagnostics already completed

1. Full access is enabled.
2. The sandbox is configured for workspace write access.
3. codex features list reports:
   • shell_tool: stable, true
   • unified_exec: stable, true
   • code_mode_host: stable, true
4. A session from before the failure contains 98 actual custom_tool_call calls to exec.
5. Sessions created after the failure contain only function_call calls to js and js_reset, or no actual tool calls.
6. The desktop app was fully restarted.
7. Windows application repair was performed, but the issue still occurs.
8. The project path, PowerShell, local file permissions, and the Word document itself have been verified.

Relevant session evidence

Working session:

rollout-2026-09-08T10-10-11-01a07ec7-b039-7e21-9a78-1936a098c6a6.jsonl

Actual tool calls included:

exec        98
js           5
js_reset     5

Affected newer session:

rollout-2026-09-11T22-06-28-01a090ca-8ad6-7b73-bca6-adb0a8489611.jsonl

Actual tool calls included only:

js          7
js_reset   35

Another affected session:

rollout-2026-09-11T23-12-52-01a09107-5523-7040-8f66-6ba7e6c185d4.jsonl

No actual local tool calls were detected.

Request

Please investigate the Windows desktop app’s local tool provisioning and the connection between chat sessions and the local command runner. The local runtime and integrated terminal appear operational, but exec is no longer included in the tool set supplied to chats.

Start by comparing the working rollout-2026-09-08T10-10-11-01a07ec7-b039-7e21-9a78-1936a098c6a6.jsonl with the affected rollout-2026-09-11T22-06-28-01a090ca-8ad6-7b73-bca6-adb0a8489611.jsonl and rollout-2026-09-11T23-12-52-01a09107-5523-7040-8f66-6ba7e6c185d4.jsonl. Trace local tool provisioning from the chat session to the command runner, using the listed feature flags as context. Done means Windows chats receive the local exec tool again while the integrated PowerShell terminal continues working.