Kernl
Watch your AI go to work.
Give any compatible AI your real context — then run observable agent teams that plan, collaborate and finish the work on your hardware.
curl -fsSL https://lifekernl.com/install.sh | sh
Free · Apache-2.0 · No telemetry · No accounts
Verify the script's integrity before running it:
curl -fsSL -O https://lifekernl.com/install.sh
curl -fsSL https://lifekernl.com/install.sh.sha256 | sha256sum -c -
sh ./install.sh
Your entire life, one kernel.
Every module is an MCP tool. Each one is optional, hot-swappable, and runs locally against your SQLite database.
See it in action.
The 3D agents office, Kernl TV, the planner and live world data — real captures, not mockups.
One server. Every AI sees it.
Kernl speaks the Model Context Protocol over both stdio and Streamable HTTP. Any MCP-capable client connects to the same set of tools.
Your AI clients
Kernl
Your stuff
{
"mcpServers": {
"mtw-kernel": {
"command": "bun",
"args": ["run", "bin/mcp-server.ts"],
"cwd": "/path/to/Kernl"
}
}
}
{
"mcpServers": {
"mtw-kernel": {
"type": "streamable-http",
"url": "http://localhost:3086/mcp"
}
}
}
# Streamable HTTP transport (official MCP spec) curl -X POST http://localhost:3086/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Install in one line.
Detects your OS, downloads the right package, and opens the dashboard.
Latest v0.2.6 changelog checksums
curl -fsSL https://lifekernl.com/install.sh | shcurl -fsSL https://lifekernl.com/install.sh | shsudo apt install ./kernl_*.debsudo dnf install ./kernl-*.rpmirm https://lifekernl.com/install.ps1 | iexgit clone https://github.com/fastslack/kernl
cd Kernl
cp .env.example .env
docker compose up -d --buildRuns kernel + dashboard + Neo4j + WhatsApp bridge. Dashboard at http://localhost:3086.
After install, the dashboard opens at http://localhost:3086 and walks you through a four-step setup — language, then your LLM: a cloud key, or a local model through LM Studio or Ollama if you would rather nothing left the machine. Everything stays editable afterwards in Settings, or in ~/.config/kernl/.env.
Why run it yourself?
Privacy by default
Your tasks, contacts, finance, health data — all in a SQLite file on your machine. Nothing leaves unless you tell it to.
Extensible by design
Every module is a plugin. Drop a .kernl bundle in, or write your own — same MCP surface.
Fast & light
Bun runtime, statically linked. Starts in a couple of seconds. ~320 MB installed — the runtime and native modules ship with it, so there is nothing else to install.
Truly open
Apache-2.0. Audit every line, run it forever, keep it even if we disappear — no licence server, no kill switch.
Local-first LLMs
LM Studio and Ollama work out of the box. Run agents on your own GPU.
Federated, not centralized
Mesh with other instances over the Matware mesh protocol. Your phone, your laptop, your VPS — same kernel.
Ready to take your life off the cloud?
Get launch updates.
No spam. One email when a new release ships, another when new modules land.
One email per release. No drip sequence, no upsells.