›_ Codex Issues
Codex Issues / #29772

Appshots still fail with “Unable to attach appshot” on 26.616.81150 after pressing both Command keys

Open 💬 4 comments Opened Jun 24, 2026 by GGBondBlueWhale
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

Codex Desktop 26.616.81150 — Released Jun 24, 2026

What subscription do you have?

ChatGPT Pro

What platform is your computer?

  • macOS Tahoe 26.5.1
  • MacBook Pro 16-inch
  • Apple M5 Max
  • 128 GB memory

What issue are you seeing?

The Appshots feature cannot be used on my current Codex Desktop build.

In Settings > Appshots, the Appshots feature is visible and the configured hotkey is pressing both Command keys simultaneously. However, every time I press the hotkey, Codex appears to hang/pause for a short time and then shows this red toast:

Unable to attach appshot

No appshot is attached to the current conversation.

Steps to reproduce

  1. Open Codex Desktop on macOS.
  2. Go to Settings > Appshots and confirm the Appshots hotkey is configured.
  3. Bring another app/window to the front.
  4. Press both Command keys simultaneously.
  5. Wait for the attempted capture to finish.

Expected behavior

Codex should capture and attach an appshot of the frontmost window, including the relevant visual/text context.

Actual behavior

Codex pauses/hangs briefly, then fails with:

Unable to attach appshot

The appshot is not attached.

Additional information

This may be related to previous Appshots / Computer Use failures such as #28622 and #29101, but this report is for the newer Codex Desktop build 26.616.81150 on macOS Tahoe 26.5.1 with Apple Silicon.

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #28622

Powered by Codex Action

hwanseoc · 1 month ago

seems related to #25269

intelKANG · 1 month ago

Confirmed: I reproduced the same user-visible failure and the captureNotFound → update_poll_failed log pattern, then fixed it by replacing a symlinked root ~/.codex with a real directory and clearing stale Computer Use LaunchServices registrations.

After the repair, three consecutive Appshots completed with hadScreenshot=true, hadAxText=true, and status=success.

I posted the full sanitized procedure, verification steps, rollback guidance, and scope limitations here:

https://github.com/openai/codex/issues/25269#issuecomment-5084912745

This workaround only applies when ~/.codex is a symlink and the logs show captureNotFound / update_poll_failed; other Appshot failure signatures may have different causes.

intelKANG · 1 month ago

Bilingual standalone guide (English default, Chinese section included):

https://github.com/intelKANG/chatgpt-codex-appshot-fix

The guide documents the symlinked ~/.codex workaround, verification, rollback, and scope limitations.