LARARIUM
The empty cathedral.
You bring the life.
Star on GitHub
No signup. No dashboard. The command is the whole product.

ChatGPT forgets you the moment you close the tab. Lararium is an assistant that is actually yours.

It lives on your machine. It remembers everything you tell it. You own every file. You are not renting a chatbot from a company that keeps your data. You are keeping one that keeps yours.

What gets built
I · brain
Plain markdown files it reads and writes as you work. You can open them. You own them.
II · soul
Who your assistant is. You write the voice, the opinions, the things it refuses to do.
III · index
Search across everything you have fed it. It surfaces the thing you forgot you saved.
IV · agents
A bench of specialists you call by name. One builds, one reviews, one digs.
V · hooks
The wiring that makes it remember yesterday.
VI · skills
Teach it something once. It keeps it.
The install is a conversation

You do not configure it. You talk to it.

It interviews you and writes the files itself. You answer a few questions like a human. It builds the niche around what you say.

lararium · setup
$ npx lararium
◦ preparing your niche
what should I call your assistant?
Vesta
what do you spend your days thinking about?
distributed systems. and my kid.
+ wrote  ~/.lararium/soul/persona.md
+ wrote  ~/.lararium/brain/threads/
+ indexed  0 files. it starts empty.
your lararium is ready.
The lab

Run other people's code without betting your machine.

Your assistant is most useful when it can clone and run a stranger's repo. That is also when it is most dangerous. So the stack ships a disposable sandbox: no network by default, nothing of yours mounted in, every privilege dropped, gone the second you exit. Say /in-the-lab and it vets the code in the box before it touches your machine.

And yes, we noticed: telling a security-minded developer to npx a stranger's installer is rich, coming from us. So don't. The scaffolder is about 200 lines of Node standard library, zero dependencies. It downloads a release and unpacks it, and runs none of the template's own code. Read it first, or clone by hand and inspect everything. Properly paranoid? Let the lab's first job be auditing Lararium itself.

lararium · lab
$ lab https://github.com/someone/repo
🔒 offline · nothing of yours mounted
reaches for network / shell / eval
postinstall: curl … | sh
dependency tree
312 packages nobody read
contained. exit and it is gone.
Agent-native

Hand the whole thing to your agent.

Lararium is markdown all the way down, so the entire methodology fits in one file: what it is, how it installs, the reasoning behind every layer. Download it, drop it into your own assistant, and let it figure out what to build for you. You do not even have to read it. That is its job.

↓  Download the methodology view raw ↗
One file. Give it to any AI. It knows what to do with it.
It gets sharper over time

The index watches for connections. When a note you saved months ago hits what you are stuck on today, it tells you. Once, quietly, not a notification storm.

Lararium · noticed

A note you wrote three weeks ago, "consistency vs. availability," just connected to the doc open in front of you.

Stay in the loop

New capabilities ship often.

Your stack tells you when there is an upgrade. If you want a human heads-up too, leave an email. Optional, and no noise.

Want this built and run for you, not by you? That is what Elorati does.

Bring your own gods.
Documentation ↗ GitHub ↗ npm ↗
An Elorati project MIT · MMXXVI