Refreshed the three Codex auth slots used by the autocoder-engine deployment after agent runs started failing with refresh-token invalidation.
The three Kubernetes secrets mounted into AutoCoder (autocoder-codex-auth-1, autocoder-codex-auth-2, autocoder-codex-auth-3) still contained stale auth.json files from 2026-04-18. Those tokens reported as logged in but failed on real codex exec with refresh-token reuse / token-expired errors.
codex login --device-auth.autocoder-codex-auth-1autocoder-codex-auth-2autocoder-codex-auth-3autocoder-engine.codex exec:
k8s-slot1-okk8s-slot2-okk8s-slot3-okThe deployment mounts these secrets via subPath, so refreshed secret content is not guaranteed to appear in an already running container. A rollout restart is required, and a second restart may be needed if kubelet still serves cached secret content during the first new pod start.