A year, made visible.
Explore active days, working hours and the projects that kept returning.
← The Work / Logos 7Your work deserves
InkVault · A memory you own
Your work deserves
a memory.
The conversations that moved you forward. The pages that changed your thinking. The decision you know you made, somewhere.
InkVault keeps your work together across tools, in a local archive you own. Find it again with your AI tools. See its shape through the Memory Atlas.
Pieces memory · Claude & Codex sessions · Chosen browser history
Memory Atlas
See the threads
you’ve been weaving.
When you worked. What held your attention. Where your projects meet. An archive becomes something you can explore.
Interactive sample · Entirely fictional data
This is InkVault’s actual dashboard, populated with made-up activity. Hover charts, change the date range, or choose “Show table.” It does not read anything from your computer.
Open the full sample Atlas ↗Follow the overlap.
See which projects appear in the same sessions. A map of recurring work, not a verdict about you.
Find the source.
Connect an AI client to search your preserved conversations, memories and pages.
Between work and memory
Built because
something mattered.
When Pieces announced its shutdown, the history people had entrusted to it needed a home. InkVault began as a way to preserve that work.
It now keeps growing with you: Claude Code and Codex conversations, supported Claude desktop sessions, and history from the browser profiles you choose. You don’t need to have used Pieces to start.
“What did we decide about the website last month?”
That’s the kind of question your connected AI tool can ask the vault. Retrieval gives it the saved material to work from; it doesn’t promise perfect recall or replace your judgment.
Start here
Two doors.
One archive.
Install uv, then run the command for your starting point in a terminal.
Rescue what’s there.
Keep PiecesOS installed and running until you’ve checked your export. Large archives take time; you can stop and resume.
uvx --from git+https://github.com/sandoreclegane/inkvault inkvault rescueRescue builds and opens your Memory Atlas.
Keep what comes next.
Preserve existing AI session files and selected browser history. InkVault asks which browser profiles are yours.
uvx --from git+https://github.com/sandoreclegane/inkvault inkvault syncThen build and open your Memory Atlas:
uvx --from git+https://github.com/sandoreclegane/inkvault inkvault dashboardNext: check your archive with the same command ending in status, back up vault.db, and run it ending in schedule to install the permanent command and keep your vault growing nightly. Full setup instructions ↗
Claude desktop import currently covers Windows agent-mode sessions. Safari is not supported. Windows has been tested with a real vault; macOS and Linux still need more reports from actual users.
Ownership, with clear boundaries
Your archive.
Your choices.
InkVault stores and searches your archive locally. No InkVault accounts or telemetry. InkVault itself does not upload your archive.
When you connect an AI client, memories returned to that client may be sent to its model provider under that client’s settings. Choose the client and settings that fit what you’re preserving.
Browser profiles are opt-in. Local storage still deserves care: saved conversations can contain sensitive text, and deleted browser visits remain in nightly backups until they rotate out.
Read the full privacy details ↗