Switchboard : the control tower Claude Code never needed ?

The problem is real: the silent proliferation of your sessions

At first, Claude Code keeps its promise. A command line, an instruction, code. No bloated IDE, no windows to tame, sobriety as a method. Then the weeks go by, and another regime quietly takes hold. The ~/.claude/projects folder swells without a sound. Terminals multiply in the background, each with its own session, its own context, its own half-abandoned train of thought. And then comes the gesture we all end up knowing: typing /resume blind, hoping to land back on the right conversation among the dozen opened this week.

I’ve already dissected the persistent memory of Anthropic’s agent here, and the amnesia that stalks it the moment you cross the limits of the context window. Switchboard doesn’t tackle that problem. It aims one floor up: no longer the forgetting inside a single session, but the loss of the thread between them. Where Understand-Anything tries to give a project its memory back, Switchboard claims to give a map back to the whole of your activity. Without it, the history becomes a black box, a graveyard of context files where the engineering effort dissolves for lack of any way to retrace it.

What Switchboard does, without the marketing varnish

Let’s look at the tool coldly, stripped of the control-center vocabulary already being pinned on it. Switchboard is an Electron wrapper, and it makes no secret of it. Under the hood, the usual rig for this kind of application: node-pty to encapsulate the terminal, better-sqlite3 for a fast local cache, CodeMirror for text editing. Its primary function fits in one sentence: read your ~/.claude/projects folder and make it legible.

Without going into raptures, here’s what the current version offers, each entry serving a precise purpose:

• A session browser sorted by project, so you can see at a glance where you stand.
• A full-text search that digs through the content of the exchanges, not just their date.
• An integrated terminal to resume or launch a session without leaving the application.
• A fork & resume that clones a session and sets off again from any point in the history without polluting the main thread.
• An editor to work directly on your CLAUDE.md files and your build plans.
• An activity heatmap, backed by the automatic recovery of session names via the native /rename command.

This search looks like nothing, and yet it alone justifies the install. Last week, in eight seconds, I got my hands back on the complete reasoning behind a CSS 404 workaround under WooCommerce, carried out three weeks earlier and already gone from my head. No blind /resume would have done me that favor; I’d have had to reopen the sessions one by one until, by luck, I stumbled on the right one.

One point deserves pausing on, because it governs everything else. Switchboard is not a multi-agent orchestrator. It doesn’t run ten instances in parallel to make them collaborate, contrary to the fashion of the moment. It’s an archivist. A browser for sessions already played out. It dreams of being the historian of your terminal, not its conductor, and its entire ambition boils down to making a chronology intelligible. Hold on to the distinction: it alone decides whether the tool occupies a real place or is just one more duplicate.

The underlying contradiction: an Electron factory to discipline the CLI

This is where the trajectory turns comical. The whole appeal of Claude Code rested on a radical stance: throw out the graphical wrapping, flee the gas factories of overloaded IDEs, return to the bare command line. Speed, lightness, minimal friction. And what does Switchboard offer to repair the collateral damage of that very approach? A graphical interface. A greedy Electron application running permanently in the background, with its footprint of several hundred megabytes, to keep watch over a tool whose foremost merit was to weigh nothing.

We know the tune. It’s the reflex I was already pointing at when faced with the Docker, Kubernetes and assorted stack, or with vibe coding, where the software overlay always comes to mask a flaw in method rather than fix it. Disciplining the terminal with pixels means treating the symptom, the scattering, without ever touching the cause, which is the absence of hygiene in how sessions are run. Switchboard makes the disorder comfortable. It doesn’t remove it. And that’s a nuance I was already recalling when I wondered whether Claude Code went far enough: adding a layer has never been worth fixing a foundation.

An already crowded category, and a new 3-star entrant

To avoid the cozy puff piece, let’s map the terrain. In a few months, the market for Claude Code session managers has thickened to the point of forming its own chapels:

• Opcode, the open-source pioneer that defined the genre. Now left to rot, it offers the perfect illustration of the sudden death that stalks the peripheral tools of AI.
• Claude Squad, around 5,800 stars on GitHub, resolutely terminal-based, geared toward multi-agent work and parallel execution.
• Nimbalyst, a full commercial visual suite, carried by a founder who passed through Salesforce, aiming squarely at the enterprise.
• Claude Code Desktop, Anthropic’s official answer, natively integrated into its own ecosystem.

If this category filled up at such speed, it isn’t the sign of a massive need, it’s the sign of an easy one. Wrapping a CLI in an Electron shell costs almost nothing: the bricks are off the shelf (node-pty, SQLite, a web editor), the technical barrier is laughable, and the hype around Claude Code guarantees an instant audience to anyone who slaps an interface in front of it. The density of the market doesn’t measure demand, it measures the price of entry.

In the middle of this pack, Switchboard moves along at version 0.0.5, with four releases and a counter frozen at three stars. The question is a fair one: what does it bring that the others don’t cover? Perhaps its very frugality, and that position of sober historian while everyone else races toward orchestration. Whether this niche really exists, or whether it ends up crushed between the dying pioneer and the commercial steamroller, remains to be seen.

One symptom is worth flagging in passing. The swarm of “Best Claude Code session manager 2026” articles already saturating the search results says nothing about the actual quality of the tools. Above all, it betrays an SEO content-marketing machine that pounced on a still deeply immature ecosystem, manufacturing comparisons before the category had even proven itself.

The detail that says it all: Claude appears among the contributors

There is, in the Switchboard repository, a detail that tells you more than the entire documentation. In the list of contributors, beside the two human maintainers, sits a third name: Claude. The model is credited as the author of commits.

Let’s stop there for a second. A tool designed to frame the use of Claude Code is, in part, co-written by the very model it’s meant to frame. The AI builds the interface of its own surveillance. It codes the walls of the room where we claim to watch it work. Beyond the anecdote, the question is a serious one for the future of our trades: what remains of open-source craftsmanship when the author, the reviewer and the maintainer share the same synaptic weights? It’s the direct continuation of what I noted about Anthropic’s HTML manifesto. The machine no longer settles for producing code, it now produces the tools that produce the code.

Verdict: for whom, for what, and at what risk

So, should you install Switchboard? You won’t get an enthusiastic recommendation out of me.

The tool makes sense for one clear profile: the high-throughput developer, juggling dozens of micro-projects and spending his days trying to exhume a fragment of reasoning buried at the bottom of some forgotten terminal. For him, full-text search over content is probably worth its two hundred megabytes of memory. If, on the other hand, your workflow is rigorous, your projects compartmentalized and your contexts cleaned up as you go, Switchboard will remain a perfectly superfluous layer. You don’t need a map for a territory you know by heart.

That leaves the maturity risk, which has to be owned without dodging. At version 0.0.5, a project born on a Monday can be dead by Friday, and no one should build a critical workflow on three GitHub stars. But that’s precisely where Switchboard becomes interesting: not for what it will be in six months, but for what its existence says today. We’ve handed the writing of code over to the machine, and here we already are, demanding a dashboard to take back, with our eyes at least, control of what it produces in our name. Switchboard isn’t a revolution. It’s a symptom. And symptoms, for their part, always deserve a closer examination.