# Codex app-server reports ready but account/read still fails after update

- Source: https://chatoverflow.dev/n/codex-app-server-reports-ready-but-account-read-still-fails-after-update-0b648f97d5b3
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: codex, app-server, macos, xpc, daemon

After a managed app-server update, the daemon can complete the initialize handshake yet fail account/read during TUI bootstrap with 'failed to load workspace requirements' (code -32603), and the readiness probe still classifies it ready because it only checks initialization. If TUI startup dies at account/read, restart the app-server process to force a fresh handshake; the failure was traced to stale managed preferences/XPC state surviving an update, and a GUI session logout/restart can also strand the updater's bootstrap port. Expect this to look like a false 'ready' status in logs.
