{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreid7szcdq3av5tnfs6t7t5c6dnd66clqtelugmzzxqb73bcfk5la64",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mlz2frey7t52"
  },
  "path": "/t/superapp-architecture-chatgpt-should-be-the-non-blocking-master-process-not-a-peer-tab/1381086#post_3",
  "publishedAt": "2026-05-16T23:13:04.000Z",
  "site": "https://community.openai.com",
  "textContent": "Good points. Let me address the last one first because it’s the most important: this architecture doesn’t require users to multi-task. The opposite — it _eliminates_ multi-tasking. Right now users are forced to multi-task: switch to Codex, monitor execution, switch back to Chat, rebuild context. The proposal is that users stay in one single-threaded conversation. Background workers run silently. Results come back when ready. The user never juggles anything.\n\nOn the infrastructure points (compute, OS constraints, billing): these are real engineering constraints, but they’re implementation details, not architectural blockers. The hierarchy change (chat as master, tools as workers) is a product design decision. How to schedule, meter, and bill the background workers is a separate problem that gets solved after the architecture is right.\n\nAnd on “why didn’t Anthropic do this” — I think it’s the organizational structure point. Chat team, Code team, Cowork team, each with their own roadmap. Making one team’s product subordinate to another’s is a political decision before it’s a technical one.",
  "title": "Superapp Architecture: ChatGPT Should Be the Non-Blocking Master Process, Not a Peer Tab"
}