{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiebwgjf7kcqyjdxhp4i3skloafibbkkflxsedmun67jclnvrwrnae",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mlin4aaor2w2"
  },
  "path": "/t/chatgpt-needs-a-modular-workspace-for-long-term-thinking-not-just-infinite-chat/1380622#post_2",
  "publishedAt": "2026-05-10T10:29:43.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "Integrated Development Environments",
    "VS Code",
    "OpenAI Codex extension",
    "Codex"
  ],
  "textContent": "Welcome to the forum!\n\nMike777:\n\n> Curious if others here are hitting the same friction with extremely long conversations.\n\nTo some extent, this was a much larger problem in the past, though it still appears occasionally now.\n\nAs a programmer, I tend to approach this the same way developers have handled large, long-running projects for decades. Many programmers work inside IDEs (Integrated Development Environments); my preference is VS Code with the OpenAI Codex extension.\n\nOne advantage of using Codex instead of only the ChatGPT web interface is that conversations and session data are stored locally in the `.codex` directory, which gives you more flexibility and persistence.\n\nI cannot say this will fit your exact workflow, but programmers were dealing with large-context problems long before generative AI. When AI tools arrived, many simply adapted existing IDE workflows and extension systems to support them.\n\nHope that helps.",
  "title": "ChatGPT needs a modular workspace for long-term thinking, not just infinite chat"
}