Codex Desktop: Computer Use approval denied in old/resumed threads after restart, while new threads can authorize normally
What version of the Codex App are you using (From “About Codex” dialog)?
26.415.40636 (1799)
What subscription do you have?
Pro for $200
What platform is your computer?
macOS 26.4.1, Codex Desktop
What issue are you seeing?
After restarting Codex Desktop, old/resumed threads can no longer use Computer Use for app state access. Calls such as get_app_state for Chrome, Excel, or Word fail immediately with:
Computer Use approval denied via MCP elicitation for app 'com.google.Chrome'.
Computer Use approval denied via MCP elicitation for app 'com.microsoft.Excel'.
Computer Use approval denied via MCP elicitation for app 'com.microsoft.Word'.
Newly created threads can trigger Computer Use authorization and use Chrome/Word/Excel normally, so this does not appear to be a macOS Accessibility/Screen Recording permission issue or a missing plugin installation issue.
What steps can reproduce the bug?
- Open a Codex Desktop thread.
- Use Computer Use successfully in that thread, e.g. inspect Google Chrome.
- Restart Codex Desktop.
- Return to the old thread.
- Ask Codex to inspect Chrome with Computer Use.
- Observe that the tool returns approval denied via MCP elicitation.
- Create a new thread and ask the same Computer Use request.
- Observe that the new thread can use Computer Use successfully.
What is the expected behavior?
Old/resumed threads should either preserve the previous Computer Use approval state or re-trigger the app authorization prompt.
Additional information
Actual behavior
Old/resumed threads fail immediately with MCP elicitation approval denied. No usable reauthorization prompt appears.
Additional local evidence
The Computer Use plugin is enabled in ~/.codex/config.toml:
[plugins."computer-use@openai-bundled"]
enabled = true
The Computer Use client exposes only:
- mcp
- turn-ended
No public reset/authorize/grant command was found.
14 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Facing the same problem, plz fix the bug 😭
yes, same problem
Same issue
same issue
same issue
same issue
same issue
一样的问题
i have teh same issue too
same issue
Problem: your thread is likely affected by a Codex Desktop Computer Use approval bug..
Solution: start a new thread and ask it to us chrome using Computer Use.
But know this that computer use is extremely slower than browser automation
Adding another reproduction case with a slightly different pattern.
Environment:
Observed behavior in the same Codex thread:
list_appssucceeds and lists many apps, including Chrome, Finder, VS Code, Notes, MATLAB_R2026a, and Zotero.get_app_state("org.zotero.zotero")succeeds and returns a full UI tree.get_app_state("com.google.Chrome")fails with:Computer Use approval denied via MCP elicitation for app 'com.google.Chrome'.get_app_state("com.mathworks.matlab")fails with:Computer Use approval denied via MCP elicitation for app 'com.mathworks.matlab'.get_app_state("com.microsoft.VSCode")fails with:Computer Use approval denied via MCP elicitation for app 'com.microsoft.VSCode'.get_app_state("com.apple.finder")andget_app_state("com.apple.Notes")also fail with the same approval-denied pattern.get_app_state("com.openai.codex")returns a separate safety-policy denial, which appears expected.Local checks:
/Applications.com.mathworks.matlabcom.google.Chromecom.microsoft.VSCodeorg.zotero.zoteroWhy this seems like the same issue:
"Old threads denied, new threads authorize" is a classic session-state mismatch — the resumed thread's stored MCP authorization token references a Codex runtime identity (or CODEX_HOME) that doesn't match the current process after restart. New threads succeed because they re-elicit fresh; resumed threads can't because the stored auth doesn't apply anymore.
If you have more than one CODEX_HOME (or one that was reassigned between sessions), the resumed thread is trying to authorize against the old home. Fix is to consolidate to one canonical CODEX_HOME, or invalidate the old auth tokens in the stored thread state.
This belongs under the multiple-Codex-homes and session-reuse failure classes — I documented six root causes for "Computer Use authorization issues": https://igorganapolsky.github.io/openclaw-mac-ai-workstation-setup/troubleshooting.html
Free script (
scripts/self-diagnose.mjs) captures both home layouts + env into a redacted bundle. $19 quick read confirms whether stored thread state is the trigger or there's a second cause.