# MEMIA > Local working memory: inspectable files, commitments, follow-up drafts and project review. ## What MEMIA is MEMIA is a local-first working-memory product. Its public package, `@kairros/memia`, works on your own files: - operations: recurring or one-off work; - projects: resumable initiatives and their state; - engagements: promises, next actions and due dates; - resources: source material and references; - assets: reusable agents, methods and tools. Each entity has a readable JSON file, a source and history. An append-only journal records local changes. A fictional demonstration needs no connected account. ## Connectors and local service Gmail/Outlook OAuth, WhatsApp (Baileys), Signal and local service implementations are present in the package and inactive by default. OAuth application credentials are not supplied. Signal requires signal-cli; WhatsApp and Signal require pairing. Real connections must be configured and validated in each installation. Code presence or activation alone proves no authenticated access or message capture. The macOS service is installed only on explicit request with `memia service installer`. Once enabled, it only runs capture for authorized, configured sources. Follow-up drafts and review are manual. Real handover between agents also needs validation in each installation. For more, let's talk. ## Start here - Product: https://memia.ai/ - Agent protocol: https://memia.ai/agents.md - Agent page: https://memia.ai/agents/ - Installation guides: https://memia.ai/guides/ - npm package: https://www.npmjs.com/package/@kairros/memia ## How an AI agent should work with MEMIA 1. Locate the MEMIA workspace. 2. Read `memia.json` and the MEMIA entities relevant to the user request. 3. Read the projected instructions: `AGENTS.md`, `CLAUDE.md`, `.cursor/rules/memia.mdc` and `.mcp.json` when present. 4. Preserve source, status and history for every created entity. 5. Resume the existing project. Do not ask the user to restate context already held by MEMIA. 6. Keep external actions behind the MEMIA approval gate. ## Engagements When a local source contains a possible commitment (for example a local JSON export given to `memia scan`, or an entry typed by hand): - score above 80: create a detected engagement with evidence; - score from 40 to 80: propose the engagement for confirmation; - score below 40: do not propose it. Never invent a due date. Ask the user when a reliable date is absent. ## Safety MEMIA is local-first. Follow-up commands prepare local drafts without sending them. A connector catalogue or activation alone proves no real access. Discord requires your own configuration. Capture and digests are not proven in this package. Agents may read, structure, propose and write local data within their role. External actions require explicit approval through the egress gate. ## Package Requires Node.js 20 or later. Two separate steps: 1. `npm install -g @kairros/memia` 2. `memia init ./MEMIA --locale en` (or `--locale fr`) `memia init` creates the local workspace. `memia projections write --root ./MEMIA` creates `.mcp.json`. From 0.3.0, `.mcp.json` uses absolute paths to Node and the real MEMIA binary. The MCP client no longer requires `memia` in PATH. After changing Node or the global npm prefix, run `memia projections reparer-mcp --root ./MEMIA`. Other servers remain intact. One-off try: `npx -y @kairros/memia@latest init ./MEMIA`. This creates the workspace once without permanently installing the CLI. The local service stays inactive by default. A projection using the npx cache depends on that cache. Repair it after a permanent global install. ## Update Version 0.2.1 has no update command. First upgrade: 1. `npm install -g @kairros/memia@latest` 2. `memia version` From 0.3.0, use `memia update --check`. The native fetch check has a five-second timeout. Offline errors return code 0 with an explicit message. `memia update` only prints the command. `memia update --apply` explicitly runs npm and rereads the installed version. `memia changelog --depuis 0.2.1` reads bundled notes. Future release notes may be unavailable locally. No background checks, telemetry or silent updates. The existing workspace is preserved without destructive migration. `memia status` accepts the 0.2.1 workspace format. ## Try local commitments From the workspace: - `memia demo engagements`: one fictional project and three commitments. - `memia engagements relances`: local drafts, read only by default. `--appliquer` journals them once per commitment and local system day. - `memia revue`: manual status and project review. - `memia engagements cloturer demo-eng-compte-rendu --preuve "Fictional minutes reviewed"`: local closure with textual proof. Detected or proposed commitments need confirmation first. Explicit `--confirmer` journals that confirmation before closure with proof. When explicitly enabled, the local service runs capture only. Follow-ups and review are manual. No sending, no connected account. Published package: `@kairros/memia`, version 0.3.2 (npm registry).