{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreias4fylnhs4uvyw3qbzvkajvklz34qskn6bz27w64vot44k2kxnvu",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mo6ye5zem4x2"
  },
  "path": "/t/codex-gpt-5-5-reliability-has-become-a-serious-trust-issue-for-daily-project-work/1383615#post_1",
  "publishedAt": "2026-06-13T18:45:45.000Z",
  "site": "https://community.openai.com",
  "textContent": "I am writing this not as an outside observer, but as a daily Codex user whose real project is being affected by this workflow.\n\nWhat I am experiencing is very clear: Codex keeps repeating the same mistakes in my project, even after I have explicitly emphasized the same constraints more than 20 times. It fails to respect project-specific rules, loses track of context, and makes decisions that actively put the structure of my project at risk.\n\nI cannot know whether this is caused by a model regression, a Codex pipeline issue, routing / deployment changes, long context failure, or something else. But from the user side, the result is the same: trust loss.\n\nThe cost of using the model has increased, yet the reliability I experience in real project work has not improved accordingly. In fact, my experience has become more unstable and more frustrating over time.\n\nI am not claiming to know exactly what is happening internally. I am telling you how it feels as a paying customer who works with Codex every day: the product is becoming harder to trust, harder to rely on, and more expensive to use at the same time.\n\nThat combination is extremely frustrating.",
  "title": "Codex GPT 5.5 Reliability Has Become a Serious Trust Issue for Daily Project Work"
}