Superapp Architecture: ChatGPT Should Be the Non-Blocking Master Process, Not a Peer Tab

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.

On 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.

And 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.