[macOS][Desktop 26.825.32147] Local project task loses shell/filesystem tools; terminal cannot attach

What version of Codex are you using?

Codex Desktop 26.825.32147, released August 28, 2026.

Platform

macOS. Exact Darwin version and architecture are unavailable from this task because the local shell runner is missing.

What issue are you seeing?

A fresh local Codex project task has no usable shell runner or normal filesystem inspection tools, so the agent cannot compile, inspect the workspace, or run even basic diagnostics.

This is not a Rust/project compile error. No command reaches Cargo, the sandbox, or approval handling.

Observed behavior

In a local project task:

• The model-visible tool catalog contains Codex app/thread tools and apply_patch, but no shell/exec_command runner and no ordinary file-reading tool.
• A spawned subagent inherited the same missing shell/filesystem capability.
• read_thread_terminal returns:

No app terminal session is attached to this thread yet.

• Requesting an integrated terminal only returns:

{"status":"queued","threadId":"01a04ada-f0f2-7322-b2f2-b1f74b0d281e"}

• A follow-up terminal read still reports:

No app terminal session is attached to this thread yet.

• The saved project inventory reported the expected local project path but marked it as isGitRepository:false; path details are omitted here to avoid publishing local user information.
• Recreating/restarting with a brand-new local project did not resolve the missing runner.
• Changing models did not recover this existing task.

Expected behavior

A local Codex project task should receive the normal local coding tool surface, including shell execution and scoped filesystem access. Asking the agent to compile a Rust workspace should allow it to run commands such as:

cargo fmt --all -- --check
cargo clippy --workspace --all-targets --all-features -- -D warnings
cargo test --workspace --all-features
cargo build --workspace --release

Actual impact

Local coding work is completely blocked in Codex Desktop. The agent cannot inspect files, cannot run cargo, cannot verify the project, and cannot distinguish a real build failure from an app tool-provisioning failure.

Reproduction outline

1. Use Codex Desktop 26.825.32147 on macOS.
2. Create or open a fresh local project task.
3. Ask Codex to run a local command or compile a Rust workspace.
4. Observe that no shell runner is available to the task.
5. Try opening/reading the integrated terminal.
6. Observe that read_thread_terminal reports no terminal session attached.

Related reports

This appears related to, but distinct from:

• #41255: 26.825.x GPT-5.6 code-mode exec failures.
• #31417: macOS read_thread_terminal cannot see an attached terminal.
• #39774: macOS native tools/tool catalog dropping across sessions.
• #41409: exact 26.825.32147 build showing session routing/capability provisioning problems.

The distinguishing symptom here is that a macOS local project task on 26.825.32147 is provisioned without the shell/filesystem tools needed for local coding at all, and the terminal attachment workaround does not recover them.

Start by reproducing the missing shell/filesystem tools on macOS with Codex Desktop 26.825.32147, then inspect the tool catalog, the integrated-terminal request, and read_thread_terminal behavior. Compare the related reports listed in the issue. Done means a fresh local project task exposes shell and filesystem access and can attach a terminal for the listed Cargo checks.