[Feature]: Support Codex Computer Use approval flow in T3 Code

[leonardoxr]

Problem or use case

I can use Codex with the bundled computer-use plugin in the Codex ecosystem, but in T3 Code there is no visible approval flow for enabling or authorizing Computer Use.

From the user perspective, this makes Computer Use feel unsupported or broken:

• T3 Code wraps codex app-server
• the Codex-side computer-use plugin can be enabled
• but when a prompt asks to use Computer Use, T3 Code does not surface an allow prompt or clear unsupported-state message

Right now it is hard to tell whether:

• T3 Code does not support this capability yet
• the capability is available but the approval UX is missing
• or macOS permissions need to be granted somewhere else

Proposed solution

When a Codex session requests Computer Use, T3 Code should surface a first-class approval flow in the UI.

At minimum:

• detect that the session is attempting to use Codex Computer Use
• show a clear prompt explaining what access is needed
• route the user through any required desktop permission flow
• show a clear error or unsupported message if this capability is not yet supported in T3 Code

Ideally, T3 Code would support the same practical workflow users expect from Codex Desktop:

• request or approve Computer Use from the UI
• explain required macOS permissions like Accessibility and Screen Recording
• make the capability state visible per session

Why this matters

This would make T3 Code much more trustworthy and understandable for users trying advanced Codex capabilities.

Without this, users get stuck in a confusing state where:

• Computer Use appears enabled on the Codex side
• prompts to use it do not work in T3 Code
• and there is no clear indication whether the blocker is product support, app permissions, or missing UI

A clear approval flow, or even a clear unsupported-state message, would remove a lot of confusion.

Smallest useful scope

The smallest useful version would be:

• detect when a session tries to use Codex Computer Use
• show a clear message that this is unsupported in T3 Code today, or
• if supported, show the approval prompt and required permission guidance

Even that would be much better than failing silently.

Alternatives considered

• Using Codex Desktop directly for Computer Use
• Checking local Codex MCP or plugin config outside T3 Code
• Manually inspecting macOS permissions

Those can help debug, but they do not solve the missing T3 Code UX.

Risks or tradeoffs

• This may require extra plumbing between T3 Code and codex app-server
• Desktop permission handling on macOS may need app-specific UX and documentation
• The capability may differ between the desktop app and the app-server path, so the UI should avoid implying support if the backend cannot actually provide it

Examples or references

Related issues:

• The app does not load a local MCP server defined in .codex/config.toml. #297 The app does not load a local MCP server defined in .codex/config.toml.
• macOS: apps launched from integrated terminal can't request TCC permissions (mic, camera) #728 macOS: apps launched from integrated terminal can't request TCC permissions (mic, camera)
• UX: App should request folder access upfront instead of showing auth error before starting chat #199 UX: App should request folder access upfront instead of showing auth error before starting chat

This request is specifically about surfacing the Codex Computer Use approval or support flow inside T3 Code.