Detailed Analysis
A Reddit post detailing "Broken Oath," a massively multiplayer strategy game inspired by Civilization and Europa Universalis, offers a window into how individual developers are now using Claude Code to build ambitious, long-running software projects with minimal direct hand-coding. The developer describes a hex-based 4X game featuring vassalization mechanics—where conquered players don't lose but instead become tributaries who can rebel or coordinate uprisings—alongside diplomacy, alliance systems, and an unusual "god player" role that lets participants strike bargains with rulers, such as building temples in exchange for battlefield favor. The technical stack is notable: Elixir, Phoenix, and LiveView for the backend, with the game board rendered entirely in 3D CSS so it runs in any browser or on mobile devices without a native client.
What stands out most is the development methodology rather than the game design itself. The author explicitly frames Claude Code as an autonomous build engine paired with a tool called CodeMySpec, describing a workflow where they hand off requirements and the "harness" builds the game over subsequent weeks with limited supervision. This reflects a broader shift in how solo developers and small teams are approaching AI-assisted coding in 2025-2026: rather than using Claude as a line-by-line autocomplete tool, they're treating it as a semi-autonomous engineering collaborator capable of sustained, multi-day project execution against a specification. The choice of Elixir/Phoenix/LiveView is also telling—these are technologies well-suited to real-time, stateful multiplayer applications, and the developer notes that their "harness" has strong browser-testing facilities, suggesting the agentic workflow includes automated verification loops (build, test, render-check) rather than blind code generation.
This kind of project matters as a data point in the ongoing conversation about AI coding agents' capability ceiling. Building a persistent multiplayer strategy game with complex turn-based state management, diplomacy systems, and real-time synchronization is a substantially harder engineering problem than typical demo apps or CRUD tools that dominate "built with Claude" showcases. The fact that a single developer is attempting this with Claude Code as the primary build mechanism—posting a live tech demo on day zero—illustrates growing confidence that agentic coding tools can handle non-trivial architecture, not just boilerplate. It also reflects the emergence of an ecosystem of meta-tools (like CodeMySpec) designed specifically to structure and constrain AI coding agents' output through specifications, indicating that effective use of Claude Code increasingly depends on scaffolding and process design as much as prompting.
More broadly, posts like this are part of a wave of "build in public" content on communities like r/ClaudeAI, where developers document AI-assisted projects in near real-time, normalizing the idea that ambitious solo software projects—game engines, multiplayer backends, simulation systems—are increasingly tractable for individuals rather than requiring dedicated teams. Whether Broken Oath ships as a polished, sustainable multiplayer game remains an open question, since MMO-style games are notoriously difficult to balance and scale even with full teams, but the project serves as an early signal of how far delegated, agentic software development has progressed and where its practical limits might still lie.
Read original article →