Alpha

Persistent
memory for
Claude Code

Your AI coding sessions remember everything. Context, learnings, preferences — carried across every conversation.

mull session
$claude
[mull]Starting session a3f8c2d1
[mull]Loading memory blocks...
847 learnings·23 tasks·12 projects
Worktree ~/active/mull-feature
───
>
From your learnings: this project uses color-eyre
and prefers eyre::Result over anyhow...
Persistent MemorySession IsolationBackground AgentsTask TrackingPR IntegrationDaily LogsGit WorktreesMemory BlocksPlan WorkflowsAuto LearningsPersistent MemorySession IsolationBackground AgentsTask TrackingPR IntegrationDaily LogsGit WorktreesMemory BlocksPlan WorkflowsAuto Learnings
The Problem

Every time you start a Claude Code session, it forgets everything.

Your coding conventions, the libraries you prefer, the bugs you already fixed, the architecture decisions you made last week. Without persistent memory, every session starts from zero.

Without Mull
Re-explain your project structure
Repeat your coding preferences
Remind it about past decisions
Rediscover workarounds every time
With Mull
Knows your entire codebase
Remembers your style and tools
Builds on previous sessions
Captures learnings automatically
Capabilities

Everything your AI needs to remember

A structured memory system that grows with your projects and makes every session smarter than the last.

Persistent Memory

Context survives across sessions. Your AI remembers your codebase, preferences, and every past decision.

Task Tracking

Structured workflows from idea to merged PR. Plan, implement, review — all tracked in memory.

Background Agents

Autonomous agents condense sessions, extract learnings, and keep your knowledge base current.

Session Isolation

Every session gets its own git worktree. Work in parallel without conflicts or lost changes.

PR Integration

Automatic PR creation, CI status monitoring, and review workflows built into the session lifecycle.

Daily Logs

Every session is automatically summarized. Never lose track of what happened or when.

Workflow

How mull works

Hooks into Claude Code transparently. No workflow changes, just better context.

01

Session starts

Mull hooks into Claude Code's session lifecycle. An isolated git worktree is created, and your memory blocks are loaded automatically.

02

Context injected

Your persona, project knowledge, active tasks, and accumulated learnings flow into the system prompt. The AI knows your world.

03

Agents work in the background

While you code, autonomous agents condense sessions, extract reusable learnings, and update your knowledge base.

04

Session ends cleanly

Changes committed, daily log updated, learnings captured. Next session picks up right where this one left off.

session lifecycle
# session start
$claude
hook|Creating worktree...
hook|Loading 12 memory blocks
ok persona, projects, learnings
# working...
(your coding session happens here)
# session end
muse|Extracting learnings...
muse|Writing daily log...
muse|Condensing memory blocks...
ok +3 learnings, log updated

Ready to give your AI
a memory?

Join the alpha. Start building AI coding sessions that carry context forward.

BUILT WITH RUST // MADE BY COREYJA