A head start from history.
Mine your existing git history for useful context. Start with what your project already knows.
Introducing Visp Memory
Great work
Great work
starts with
a little memory.
Give your coding agent the context to pick up where you left off. Your project’s history, decisions, and lessons. Ready for what’s next.
Local-first. Open source. Built for your workflow.
Context carries forward.
From your projectDecisions worth keeping
For your next sessionA little more context
A memory layer for
the way you build.
Runs locally
Open source
Connects via MCP
Backed by SQLite
Visp MemoryNew session.
Same understanding.
Your agent starts fresh. Your project doesn’t.
Visp Memory keeps useful knowledge close, so every session can build on the last.
Project memoryIllustrative workflow
From an earlier sessionDecision
The decision stays.
Even when the session ends.
“Keep session tokens in secure cookies. The auth flow depends on server-side validation.”
Source: project history · auth/session✓
In your next session
Your agent gets the reasoning before changing the auth flow.
Only what earns its place.
Memory is selected for relevance. When nothing clears the threshold, it stays out of the way.
Context you can inspect.
Curated, auditable memory. Keep the reasoning connected to the work it came from.
A little continuity goes a long wayFrom past work
From past work
to the next idea.
A simple memory layer between your project and your coding agent.
Explore the documentation- 1
Start with your project.
Install Visp Memory and use your existing git history to give memory a starting point.
- 2
Connect your coding agent.
Use MCP to bring project memory into your agent’s workflow. Keep using the tools you know.
- 3
Carry the useful parts forward.
Surface relevant decisions and lessons when they matter, without flooding the next session.
Your next session
doesn’t have to start over.
Give your coding agent a little memory.
pip install visp-memory