01Listen
It reads the channels it's invited to and picks out the people, projects, decisions and customers in them.
How it works
Living Brain reads your team's conversations, writes what it learns as a Markdown wiki with sources, and keeps that wiki true. Parts of it run today: sessions sync from the Mac app, facts carry dates, and dreaming tidies them. The chat and mail flows are planned, and the examples are sample data.
Speaks up
Living Brain listens in the team chat channels you invite it to, in Slack or Discord. When a question already has an answer, it replies in the thread and links to the exact message the answer came from.
Rolling back #412. The 502s on /api/routes come from the new pool config.
is prod down? Northwind says routes won't load
Not down. routes-api returned 502s from 09:38 to 09:52 after deploy #412. Dev rolled it back at 09:51 and error rates have been normal since.
It reads the channels it's invited to and picks out the people, projects, decisions and customers in them.
Conversations become Markdown pages with [[backlinks]]. Every fact cites the message it came from.
On its own schedule it merges duplicates, flags contradictions, retires stale facts and rewrites summaries.
Every night the brain revisits what it knows.
Dreaming is live: a background pass reviews each subject's facts, and ends, supersedes, retracts or renames the outdated ones while keeping the history. How it works. Merging duplicate pages and flagging contradictions are planned.
While the team is offline it reads what happened, tidies what it knows and hands work to agents. It also scans new research papers, news and releases about your stack, and notes how they could apply to your projects. By morning there's a digest waiting.
Sample dataacross 9 channels
billing.md folded into billing-v2.md, and 3 more
Billing v2 ship date, PG16 window, Bluepeak contact
"Set routes-api pool size back to 20", waiting for Dev's review
emailed to 12 people, each in the format they prefer
See how it thinks
This is Kestrel Freight, a fictional 20-person logistics company. Drag to orbit, scroll or pinch to zoom, and click any node to open its page.
Static view · click a node or use the list below
Opens the issue, reads the PR, sends the email digest, and hands bigger jobs to a sandboxed agent that returns a pull request. How that works
The learning layer notices how each person likes answers, short or detailed, in threads or DMs, and adapts week by week, so its answers improve every week. It learns from agent sessions too
You own it
Read it, edit it, version it, move it. Your knowledge isn't locked in a black-box vector store. The Living Brain GitHub App already reads a connected repository's commits, issues and pull requests into the brain. Keeping the wiki in your git repo, with the app proposing every change as a pull request that flows back when you merge it, is planned.
Each line is scaled to its own total. The graph above fills in as the chart plays.