OpenAI Codex Kept Running 17 Hours After Hitting Usage Limit
Present-Quantity-813 · reddit · 2026-07-30
A developer discovered that OpenAI's Codex Desktop continued executing an in-flight task for about 17 hours even after the account's usage hit zero. While new tasks were blocked, the existing goal-driven session kept progressing.
The user is building Aming Claw, an agent-governance system using a push architecture where an external layer determines the agent's position and supplies actions. This raises a key infrastructure question: for long-running agents driven by external goals, should the task's endpoint be defined by a model turn, a workflow step, or the semantic return of the external goal?
More from coding & agent
- 'LLM code is sloppy' rebutted with real ffmpeg code: identical if/else branches in a top library — kingslyj · 2026-10-16
- Office-editing tool calls need file, worktree and unit: lessons from dsh-univer-office — FunDistribution6537 · 2026-10-16
- Architect MD workflow: Gemini one-shot outputs that beat Opus, via 5-lens plan critique — oikk01 · 2026-10-16
- Prove a coding agent actually ran the tests: check artifacts, not approvals — ComprehensiveShake76 · 2026-10-16
- Building an acceptance harness for AI spreadsheet edits: allowlists, recalc checks, idempotency — ukdicha-modakkk · 2026-10-16
- Agent actions need checks outside the model: NVIDIA demos lean on guardrails amid wave of real agent incidents — Creamy-And-Crowded · 2026-10-16