codex - 💡(How to fix) Fix Appshots hotkey dispatches but capture never starts on macOS arm64

What version of the Codex App are you using?

Codex App: 26.519.41501 (CFBundleVersion 3044) Codex CLI bundled with app: 0.133.0-alpha.1 Computer Use helper: com.openai.sky.CUAService, version 1.0 build 799

What platform is your computer?

macOS 15.6.1 (24G90) Darwin 24.6.0 arm64 Apple Silicon / Apple M1 Pro

What issue are you seeing?

Appshots does not attach anything after pressing the configured hotkey.

This is not the same as #24009, where the hotkey never fires. In this case, Codex logs show the Appshots hotkey is registered, pressed, and dispatched to the existing chat window, but no capture request appears to start afterward and no appshot is attached.

This also looks related to #24056, but I do not see the same Failed to spawn managed Computer Use service or Appshot capture request created log lines. The log appears to go silent after dispatch.

Expected behavior

Pressing the Appshots hotkey should capture the frontmost app/window and attach the appshot to the current Codex thread.

Actual behavior

The shortcut is detected and dispatched, but nothing is attached to the chat.

Relevant Codex app log lines:

2026-05-25T09:23:06.108Z info Registering appshot hotkey hotkey=DoubleCommand
2026-05-25T09:23:06.109Z info Registered appshot hotkey hotkey=DoubleCommand
2026-05-25T09:25:24.847Z info Appshot hotkey pressed hotkey=DoubleCommand
2026-05-25T09:25:24.847Z info Dispatching appshot hotkey target=existing-chat windowId=1
2026-05-25T09:25:28.804Z info Appshot hotkey pressed hotkey=DoubleCommand
2026-05-25T09:25:28.804Z info Dispatching appshot hotkey target=existing-chat windowId=1
2026-05-25T09:25:29.445Z info Appshot hotkey pressed hotkey=DoubleCommand
2026-05-25T09:25:29.445Z info Dispatching appshot hotkey target=existing-chat windowId=1
2026-05-25T09:25:29.970Z info Appshot hotkey pressed hotkey=DoubleCommand
2026-05-25T09:25:29.971Z info Dispatching appshot hotkey target=existing-chat windowId=1

The desktop feature log from the same launch does not list Appshots/capture explicitly:

Features enabled enabledFeatures="enable_request_compression, collaboration_modes, personality, request_rule, image_generation, image_detail_original, workspace_dependencies, guardian_approval, apply_patch_streaming_events, workspace_owner_usage_nudge, enable_mcp_apps, apps, plugins, tool_search, tool_suggest, tool_call_mcp_elicitation"

codex features list shows computer_use enabled:

computer_use stable true

Reproduction steps

1. Open Codex App.
2. Open Settings > Appshots.
3. Use the DoubleCommand Appshots hotkey.
4. Focus another app/window.
5. Press both Command keys.
6. Observe that Codex logs Appshot hotkey pressed and Dispatching appshot hotkey, but no Appshot is attached.

Troubleshooting already tried

• Restarted Codex.
• Killed stale SkyComputerUseClient helper processes.
• Reopened Codex so there is only one Codex process, one hotkey monitor, and one SkyComputerUseClient helper.
• Checked macOS Privacy & Security settings for Accessibility and Screen Recording / Screen & System Audio Recording for Codex and Codex Computer Use.
• Tried again after the permission and helper cleanup.
• Ran codex doctor; auth/config/state were healthy.
• Checked macOS unified logs for recent Screen Recording/TCC denial or helper crash; no clear denial or crash appeared.

Notes

This looks like a possible Appshots feature-availability/runtime wiring issue: the Appshots UI and hotkey are present, but the actual capture flow appears not to start after the dispatch event.

Related issues:

• #24009: hotkey registers but never fires. This differs because my hotkey does fire.
• #24056: Appshots fail with managed Computer Use service spawn failure. This may be related, but my logs do not show the spawn failure or capture request lines.
• #24234: AppShots failure caused by non-default ps from procps. I do not see that ps: rss: requires entitlement error in my logs.