2 people reported

All time, since Sep 30.

Locked use fails after display sleep

“The Mac is locked and automatic unlock could not unlock it. Ask the user to unlock the Mac manually before continuing.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/14629/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Locked use fails to unlock Mac after display sleep. Native Computer Use works while unlocked, then fails after the display dims or switches off automatically with Locked use enabled.

Is this your bug?

File my report
Where
Computer Use
Error text
The Mac is locked and automatic unlock could not unlock it. Ask the user to unlock the Mac manually before continuing.
Versions
26.928.20755 to 26.1013.40934
Platforms
macOS
How bad
Breaks a normal workflow.

Not quite your bug?

  1. Locked use fails on Intel Macs2 people

Original reports2, newest first

  1. Native Computer Use fails after automatic display sleep with password-on-wake set to Never (macOS, build 20770)On GitHub#55615
  2. Native Locked use fails after display-dim lock during unattended local Goal, after earlier successful unlocksOn GitHub#49808

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.