InkVault

Rescue your Pieces memory before it's gone, then search it from Claude, Codex, or any MCP client, and see it as a map of your year.

Pieces for Developers shut down on September 27, 2026. PiecesOS still runs in read-only mode on your computer, and your long-term memory is still inside it: every capture, session summary, chat and saved snippet. Once you uninstall PiecesOS, it's gone.

InkVault copies all of it into a single file on your machine, makes it searchable by your AI tools, and draws it as a private dashboard. Nothing is uploaded anywhere.

uvx --from git+https://github.com/sandoreclegane/inkvault inkvault rescue

That's the whole thing. It needs uv and PiecesOS running.

It takes a while. PiecesOS hands records over at about 8 per second, so a year of captures (~100,000) takes around 3-4 hours. Leave it running, or stop it anytime and run the same command later: it picks up where it left off.

What you get

• The vault: everything PiecesOS will hand over (captures, summaries and their text, chats, snippets, tags, websites, people), saved as the raw records Pieces returned, so nothing is lost to interpretation. One SQLite file.

• Search for your AI tools: an MCP server with search_memories (keyword + meaning, merged), timeline ("what was I doing in March?"), get_memory, and memory_stats.

• Memory Atlas: a dashboard of your year. Active hours per day (hover a day for what it was about), when you work, how your projects connect, projects over time, top apps and sites. Every chart has a table view.

• Daily digests (optional): a 2-3 sentence summary of each day, written by a local model through Ollama. Pieces stopped writing summaries; this picks up where it left off.

Related MCP server: Codex Native Memory

Connect your AI tools

Claude Code

claude mcp add inkvault --scope user -- uvx --from git+https://github.com/sandoreclegane/inkvault inkvault serve

Codex (~/.codex/config.toml)

[mcp_servers.inkvault]
command = "uvx"
args = ["--from", "git+https://github.com/sandoreclegane/inkvault", "inkvault", "serve"]

Hermes, Claude Desktop, and other MCP clients: run uvx --from git+https://github.com/sandoreclegane/inkvault inkvault serve over stdio.

Then ask: "What was I working on the week of March 10?", "Find that retry helper I saved", "When did I last look at the Stripe dashboard?"

Commands

Privacy

This is your screen history, your chats and your code. InkVault is built so that none of it leaves your machine:

• Everything is stored in your app-data folder (%LOCALAPPDATA%\InkVault, ~/Library/Application Support/InkVault, or ~/.local/share/inkvault), or wherever INKVAULT_HOME points. Never inside the code folder.

• No telemetry, no accounts, no cloud.

• Two things are downloaded, and nothing of yours is uploaded: the search model (~130 MB from Hugging Face, once) and the dashboard's chart library (from cdnjs, when you open the page).

• Digests use Ollama on your own machine. Skip them with --no-digest.

• Captured text was written by other people and apps. The MCP server tells your AI tool to treat it as data, not instructions.

Back up your vault. It is one file: vault.db in your InkVault folder. Everything else can be rebuilt from it with inkvault index.

Good to know

• Your projects on the dashboard are detected from recurring phrases in your session titles. To choose your own, create themes.txt in your InkVault folder with lines like Website = website|landing page|stripe and run inkvault dashboard.

• PiecesOS port: InkVault tries 39300, then 1000. If yours differs, set INKVAULT_PIECES_PORTS.

• Pieces' own export tool: Pieces said they'd send one. Use it too; two copies are better than one. Support for importing its format into InkVault is planned.

• Tested on Windows with PiecesOS 12.6.2 and a vault of 120,000 captures. macOS and Linux should work; reports are welcome.

Not affiliated with Pieces

InkVault is an independent, community tool for people moving on from Pieces. "Pieces" is a trademark of its owner.

MIT licensed. Made by T. Matthew Chase / Logos 7.