No credit

Open 💬 1 comment Opened Jul 23, 2026 by leoagoss
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What issue are you seeing?

019f8142-d413-7140-915c-96343691e3a3
My availability was at 60%. I submitted a task to fix a simple variable, just as I had done before, and my availability had only dropped by 1%. But yesterday, I thought it was strange because it was taking longer than usual, and suddenly Codex notified me that I had no availability left and wouldn't be able to work until the 28th!!!

<img width="808" height="824" alt="Image" src="https://github.com/user-attachments/assets/697ce4b7-4b8d-428e-ade9-c3d1c52ff6e0" />

What steps can reproduce the bug?

Yesterday, Codex was constantly repeating “Automatically compressed context” and taking a long time. I thought this was unusual—I usually use it on medium-sized projects. I didn't do anything out of the ordinary, as far as I know; I just let Codex respond to a simple variable change in my project.

What is the expected behavior?

I'm waiting to hear your thoughts and will hold off until the 28th to continue :-(

Additional information

_No response_

View original on GitHub ↗

1 Comment

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #34395
  • #34058
  • #33803
  • #33685

Powered by Codex Action