codex - 💡(How to fix) Fix Codex Desktop regression: direct @Mac app mentions no longer route through Computer Use / Any App

What version of the Codex App are you using (From "About Codex" dialog)?

Codex Desktop 26.513.20950 / build 2816

Additional local versions:

codex-cli 0.130.0
computer-use@openai-bundled 1.0.791
Codex bundle id: com.openai.codex

What subscription do you have?

Pro / paid account.

What platform is your computer?

macOS 26.3 (25D125)
arm64 Apple Silicon

What issue are you seeing?

Direct @<Mac app> mentions no longer work as an invocation path for using local Mac apps through Codex Desktop.

Current workaround:

1. I can explicitly mention @Computer / Computer Use.
2. Then I can write the app name in natural language, for example "use Computer to access <app name>".
3. Codex can then use Computer Use as the tool surface.

But the intended direct app mention path no longer works. Previously I could @ a local app directly and have Codex route to it. Now I need to explicitly route through @Computer and spell out the app name in the prompt.

This is a workflow regression because the direct @<app> path was the safer, more explicit way to tell Codex which local app to operate. Requiring a natural-language app name after @Computer makes tool routing more ambiguous and less reliable.

Possible related local context:

• Computer Use is enabled in ~/.codex/config.toml:

[plugins."computer-use@openai-bundled"]
enabled = true

• The Computer Use app approval store exists at:

~/Library/Group Containers/2DC432GLL2.com.openai.sky.CUAService/Library/Application Support/Software/ComputerUseAppApprovals.json

• On this machine that store currently contains one top-level key, approvedBundleIdentifiers, with 576 approved bundle identifiers.
• I previously used a local workaround/skill-like flow to bulk-add installed apps to the Computer Use "always allowed" approval store because app approvals started prompting manually after an update. That may or may not be related, but direct app mentions should still degrade gracefully or remain supported even when a broad approval list exists.

What steps can reproduce the bug?

1. Open Codex Desktop on macOS.
2. Ensure Computer Use / Any App is enabled.
3. In the composer, type @ and try to mention a local Mac app directly, using the app-name mention flow that previously routed Codex to that app.
4. Observe that direct app mentions no longer route/work as intended.
5. In the same environment, explicitly mention @Computer / Computer Use and then write the app name in natural language.
6. Observe that the workaround still works: Codex can use Computer Use when routed through @Computer, but not through the direct app mention path.

What is the expected behavior?

Direct app mentions should remain available and functional:

1. Typing @ should allow selecting local Mac apps / Any App targets directly, not only the generic Computer Use plugin.
2. Direct @<app> mention selection should route Codex to the intended local app through Computer Use / Any App.
3. A broad local approval list should not break app mention discovery or routing.
4. If the product renamed Computer Use to Any App, existing direct app mention behavior should remain backwards-compatible or show a clear migration path.

Additional information

Related but not identical issues:

• #22805: @Computer / Computer Use disappearing from mention completion after Any App update.
• #22716 and #22752: general @ plugin picker loading/hanging regressions.

This report is distinct because @Computer is still usable as a workaround here; the broken surface is direct @<Mac app> mention/routing.

The practical impact is significant: I use Codex Desktop to intentionally operate local Mac apps, and direct app mentions were the precise control surface for that. The current workaround is usable, but it is not the intended UX and is less reliable.