{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihmfs25m7ofemt4ajd237qiriiwpkat2a223gcuqozjxltgyvzqom",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mnrkfhmueqp2"
  },
  "path": "/t/using-chatgpt-for-planning-vs-codex/1382876#post_11",
  "publishedAt": "2026-06-08T10:45:39.000Z",
  "site": "https://community.openai.com",
  "textContent": "mat.eo:\n\n>   * Is much easier for back-and-forth\n>\n\n\nhmmm … Isn’t switching a bit “back and forth”…\n\nI plan my work inside Codex CLI.\n\nThe one issue with this of course is the other issues you’ve mentioned and the lack of cloud persistence, although I tend to expand Readme’s and test specs to ensure the behaviour is fully documented and committed to the code base.\n\nIt would be great to be able to “upload” CLI sessions as a ChatGPT convo and additionally be able to import one - after all you are authenticated!",
  "title": "Using ChatGPT for Planning vs Codex?"
}