Local-first memory atlas · DSH plugin

Your memories,
as a sky.

A read-only nebula for every store on this machine — meow-memory, OpenViking, notes, SQLite. See what connects, follow the evidence, and hand someone one file instead of your whole life.

20k memories supported 0 bytes uploaded MIT licensed
Memory Nebula showing 2,062 memories and 10,027 connections across nine workspaces
in the live library10,027connections, one sky
evidence chain1 hoptwo nodes, one reason
local only127.0.0.1no account, no cloud
The point

A graph is only useful
when it can answer why.

Most memory tools give you a list and a search box. This one gives you the shape: which memories keep appearing together, which project they belong to, and what evidence made the link.

01

Recall that spreads

Start from a word, then walk outward along real edges. Every hit carries its path, its workspace, and the reason it surfaced.

02

Evidence you can stand on

Click two blobs and get the shortest chain: shared entity, same project, a session where they were both used. No invented links.

03

A slice you can hand over

Export one workspace, one project, or two hops around a node as a single HTML file. Text, styles and search all travel with it.

Demo galaxy with a highlighted evidence path between two memories
↳ shared entity · confidence 0.92 · 1 hop
What is inside

Small surface,
deep map.

No daemon to babysit, no account to create. A plugin inside DSH, or a standalone engine on loopback when you want the CLI.

Search / recall

Search is a seed, not a filter.

Type one word. The map returns direct hits, then the neighbours they activate, with a budget so a common word cannot flood the page.

Snapshots

One file. Zero network.

A whole graph or one slice becomes a self-contained HTML file. Open it on a plane, send it to a client; it still searches and draws evidence locally.

Boundary

Private by default. Honest about exports.

Every store opens read-only. Writes stay in $DSH_HOME/memory-nebula. The only way text leaves is the export you ask for.

Scale
20,000nodes · 2.53s

Entity pairing gets a budget above 12k nodes, candidate scoring stops allocating strings. Ten thousand stays at 1.2s; twenty thousand fits in a 3s build and 248MB heap.

Operations

A doctor that speaks first.

Nine read-only checks: Node version, package files, profile wiring, bundled version, sources, endpoint, and version drift. If a blank page is a restart problem, it says so.

CLI / CI

A CLI for the rest of us.

--share, --export, --scope, --token, --diagnose. Build a snapshot in CI, gate a release on 126 tests, or diagnose a customer without touching their memory text.

Keyboard / screen reader

Playable without a mouse.

Tab into the map and arrow keys walk between stars by spatial direction; [ ] follow edges, + - zoom, 0 returns to the full map and Home jumps to the busiest star. Every move is announced through aria-live, and a plain-text index lists all N memories for screen readers — the canvases stay out of the accessibility tree instead of pretending to be images.

Screens

Real pixels,
not mockups.

Captured from the live catalog: the English interface, the demo galaxy, and the 20k offline snapshot.

English memory nebula with 2,062 memories
01 · The whole sky2,062 memories · 10,027 links
Demo galaxy with a selected memory and its neighbours
02 · A selected memorydemo galaxy · evidence visible
Offline snapshot of the nebula
03 · Offline snapshotone file · no network
20,000 node benchmark snapshot
04 · 20k nodes2.53s build · 248MB heap
Install

Three commands
and a look.

Install from the curated catalog, open the page inside DSH, and run the doctor only if something looks empty. No build step, no database migration, no account.

dsh plugin --profile web add dsh-memory-nebula
npm install dsh-memory-nebula@latest

Just looking? npx -y -p dsh-memory-nebula memory-nebula --demo starts the built-in demo on 127.0.0.1:7891.

$ dsh plugin --profile web add dsh-memory-nebula
✓ resolved dsh-memory-nebula@1.7.0
✓ profile web · bundle enabled
restart DSH to load the new host code
$ node scripts/doctor.mjs
[ok] runtime Node 24.17.0
[ok] sources 9 memory stores
[ok] endpoint 1.7.0 · standalone
summary: 9 passed / 0 warnings / 0 failed
$ memory-nebula --share ./nebula.html --scope ws:design
wrote ./nebula.html · 398 KB · 174 ms
The boundary

What it does.
What it refuses.

This is a viewer, not a sync service. The limits are part of the design, not a roadmap promise.

  • Reads only. Every adapter opens its store read-only; the plugin writes only to its own directory.
  • Loopback only. Host and Origin are pinned; a DNS-rebinding request gets 403 before it reaches memory.
  • No account system. Standalone can add an optional local token; without it, the model is one local user on one machine.
  • Exports are plaintext. A snapshot contains the text in its scope. Treat it like a backup, because that is what it is.
  • No cloud, no telemetry. There is no upload path, no analytics key, and no “sign in to continue”.