<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Ben Croughs</title>
    <description>The latest articles on DEV Community by Ben Croughs (@bc3).</description>
    <link>https://dev.to/bc3</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4250195%2F796c8422-41a9-4e4b-b692-bd180b167fd3.jpg</url>
      <title>DEV Community: Ben Croughs</title>
      <link>https://dev.to/bc3</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/bc3"/>
    <language>en</language>
    <item>
      <title>Why I rendered my Claude Code projects as a medieval kingdom</title>
      <dc:creator>Ben Croughs</dc:creator>
      <pubDate>Tue, 17 Nov 2026 16:36:17 +0000</pubDate>
      <link>https://dev.to/bc3/why-i-rendered-my-claude-code-projects-as-a-medieval-kingdom-4ki2</link>
      <guid>https://dev.to/bc3/why-i-rendered-my-claude-code-projects-as-a-medieval-kingdom-4ki2</guid>
      <description>&lt;p&gt;I have five Claude Code sessions running right now. One is refactoring an auth module, one is stuck waiting on a test I forgot to write, one finished twenty minutes ago and I haven't noticed, and I genuinely cannot tell you the state of the other two without tabbing through five terminal windows.&lt;/p&gt;

&lt;p&gt;That's the actual problem &lt;code&gt;sir-claude&lt;/code&gt; is trying to solve, and it's the reason the solution ended up looking like a medieval kingdom instead of a dashboard.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem: parallel agents, serial attention
&lt;/h2&gt;

&lt;p&gt;Claude Code is great at running several projects at once — spin up a terminal per repo, kick off a session, move on. The failure mode isn't the agent, it's you. Terminal tabs all look the same. A title bar doesn't tell you "this one needs a decision" versus "this one is still happily chugging through a migration." So you end up doing the thing humans are bad at: periodically re-checking N identical-looking windows to guess which ones matter right now.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why a spatial metaphor actually helps here
&lt;/h2&gt;

&lt;p&gt;A status dashboard with five rows of green/yellow/red text solves the same problem on paper, but it doesn't solve it in practice — rows of text all compete for the same kind of attention, which means you still have to &lt;em&gt;read&lt;/em&gt; every row to know what's going on.&lt;/p&gt;

&lt;p&gt;Spatial memory doesn't work that way. If "the auth project" is a specific building in a specific corner of a 3D scene, you don't need to read anything to know something changed there — you see a building get bigger, catch fire, or light up at the edge of your vision. That's the bet behind &lt;code&gt;sir-claude&lt;/code&gt;: render each of your Claude Code project folders as a building in a small Warcraft II–style medieval kingdom, and let activity, status, and size do the reporting instead of text.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Size&lt;/strong&gt; = how active the project is — more recent commits/tool calls, bigger building.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Color&lt;/strong&gt; = status — healthy, waiting on you, stuck, done.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Day/night cycle&lt;/strong&gt; = ambient sense of how long things have been running, so a session that's been going all "day" reads differently than one that just started.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It's a goofy premise on the surface, but it's the same instinct behind why pilots use dials instead of a column of numbers — ambient, peripheral information beats information you have to actively go read.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it's built
&lt;/h2&gt;

&lt;p&gt;Under the hood it's a lot less magical than "medieval kingdom" makes it sound:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A &lt;strong&gt;three.js scene&lt;/strong&gt; renders one building per project folder. Each building is a self-contained mesh that reacts to a small state object (&lt;code&gt;activity&lt;/code&gt;, &lt;code&gt;status&lt;/code&gt;, &lt;code&gt;lastEvent&lt;/code&gt;) rather than owning any logic itself — the kingdom is a rendering layer, not where decisions happen.&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;status → color/size mapping&lt;/strong&gt; watches each project's Claude Code session and translates recent activity into the visual state above. This is the part that actually matters; the 3D is just the output.&lt;/li&gt;
&lt;li&gt;Clicking a building drops you into a &lt;strong&gt;per-project terminal plus a readable, parsed view of the Claude session history&lt;/strong&gt; for that project — so the game layer is a map, not a replacement for the real interface. You zoom out to see the kingdom, zoom in to actually work.&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;"Spellbook"&lt;/strong&gt; sits alongside each project for saved commands and scheduled jobs — the stuff you re-run often enough that typing it out each time is friction.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;"Conjure"&lt;/strong&gt; is a natural-language-to-command layer: describe what you want in plain English, it proposes the actual command, you confirm before it runs. Keeps you in control without needing to remember exact flags.&lt;/li&gt;
&lt;li&gt;Offline &lt;strong&gt;voice control&lt;/strong&gt; via &lt;code&gt;whisper.cpp&lt;/code&gt; for speech-to-text and Kokoro for TTS — no cloud dependency, no account, works the same on a plane as it does on your desk.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Telegram remote control&lt;/strong&gt;, for checking on or nudging a session from your phone when you're away from the kingdom entirely.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of this needs a server. No signup, no cloud dependency to run it — it's a local tool that happens to render its status screen as a game.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's next
&lt;/h2&gt;

&lt;p&gt;Two things I'm actively building toward:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Proving Grounds&lt;/strong&gt; — an LLM-vs-LLM arena inside the same kingdom, for comparing how different models/agents handle the same task instead of just trusting vibes.&lt;/li&gt;
&lt;li&gt;Deeper &lt;strong&gt;voice control&lt;/strong&gt; — right now it's functional; the goal is for it to be the default way you check in on a running session, not a novelty feature.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx sir-claude
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;No install step, no account, no cloud dependency — it just runs against whatever Claude Code projects you already have locally.&lt;/p&gt;

&lt;p&gt;The project itself is closed-source for now. If you want access to the source on GitHub, the easiest way in is to DM &lt;a href="https://instagram.com/sirclaude.dev" rel="noopener noreferrer"&gt;@sirclaude.dev&lt;/a&gt; on Instagram, connect via GitHub, or email &lt;a href="mailto:ben.croughs@telenet.be"&gt;ben.croughs@telenet.be&lt;/a&gt; — happy to talk through it.&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>javascript</category>
      <category>ai</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
