MindSlice
Portable memory for AI agents, with isolation and evolution built in.
Keep project knowledge, personal preferences and shared handbooks in plain Markdown. Mount what an agent needs, let it learn in its own workspace, and bake those learnings into reusable versions. Connect through MCP, the CLI or Python.
Why MindSlice?
Isolation. A slice is a folder of Markdown cards you can mount, unmount and share independently. Mounted slices stay read-only through the engine; new learning goes into a separate overlay. Multiple workspaces can reuse the same baseline while keeping their own changes. Pending edits stay outside live memory until approved.
Evolving memory. Cards can explicitly extend or supersede earlier knowledge, so
retrieval follows recorded relationships under your trust rules. bake turns selected
changes into new slice versions, preserving the original folders and returning the new paths.
Hot/cold memory focuses on what stays in context and what is retrieved later. LLM Wiki focuses on compiling sources into a maintained knowledge base. MindSlice makes memory boundaries and controlled evolution first-class engine operations. How these approaches fit together →
Python 3.12+. No runtime dependencies, database server or LLM API calls inside the engine.
Get started
Paste this into your coding agent:
Clone https://github.com/pancerZH/MindSlice.git (or use the existing checkout).
Read skills/mindslice-setup/SKILL.md to finish setup.
The agent helps you choose a workspace, connect your app, and choose how to start:
| Starting point | Tool |
|---|---|
| Empty memory or a short conversation | MindSlice init and ordinary memory writes |
| Existing MindSlice workspace | Connect it directly with -w |
Shared .slice or Markdown notes folder |
MindSlice mount, indexed as is |
| Documents to distill into structured cards | MindSlice-forge |
Forge is an optional document-conversion tool. It creates a new workspace using an agent harness; MindSlice handles storage, retrieval, mounting and memory evolution without needing Forge or an LLM. The builder skill guides conversion and integration with an existing workspace.
Prefer manual setup? With Python 3.12+ and pipx installed:
git clone https://github.com/pancerZH/MindSlice.git
cd MindSlice
pipx install -e .
mindslice init ~/mindslice
Then connect your agent and tell it what to remember.
Run mindslice -w ~/mindslice doctor, then verify a new session.
Full setup guide · Review changes and bake slices
Documentation
- Concepts — isolation, evolution, and how MindSlice fits other memory architectures.
- Reference — commands, Python API, MCP tools and card formats.
- History and recovery — explain memory, roll back slices, back up and restore workspaces.
- Build slices with Forge — convert documents and connect the resulting workspace or slices.
- Maintain memory — consolidate knowledge and repair relationships.
- Evaluations · Design · Uninstall
License
Apache License 2.0. Benchmark excerpts quoted in the evaluation records keep their datasets' licences; see NOTICE.
Metadata
Release files for mindslice 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mindslice-0.1.0.tar.gz | 220.5 kB | With provenance | Details for mindslice-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mindslice-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for mindslice-0.1.0-py3-none-any.whl |
Total release size: 369.2 kB
Release files / mindslice-0.1.0.tar.gz
| Download URL | mindslice-0.1.0.tar.gz |
|---|---|
| Size | 220.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ef2360136afdf752ff77c60d07b26bed6df5f9fd1660e1584d45bdf4a72e535e
|
|
BLAKE2b-256 checksum How to use checksums |
69a8867297ccbcb4f85c1716ea0589118cdc6253847831dd21ad677a7d586f1a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logRelease files / mindslice-0.1.0-py3-none-any.whl
| Download URL | mindslice-0.1.0-py3-none-any.whl |
|---|---|
| Size | 148.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7558f52363c4d9d2c89e349e2d06667843f0ee8a24a980cc739040849214b577
|
|
BLAKE2b-256 checksum How to use checksums |
fc4f3eee16710bed9d580fea265b0175a638c49568a23822ad914515e357e57d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logSecurity for mindslice 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for mindslice-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.