openai / openai/codex

Subject: Previously visible Work history disappeared when weekly limit was reached; selective project-sync failure

Open
#44,812 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug rate-limits session
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

On September 10, 2026, approximately around 3 p.m. Pacific time, I reached my weekly Work-agent limit in the desktop beta. Until then, my completed work was visible. Afterward, approximately the last two days of content disappeared from “Black Hills solve” in my “Treasure Map Adventure” project.
Separately, the mobile app is missing new projects from approximately the last three or four days, while other projects and chats are synced and current. Earlier troubleshooting has not restored the missing content.
Please investigate whether the missing messages and Work task records remain stored, whether reaching the limit affected access to existing Work history, and whether this relates to the September 10 Work incident.
Please also review usage charged for the inaccessible work and address restoration of the corresponding included allowance or adjustment of any purchased credits. I am requesting recovery and accounting review—not simply instructions to buy more usage or repeat the work.

reiddaniel79@gmail.com
session id: 01a06d86-d94e-7c42-bca0-d8d9ed05bedb

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file, test, or entry point is identified. Start by tracing the September 10 Work-limit event using the provided session ID and comparing desktop Work history with mobile project sync. Done means determining whether the messages and task records remain stored and documenting the required usage restoration or accounting adjustment.

Written by the indexing model from the issue text.

Assessment

Domain
backend-api-design, cloud
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.