Software shaped to you,
built by an agent,
on demand.
Traditional frameworks give humans abstractions to write code against. Claudepanion inverts that — it gives the agent a scaffold and lets it build the software itself. You describe what you want. Claude fills in the rest. A localhost host for personal companions, with Claude Code as the runtime backend.
~/projects/claudepanion
$ git clone github.com/sean1588/claudepanion
$ cd claudepanion && npm install
$ npm start # → http://localhost:3001
✓ host running
✓ build companion mounted
# now open Claude Code in any repo and type:
› /build-companion ▍
§01 · SharingThe registry is
The registry is
npm. We didn't
build one.
A companion is just a set of exports following a stable contract. Source it from a folder. Source it from npm. Same contract.
npm is already globally replicated, versioned, permissioned, and familiar. Private packages? Already work. Org-scoped? Already work. We just reserved the prefix.
Local
companions/<name>/
your hand-written or Build-scaffolded ones
Published
claudepanion-<name>
drop-in from the npm registry
Official
@claudepanion/<name>
scoped, blessed, curated
§02 · FAQThings people
Things people
actually ask.
01 Is this a SaaS? +
No. It's a localhost host. One process, one URL, one user. Your companions and their data live on your machine.
02 What is a 'companion,' exactly? +
A small personal app inside the host. It has a form, a slash command, a Claude Code skill, and a set of MCP tools that proxy to external systems. Think: PR reviewer, on-call investigator, reading tracker.
03 Do I have to use Claude? +
Yes — and intentionally so. The primitives (MCP, slash commands, skills) assume Claude Code is the runtime. Companions can run without invoking Claude, but that's a side door, not a feature.
04 How is this different from Claude Code with extra steps? +
Persistence across sessions. Visual artifacts (tables, dashboards, live logs). Ambient presence — a tab that stays open. Authenticated proxy tools so Claude can hit your AWS / GitHub / Linear without you pasting credentials.
05 Where do shared companions live? +
On npm. Anything published as claudepanion-<name> drops into your sidebar after one install. We don't run a registry — npm already does that job.
06 Is it production-ready? +
No, and intentionally so. It's for an audience of one — you. The bar is 'works for the next two weeks,' not 'serves a million users.'
Bring an idea.
Claude builds it.
Run it locally. Throw it away when you're done. Or don't.
View on GitHub