DOOM MCP vs OpenAI Agents Python

Chris Nager built a fully playable DOOM that runs as an MCP (Model Context Protocol) app, rendering inline inside Claude and ChatGPT without a separate browser tab. The architecture uses two MCP tools — create_doom_session for inline-capable hosts and get_doom_launch_url as a browser fallback — combined with cloudflare/doom-wasm for the game runtime and a signed token system that maintains session state across both surfaces. The result is the same session whether you're playing inline or in a tab. The key technical challenge was avoiding iframe and CSP (Content Security Policy) issues. Rather than embedding a browser page inside the MCP iframe, the DOOM canvas runs directly inside the host's iframe — a subtle but critical distinction that resolved a class of rendering and input-handling bugs. The final implementation is intentionally stripped down: no save/load, no persistence adapters, just stable playable DOOM. Beyond the novelty, this project is a concrete demonstration that MCP apps are interactive surfaces, not just tool-calling JSON endpoints. The progressive enhancement pattern — same signed-token foundation serving both inline and browser modes — is a reusable architecture for any game or interactive experience that wants to live inside an AI assistant. Nager open-sourced the implementation and the blog post is a detailed technical breakdown.

OpenAI's openai-agents-python is the production evolution of the experimental Swarm framework — a lightweight, opinionated Python SDK for building multi-agent workflows without the bloat of heavyweight orchestration frameworks. It abstracts agents as first-class objects with typed handoffs, tool registries, and structured output handling, while staying thin enough to understand in an afternoon. The framework leans heavily on Python type hints and function decorators rather than XML configs or complex DAGs, making it feel closer to writing ordinary Python than setting up a workflow engine. Agent handoffs are explicit — you define which agent can delegate to which, under what conditions — giving you audit trails that many competitors lack. The SDK also integrates natively with the OpenAI models API, including structured output models and the function calling spec. The repo is trending today with 625 new stars, reflecting that despite dozens of agent frameworks in the ecosystem, developers keep returning to official, well-maintained options with clear upgrade paths. For teams building on GPT-5 and OpenAI's infrastructure, this is likely to become the default starting point.