{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidtgbesmxch33gsupxneyoedjoctzbthaontymdbdepls4fvup6sq",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mmcwcihixja2"
  },
  "path": "/t/i-wish-there-was-a-voice-brainstorm-mode-in-codex/1381368#post_4",
  "publishedAt": "2026-05-20T20:38:25.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "Superapp Architecture: ChatGPT Should Be the Non-Blocking Master Process, Not a Peer Tab",
    "Use cases and examples"
  ],
  "textContent": "Superapp Architecture: ChatGPT Should Be the Non-Blocking Master Process, Not a Peer Tab Use cases and examples\n\n> Hi, I’m in the Codex developer program. I have a specific architectural suggestion for the superapp that I think is worth 3 minutes of someone’s time. Your current direction: merge ChatGPT + Codex + Atlas into one app with multiple modes. What I think it should be: ChatGPT is the only interface. Codex and Atlas are non-blocking background subprocesses that ChatGPT can spawn. The difference: - “Merge” means three tools in one window. Users still switch between them. - “Orchestrate” means on…",
  "title": "I wish there was a voice \"brainstorm\" mode in Codex"
}