{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicxsjk6guhydtpmnq6fac57sn4czguarxg6ooj7lk2pgxhfowtnfm",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mk42bva6cdp2"
  },
  "path": "/t/feature-request-native-chatgpt-codex-thread-bridge/1379162#post_3",
  "publishedAt": "2026-04-22T17:16:08.000Z",
  "site": "https://community.openai.com",
  "textContent": "Thanks, good to hear back. As far as Im concerned, Pro is streets ahead of every other model. Now that its got so fast, its a crime not to use it. For me, Giving Pro access to Codex or VScode would basically be AGI. The main blockers and errors in my code comes because Pro doesn’t have full state over the repo. Codex (especially not in plan mode) is a clunky thinker and really doesn’t understand subtleties, so it tends to misinterpret fine distinctions or why something is being done. Which means its explanations to Pro are often not quite right, and the cycle goes off the rails.",
  "title": "Feature request: native ChatGPT<->Codex thread bridge"
}