{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicjegm7nfaon4ezjohxpasi5y3azqbvj3njbs7xk62ydbmom3q5sq",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mnofnsazl7a2"
  },
  "path": "/t/how-to-stop-codex-from-rushing-fixes/1382830?page=2#post_25",
  "publishedAt": "2026-06-07T03:55:56.000Z",
  "site": "https://community.openai.com",
  "textContent": "shamimarakhaliq:\n\n> Allowed actions: Run experiments. Reanalyse existing data. Write notes.\n\nPersonally, I define action as “single transformation that does not need to be broken down into steps”. I think ai also acts under a similar definition.\n\nThe ones you’ve mentions here, are more like workflows to me. And I would definitely automate or, at least, define them in a more structured way with failure procedure escalation descriptions.\n\nAre those get defined in your context window at some point? If so, how? If not, why?",
  "title": "How to stop Codex from rushing fixes?"
}