Rolled out AutoCoder Engine commit 62e18c1cd33d035e61e278730d5e899a2f658370 to production via the normal Gitea Actions deployment pipeline.
refresh_token_reused, refresh-token duplicate-use messages, and Codex 401 Unauthorized websocket failures.refresh token duplicate use, please log in again.cargo fmt --checkcargo test780 for commit 62e18c1cd33d035e61e278730d5e899a2f658370 completed successfully:
classify: successfrontend_rust_checks: successbuild_frontend_image: successbuild_backend_image: successrollout_frontend: successrollout_backend: successdeploy_cronjobs: successdeployment/autocoder-engine successfully rolled out with image gitea.app.lan/autocoder/autocoder-engine:sha-62e18c1cd33ddeployment/codecartography-frontend successfully rolled out with image gitea.app.lan/autocoder/autocoder-engine-frontend:sha-62e18c1cd33dAfter the first rollout, an audit found that suppressed refresh-token reuse worker failures were also being marked as fully surfaced. That could prevent the affected issue from being picked up by startup recovery if no active waiter was present.
Rolled out follow-up commit e29e60be170339279dd1c80cfa21e2f98774b44c on 2026-05-28. The correction keeps the issue eligible for recovery while still suppressing the duplicate failure comment.
cargo fmt --checkcargo teste29e60be170339279dd1c80cfa21e2f98774b44c completed successfully:
classify: successbuild_backend_image: successrollout_backend: successdeploy_cronjobs: successdeployment/autocoder-engine successfully rolled out with image gitea.app.lan/autocoder/autocoder-engine:sha-e29e60be1703deployment/codecartography-frontend remained on image gitea.app.lan/autocoder/autocoder-engine-frontend:sha-62e18c1cd33dNo manual Kubernetes manifest changes were applied. Rollout used the repository-managed deployment pipeline.