English | 简体中文
我要给她完整的一生。 I will give her a whole life. — from The Wandering Earth (《流浪地球》)
JarvisMind is an open, self-hosted unified memory infrastructure for AI systems. It gives any assistant (a chat app, an agent, a desktop tool, an enterprise system) one place to remember, recall, govern and forget what a user has told it, and one web console where the owner can see and correct all of it.
- Authoritative memory (JME). Each memory space keeps its memories in one SQLite database. No other component keeps a copy that can drift.
- Governance (JMR). Credentials are refused before any write. Sensitive personal facts wait for the owner. Agents cannot approve their own requests or correct memories themselves.
- Knowledge graph (JKG). A view of people, projects, events and relations derived from memories. It is never a second memory store.
- Context engine (MCE). Finds relevant memories and builds a context block. The block is marked as untrusted data, so a model reads it as reference material, not as instructions.
- Console. The owner's browser console: memories, graph, governance, spaces, agents, operations, API management, backups, settings.
- API v1 and SDKs. A versioned
/api/v1surface for agents, with Python and TypeScript clients. - DSH example. A runnable integration with a cross-session demo.
Owner (browser) Agents and apps (DSH, DeepSeek, Claude, custom ...)
owner credential agent token (jmt_...), per-space grants
| |
v v
/api/v1/console, /api/v1/memories, ... /api/v1/agent/*
| |
+------------------------+----------------------------+
v
JarvisMind API (FastAPI, one process)
+----------------------------------------------------------+
| MCE context and recall --reads--> JME memories |
| JMR governance gate --guards--> JME writes/audit |
| JKG graph (derived) <--feed--- JME audit log |
+----------------------------------------------------------+
|
control.db : spaces, agents, grants, token digests, access log (metadata only)
jarvismind.db : default memory space (JME + JMR + JKG tables)
spaces/<id>/ : one physical store per additional space (database + vectors)
Read docs/ARCHITECTURE.md for the principles, the write and forget paths, and the isolation model.
Requirements: Python 3.13 (the version used for the release tests). Node.js 20 or newer is needed only to build the console.
cd backend
python3.13 -m venv .venv
. .venv/bin/activate # Windows: see docs/deployment/WINDOWS.md
pip install -r requirements.txt
python -m jarvismind init-db # creates ./data/jarvismind.db and ./data/control.db
python -m jarvismind serve # http://127.0.0.1:8777Check it:
curl -s http://127.0.0.1:8777/healthBuild the console and serve it at /console/:
(cd ../console && npm ci && npm run build)
JARVISMIND_CONSOLE_DIR="$(cd ../console && pwd)/dist" python -m jarvismind serveThe owner token is in backend/data/.jarvismind_token (created on first start, mode 0600), or in the
JARVISMIND_API_TOKEN environment variable if you set one. Sign in at http://127.0.0.1:8777/console/.
Step-by-step guides: Installation, Configuration, Docker, Windows, Linux, macOS.
- Create the agent and its token in the console (Agent 管理), or with
examples/dsh-integration/python/setup_agent.py. - Before a reply, call
POST /api/v1/agent/contextand put the returned block in the system prompt. - After a turn, call
POST /api/v1/agent/remember. JMR decides what is stored. - Forgetting is two-step and the owner decides it. See docs/AGENT-INTEGRATION.md.
SDKs: Python and TypeScript. The full DSH walk-through is in docs/tutorials/INTEGRATE-WITH-DSH.md.
| Area | Result in the release environment |
|---|---|
| Backend test suite (including the P0 release gate) | 2485 passed, 0 failed; gate 67/67 |
| Console | typecheck clean, 15 unit tests pass, production build succeeds |
| Python SDK | 10 tests pass |
| TypeScript SDK | 9 tests pass |
| DSH cross-session demo | 16/16 checks, Python and TypeScript, against a live server |
| Docker image, Windows and Linux installs, a real DSH application | not verified (see the release report) |
Limits and open items are listed in docs/ROADMAP.md and in the release report.
All documentation is indexed in docs/README.md. Security status is in docs/SECURITY.md and docs/SECURITY-AUDIT.md.
- CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md
- CHANGELOG.md (versioning follows SemVer)
- Licensed under the MIT License, see LICENSE.