AI tool comparison
botctl vs DOOM MCP
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Developer Tools
botctl
A process manager for persistent autonomous AI agents — like systemd for bots
75%
Panel ship
—
Community
Free
Entry
botctl is a Go-based CLI/TUI/web process manager purpose-built for running and orchestrating persistent autonomous AI agents. Where most AI tooling focuses on one-shot completions, botctl is designed for bots that need to keep running — sleeping, waking on schedule, resuming after a pause, and persisting memory across sessions. Bots are defined as BOT.md files: a YAML frontmatter block sets the configuration (schedule, skills, memory settings, log retention), and the markdown body is the system prompt. This declarative format makes bots versionable, shareable, and auditable. A built-in skills system lets bots tap into extended capabilities, and the session persistence layer means a bot can pick up exactly where it left off after a restart or pause. The tooling stack is pragmatic: a terminal TUI for local oversight, a web dashboard for remote access, and a clean REST API for integration. With just 25 GitHub stars as of April 9, botctl is deeply indie — the kind of tool that gets discovered by a few hundred developers and quietly becomes infrastructure for serious builders.
Developer Tools
DOOM MCP
Play DOOM inline inside Claude or ChatGPT — full game, no browser needed
75%
Panel ship
—
Community
Free
Entry
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.
Reviewer scorecard
“This fills a real gap. Running AI agents as persistent processes with proper lifecycle management — sleep, pause, resume, memory — is something every serious builder eventually cobbles together themselves. botctl gives you that scaffolding out of the box. The BOT.md format is a genuinely clever design choice: your bot is just a file you can git commit.”
“The signed-token progressive enhancement pattern is the part worth stealing. This is a clean reference architecture for MCP interactive apps, and DOOM just happens to be the demo case.”
“25 stars and v0.3.5 with no public adoption story. The concept is sound but the execution is completely unproven at scale. Most teams running serious agent workloads are building on Kubernetes or Modal, not a Go CLI from a solo dev. Check back when there's a community behind it.”
“Fun proof of concept but let's be honest: if your AI assistant is hosting a DOOM session, something has gone wrong with your productivity. The MCP-as-interactive-surface insight is real, but this specific app has no utility.”
“The future of software is armies of persistent agents running 24/7, each with a job and a memory. botctl is betting on that future early. The BOT.md format could become a community standard for sharing and distributing agent definitions — like Dockerfiles but for AI workers.”
“Every major compute platform's pivot point is when it runs DOOM. MCP running DOOM means MCP is a real platform now. The implications for interactive AI-embedded experiences are significant.”
“The idea of defining a bot as a markdown file with YAML frontmatter is elegant and approachable. It's the same mental model as a blog post or documentation page — creators who aren't full-time engineers can understand and modify it. That lowers the barrier to deploying personal automation agents considerably.”
“As someone who thinks about interactive experiences, the idea of game-like UI living inside an AI context is genuinely exciting. This is a crude ancestor of what interactive AI-native media could become.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.