[Ops] Restore Codex CLI authentication for hourly release pulse #20

Closed
opened 2026-08-04 14:47:03 +00:00 by rockachopa · 1 comment
Member

Hourly release pulse on 2026-08-04 selected issue #9 but Codex CLI could not start implementation. codex exec returned HTTP 401 on both WebSocket and HTTPS responses endpoints: missing bearer/basic authentication. No repository files were changed.

Acceptance criteria:

  • Standalone Codex CLI has valid non-interactive credentials in the cron/service context.
  • codex exec can complete a minimal read-only repository task with PTY.
  • Re-run the release planner and resume issue #9 under strict TDD.
Hourly release pulse on 2026-08-04 selected issue #9 but Codex CLI could not start implementation. `codex exec` returned HTTP 401 on both WebSocket and HTTPS responses endpoints: missing bearer/basic authentication. No repository files were changed. Acceptance criteria: - Standalone Codex CLI has valid non-interactive credentials in the cron/service context. - `codex exec` can complete a minimal read-only repository task with PTY. - Re-run the release planner and resume issue #9 under strict TDD.
timmy was assigned by rockachopa 2026-08-04 14:47:03 +00:00
Author
Member

Resolved: hourly pulse now implements directly as the pinned Hermes coding agent; standalone Codex CLI auth is no longer a pipeline dependency.

Resolved: hourly pulse now implements directly as the pinned Hermes coding agent; standalone Codex CLI auth is no longer a pipeline dependency.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#20
No description provided.