v1.3.0 — Norn Live

v1.3.0 — Norn Live

@samad001z/norn-core@1.3.0 · @samad001z/norn-server@1.3.0 — both on npm. The
npx one-liner picks this up automatically on next launch; no config changes needed.

Norn Live: watch agents use memory

The dashboard has a new page, /app/live: a real-time feed of every remember,
recall, and forget your agents perform through Norn — who acted, when, and a short
preview of what was touched. A needs you panel collects possible conflicts (when
NORN_DETECT_CONFLICTS=1 is on) still waiting for your decision, and clears as you
resolve them in the dashboard. Updates arrive over server-sent events, with automatic
fallback to polling.

Under the hood, core gains an append-only events table in the same local SQLite file
as your memories. Existing stores migrate in place the first time the new version opens
them; nothing leaves your machine.

Attribution is opt-in: pass the new agentId tool argument or set NORN_AGENT_ID to
label a session (unlabeled sessions get a generated per-session id), and set
NORN_MODEL to tag events with a model.

Honest limits: only Norn's own tools are logged — it's not a session recorder, and
plain list calls are deliberately excluded. Logging is best-effort: a failed event
write never blocks a memory write, so treat the feed as a trace, not an audit record.
The log has no retention cap yet (pruning is on the roadmap).

Fixes

• The dashboard no longer seeds demo data. Previous versions silently wrote eight
  fabricated example memories into an empty store on first open — the same store your
  agent reads. It no longer writes anything you didn't ask for; empty stores stay empty.
  If you saw those seeds, they're ordinary memories: forget them from the dashboard.
• A local production build of the dashboard now works with zero config. Hosted mode
  (the empty read-only preview) used to trigger on NODE_ENV=production, so a local
  next build && next start showed an empty dashboard unless you knew to set
  NORN_DASHBOARD_LOCAL=1. Hosted mode is now an explicit signal only: VERCEL (set by
  the platform) or NORN_DASHBOARD_HOSTED=1. NORN_DASHBOARD_LOCAL is no longer needed
  and is ignored.

Also

• New test pinning the zero-config promise: the MCP server and the dashboard, launched
  from unrelated directories, resolve to the same global store.
• norn-core gains a simulate script that generates demo activity locally, if you
  want to see the live view move without wiring up an agent.

Compatibility: no breaking API changes. The events table is created automatically
on first open; older servers simply write no events (the live view stays empty until
they upgrade). Dashboard users running from a clone: pull and re-run
npm install && npm run build:core.

Verified before release: installed the published server in a clean environment via the
README one-liner path, saved a memory over MCP, and confirmed the event row lands in the
store and is returned by the same read path the live view uses.