Skip to content

v0.5.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 20:08
· 64 commits to stable since this release

The graph is built in: no Neo4j to run, every install moves on its own, and what one agent learns reaches the others.

Article: https://lifekernl.com/news/0.5.0 (Español: https://lifekernl.com/es/news/0.5.0)

Install or update:

curl -fsSL https://raw.githubusercontent.com/fastslack/kernl/stable/install.sh | sh

Windows: take the .msi below. Homebrew cask updated. Checksums in SHA256SUMS.

Upgrading from 0.4.6

  • The graph is built in now, and your install moves to it on its own. On the first start Kernl switches to Relate, the embedded graph, once:
    • No graph before (the desktop app): Relate is switched on and filled from your SQLite data in the first minute.
    • Neo4j before (Docker): Kernl keeps serving from Neo4j while it copies the graph into Relate in the background, checks the counts, switches over live and then brings over what reached Neo4j during the copy. Neo4j is left exactly as it was; activating it again in /extensions is the way back. If the copy fails, Kernl stays on Neo4j and tries again on the next start.
    • The cinema catalogue stays behind. It was a projection of SQLite that nothing read any more, and ~90% of the graph. On a real install the rest (13k nodes, 7.5k relationships) copied in 7 seconds with a 230 MB peak, instead of 53 minutes and 12 GB.
    • To stay on Neo4j (you use Graph Data Science, say), set KERNL_KEEP_NEO4J=1. KERNL_GRAPH_UPGRADE=off skips the step.
  • Docker: update with scripts/kernl.sh update. Leave Neo4j running until the log says Graph upgrade: caught up with what reached Neo4j during the copy; then scripts/kernl.sh stop neo4j is safe and the data stays in its volume.
  • Back up the built-in graph by hand for now. backup.sh copies the database but not data/graph, where chat memory, contact links and the news archive live. docs/DEPLOYMENT.md shows how.
  • Bundled extensions that changed carry a new version (Cinema 1.38.0 and nine others one patch up), so a copy in the extensions folder takes the new code.
  • Migrations run on start (agents 64, cinema 22, and the graph's schema upgrade). Nothing to do by hand.

Added

  • Agents learn from each other. Runs, the tools they used and the lessons drawn from them form a shared experience graph; an agent's prompt now carries other agents' lessons that fit its goal, as untrusted data. Every change in what an agent knows is recorded and announced.
  • Office packs. Export an office's lessons as a file, with emails, phones, tokens and home paths blanked; importing one stages its lessons for review.
  • Agents' decisions are remembered and measured. Each answer records who gave it and through which channel. A question that keeps getting the same answer shows it as a suggestion, and an office can let a category answer itself once it has been right at least 97% of 30 times, where an extension says it is safe; one in ten still goes to a person.
  • Environment facts. A shared outside cause (a server down, a missing credential) is recorded once; blocked agents wait on it and wake when it closes.
  • Facts with two timelines. When each fact was true and when Kernl believed it; nothing is deleted. kernel_facts_explain answers why Kernl acted and what it knew then, and the time machine shows it for a person, company or agent at any moment.
  • kernel_brain_ask: one question over every memory — brain, chat, lessons and the graph — by meaning and by words.
  • One person across every source. Contacts keep every address and handle they are known by; duplicates are found and merged with a snapshot, and a 360 view gathers everything about a person.
  • Provenance. Every write records who made it and whether it worked; kernel_audit_who_changed answers for any id.
  • Agents read the graph. Schema, checked read-only Cypher and questions in plain words; private scratch graphs per run; outside MCP clients never see mail, chat memory or facts by default.
  • Graph analytics on any engine: PageRank, communities, components and betweenness, with GDS when there is one and plain TypeScript otherwise.
  • See the graph. A 3D graph explorer, the engine room (the graph at work, with the engine's own timing), and what the offices learned: each lesson's impact, a library by week and a constellation by meaning.
  • Code graph for repos (hotspots, owners, change impact from git history) and places (where events, trips and hotels are, and what is near).

Fixed

  • The Docker image builds on ARM again (Graviton, Raspberry Pi, Docker on Apple Silicon).
  • A slow graph read no longer stalls the kernel: Relate runs one writer and a few readers (a lookup behind a 3 s read went from 3 s to 2 ms).
  • Chat with Claude Code moves to the next connected account at a usage limit, and to the rest of the model chain when every account is out.
  • Relate's memory limit is actually applied.
  • LIMIT/SKIP parameters reach Neo4j as integers.
  • AGENTS_SCHEDULER=off also stops the inbox sweep.

Full Changelog: v0.4.6...v0.5.0

Full Changelog: v0.4.6...v0.5.0