{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibxxqxqj42uoccfahzdmpk44zha33uwqqwc3gomw7dnytm266qxb4",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mmrmmcnujtl2"
  },
  "path": "/t/codex-is-unusable-with-automations/1381831#post_1",
  "publishedAt": "2026-05-26T18:04:54.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "https://chatgpt.com/backend-api/codex/responses"
  ],
  "textContent": "I’ve started experimenting with automations but I have found it to be unusable. I am running a total of 12 automations that are on relatively small repos one is around 10K lines of code, and the other is barely 1K.\n\nThese automations constantly find themselves reconnecting, or stalling. The most obvious error is this which I’ve seen has been open for a while on GitHub issues. stream disconnected before completion: error sending request for url (https://chatgpt.com/backend-api/codex/responses)\n\nFor me, the purpose of these coding agents / AI automations are so that I don’t have to sit and watch over them but instead they autonomously work on their own given prompt instructions but it’s at the point where I am considering alternatives over Codex. I am on a ChatGPT Pro subscription.\n\nEach agent opens up its new chat session per automation.",
  "title": "Codex is unusable with automations"
}