Memexa · 镜我
English · 中文
A self-hosted personal memory graph over Chinese-native data — WeChat / QQ / email / documents / audio. This repository is the open demo. The full engine is a separate proprietary product.
What this is
memexa turns scattered, multi-party Chinese data into a queryable memory graph: every message is stored verbatim, extracted into structured cards, and every answer is cited back to the original sentence. It is fully self-hosted — your data never leaves your machine.
This repository ships the open demo: a small synthetic dataset and a stub extractor, so you can see the shape of the project in thirty seconds — no backend, no API key, no configuration.
Try the demo
pip install memexa
memexa demo
Six synthetic sources (WeChat / QQ / email / browser / AI chat / audio) are ingested with the stub extractor, then five sample queries run against the resulting cards — entirely in memory. This is the honest first look at what the project does.
The full engine
The demo runs a stub on synthetic data. The full memexa engine is a proprietary product and is not included in this repository. It adds:
- Live ingestion of your own data across multiple sources, incremental.
- A two-LLM extraction pipeline producing cards with per-claim citations and cross-alias canonical identities.
- A multi-channel recall stack with cross-encoder re-ranking — built for high-accuracy retrieval over messy, multi-party Chinese chat, not a single-vector lookup.
- An MCP server + CLI, so any coding agent (Claude Code, Cursor, Cline, Codex) can use your memory as a first-class tool.
- A local desktop app — runs the whole stack on your own machine.
For access to the full engine, please reach out via the repository owner's profile.
License
The demo in this repository is licensed under Apache-2.0 (see LICENSE). The full memexa engine is a separate proprietary product and is not covered by that license.
Metadata
Release files for memexa 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| memexa-0.1.0-1-py3-none-any.whl | Python 3 | none | any | Details |
Release files / memexa-0.1.0-1-py3-none-any.whl
| Download URL | memexa-0.1.0-1-py3-none-any.whl |
|---|---|
| Size | 20.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2ffa93b651951fc63424fa738cbf5ff7076f38fe1b1c9c5373153d300a4a0123
|
|
BLAKE2b-256 checksum How to use checksums |
688833d0b40100e9affef0cbe1ee16e65bc20c32ea5011df13e64c3c58045c32
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 1, 2026.
Transparency logSecurity for memexa 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
All 1 file in this release has been uploaded with provenance metadata.
Attestation for memexa-0.1.0-1-py3-none-any.whl
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 Jul 1, 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.