11 people reported

All time, since Sep 25, including 9 thumbs-up on GitHub.

"No complete local package" error

“0.157.1 and 0.158.0 are broken on my machine.”

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/15149/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

CLI fails to start with "no complete local package" error. Running codex after upgrading to 0.157.x or 0.158.0 fails, while codex --version still works; seen with Arch package and renamed Windows binaries.

Is this your bug?

File my report
Where
CLI startup
Error text
Error: this CLI has no complete local package; install a packaged Codex CLI or use the standalone installerPasted in 2 reports
Versions
0.157.0 to 0.157.1
Platforms
Linux, Windows
How bad
Breaks a normal workflow.

Part of: Background daemon fails at startup3 bugs

  1. Daemon access denied on Windows7 people
  2. WinGet daemon fails to start3 people

Not quite your bug?

  1. Daemon executable not found loop3 people

Original reports2, newest first

  1. Windows 10: "no complete local package" on 0.157.1/0.158.0On GitHub#48899
  2. Codex 0.157.0 no longer starts with the Arch Linux package unless --no-daemon is usedOn GitHub#48050

Do you work on Codex?

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