Memini
Memini is a self-hosted search and decision journal for code repositories, work conversations and meeting notes. Search results link to the source file, message or transcript that supports them.
Install
Run your own server. Start Docker with Compose 2.24+ and install the server launcher for your platform.
macOS or Linux (Homebrew)
brew tap npavlov/memini https://github.com/npavlov/memini.git
brew install npavlov/memini/memini-server
memini-server start
Windows (PowerShell and Scoop)
scoop bucket add memini https://github.com/npavlov/memini.git
scoop install memini/memini-server
memini-server start
The first start creates private settings and downloads the application, database and search model. Allow 4 CPU cores, 8 GB RAM and 20 GB of free SSD space. Get your first token · Illustrated installation guide · Manual Docker setup
Connect to an existing server. Install the CLI with the Windows x64 installer or Homebrew on Apple Silicon macOS and x86_64 Linux. You’ll need the server address and a read token from its operator.
Develop Memini. Build from source.
First steps
Create a workspace, import one example email conversation and find who proposed changing archive retention. The first search walkthrough includes the sample data, commands and expected results. To start with code, index one file from a Git repository and search for its bootstrap function.
Intake
| What you have | How to bring it in |
|---|---|
| A Git repository | Register the repository and schedule a sync. Memini tracks the selected ref. |
| Mail, chat, notes or wiki exports | Push records from a file or the HTTP API. Use one source per mailbox to keep accounts separate. |
| A mailbox or chat available inside an agent session | Give the agent a bounded import. It can push complete threads or capture a recipe's MCP responses. |
| An MCP server reachable from the service | Set up a scheduled MCP source. |
Use Memini
- Locate an implementation by symbol and open its file at the indexed commit. Code search · Read source
- Find who agreed to a change, read the evidence, and follow later decisions that replaced it. Decision history
- Find messages addressed to a person or meetings they attended. Messages · Meetings
Browse the online user knowledge base or its version in this checkout for setup, Intake, CLI and MCP tools, security, backup, upgrades and troubleshooting. For development and project history, see Contributing, the changelog and the Apache-2.0 license. Report a vulnerability privately.
Metadata
Release files for memini 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 |
|---|---|---|---|---|
| memini-0.1.0.tar.gz | 1.3 MB | Without provenance | Details for memini-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| memini-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for memini-0.1.0-py3-none-any.whl |
Total release size: 2.8 MB
Release files / memini-0.1.0.tar.gz
| Download URL | memini-0.1.0.tar.gz |
|---|---|
| Size | 1.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d2ece8e94bab8ad5cafd7d00b6acbc1f6a775604194ac8955ac3ec0e9f7b5c37
|
|
BLAKE2b-256 checksum How to use checksums |
0fc0490c846954250e0697a2f122ea3bbd7d5482e92640af3525e83016846937
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / memini-0.1.0-py3-none-any.whl
| Download URL | memini-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.5 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d8b2f75823585243b286b1ac1a9cad89605c022c6422b1f2c1d9e16e9d99192a
|
|
BLAKE2b-256 checksum How to use checksums |
1e257116083eb1c78b753a48289cd95b03a412867a987ca571acb47b1bb0730f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for memini 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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.