Skip to content

It hits the token limit. #6722

Closed as not planned
Closed as not planned

Description

@EnterOgawa

What version of Codex is running?

0.58.00

What subscription do you have?

pro

Which model were you using?

gpt-5.1 high

What platform is your computer?

windows11pro

What issue are you seeing?

The following message appears and the session cannot continue.

■ Conversation is still above the token limit after automatic summarization (limit 244800, current 248148). Please start
a new session or trim your input.
■ stream disconnected before completion: stream closed before response.completed

Image

What steps can reproduce the bug?

When using it near the context limit, it ends up in this kind of state.
By the way, this session has repeatedly gone from full context to automatic compaction multiple times since 0.57.00.
I tried ending it once with Ctrl+C and resuming, but the situation didn’t change.
Even after using the /compact command, the situation remains unchanged.

What is the expected behavior?

No response

Additional information

No response

Activity

  1. added
    rate-limitsIssues related to rate limits, quotas, and token usage reporting
    on Nov 16, 2025
  2. etraut-openai commented on Nov 26, 2025

    @etraut-openai
    Contributor

    You appear to be confusing context window usage (which is affected by /compact) and token usage rate limits. The error you are seeing here indicates that you have reached your five-hour token rate limit. This will reset after the five-hour period elapses.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingrate-limitsIssues related to rate limits, quotas, and token usage reporting

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions