GPT-5.6 Sol entered a repetitive agent loop and consumed ~80% of a freshly reset usage allowance

Codex surface

Codex app / agent session (exact client version was not captured at the time of the incident)

Model and configuration

• Model: GPT-5.6 Sol
• Reasoning effort: Extra High
• Task type: long-running redesign and implementation work in a large existing codebase

What issue are you seeing?

Immediately after applying a banked rate-limit reset, I started a repository task with GPT-5.6 Sol. The agent entered a repetitive/no-progress loop instead of continuing normal implementation work.

While the loop continued, the freshly reset usage allowance dropped from approximately 100% to approximately 20%. In other words, roughly 80% of the reset allocation was consumed by one abnormal session without corresponding useful progress.

The affected project state and resulting changes are preserved in a private Git repository, so commit history and diffs can be provided privately if the Codex team needs them for investigation.

Steps that led to the issue

1. Apply a banked rate-limit reset.
2. Start a large repository redesign/implementation task using GPT-5.6 Sol with Extra High reasoning.
3. Allow the agent to continue working for an extended session.
4. The agent begins repeating substantially the same work/actions without meaningful forward progress.
5. Usage continues to be consumed until the session is manually stopped.

Expected behavior

Codex should detect repeated actions or a sustained lack of progress and either stop, ask for confirmation, or recover from the loop before consuming most of a newly reset allowance.

Actual behavior

The loop continued and consumed about 80% of the freshly reset usage allowance.

Additional information

This issue is being filed as a technical bug report. A separate support request may be needed for restoration of the usage allowance. Session telemetry, a feedback/session ID, and private Git evidence can be supplied when available.