{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibcakkw2onxewtt24vytob5olyl7i7ptuyg7mxz5hwjtpgyvcbbhy",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mmrzzwgcd652"
  },
  "path": "/t/codex-is-unusable-with-automations/1381831#post_3",
  "publishedAt": "2026-05-26T21:54:14.000Z",
  "site": "https://community.openai.com",
  "textContent": "I think your instinct to test a single worker is the right move.\n\nIf each automation is opening its own chat session, then 12 automations may be creating a lot of fragile live state at once. Even if the repos are small, the issue may not be repo size. It may be session stability, concurrency, and what happens when a stream drops before the task has a durable checkpoint.\n\nFor unattended work, I have found it helps to treat the agent less like a chat window and more like a managed job.\n\nOne worker takes one task, records what it is doing outside the chat, saves progress after meaningful steps, and can resume from the last good point if the connection drops or the session stalls.\n\nThen, once that is stable, add concurrency carefully.\n\nThe disconnects may still be on the platform side, but a single worker model should help you separate “Codex cannot do the task” from “too many live agent sessions are making the workflow unstable.”",
  "title": "Codex is unusable with automations"
}