The problem: a team's knowledge is scattered across everyone's screen. Each person talks to Claude Code in one terminal and Codex in another, decides things in Slack, reads docs and joins calls. None of it is shared. To learn where a project stands, you need a meeting, and when someone hands a project over, most of what they knew is lost.
The solution: Lanterns, a shared team memory built on screenpipe. screenpipe sees your screen; Lanterns reads it, along with your Claude Code and Codex conversations, and writes one book organized around your real projects and the people you work with. Every sentence links back to the screen capture or message it came from.
Sharing is the core (Track 3). Hand a project to a teammate in one click: Lanterns already knows who works on it from git and drafts the handoff in seconds: where it stands, what was learned, what is left. You approve every sentence before anything leaves. Your doubts never leave, and emails, numbers and secrets are masked. Your teammate gets a read-only link that opens once, with no account, and their Claude Code can read that page over MCP to pick the project up. Revoke it and it is gone, for them and their agent.
The team page shows who is connected and which project each teammate is on right now, as a lit lantern; only the project name leaves their screen. Your standup writes itself from your day, you approve it, and the team sees it every evening. And "who knows about pricing?" finds the teammate who does, with their exact words.
Nothing leaves your laptop until you approve it.
Lanterns runs locally: a Node.js server in TypeScript and a plain JavaScript web app, with the model you pick (OpenAI, Claude or Tinfoil) for summaries and chat.
screenpipe is the base layer. Every chat question calls /search live, and /frames/:id opens the capture behind an answer. Each project page lists where it appeared on your screen, also from /search. The book is built from /search and screenpipe's SQLite database, and every quote is checked word for word against /frames/:id/context, /text and /elements. App, window and URL light up the project you are on. We write back with /tags/vision and /memories.
Team sharing uses hashed tokens, a sha256-chained access log and encrypted storage. Agents read shares over MCP.