Summary
During longer Codex chat sessions, the token/context indicator can stay at 100% even though Codex is still running normally.
This makes the indicator difficult to trust because it looks like the context window is exhausted, but the session continues working.
Steps to reproduce
- Start Dr. Claw.
- Open any project and select Codex as the active provider in Chat.
- Have a long back-and-forth conversation with Codex in the same session.
- Continue the session until the token/context pie reaches
100%.
- Observe that Codex still continues responding normally even while the indicator remains at
100%.
Expected behavior
If the indicator is intended to represent current context usage, it should not remain pinned at 100% while the session is still functioning normally.
Actual behavior
- the Codex token/context pie reaches
100%
- it continues to show
100% during a long session
- Codex still responds and continues working normally
VibeLab version
latest
Operating system
Ubuntu 22.04.5 LTS
Install method
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information

Summary
During longer Codex chat sessions, the token/context indicator can stay at
100%even though Codex is still running normally.This makes the indicator difficult to trust because it looks like the context window is exhausted, but the session continues working.
Steps to reproduce
100%.100%.Expected behavior
If the indicator is intended to represent current context usage, it should not remain pinned at
100%while the session is still functioning normally.Actual behavior
100%100%during a long sessionVibeLab version
latest
Operating system
Ubuntu 22.04.5 LTS
Install method
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information