MEMIA Guides

Your first continuity thread

Create the local workspace once. Then choose one surface and verify that the next agent can resume the workstream.

1. Create the local workspace

Prerequisite: Node.js 20 or later.

# step 1: install the package, globally
npm install -g @kairros/memia

# step 2: create the MEMIA workspace
memia init ./MEMIA --locale en
memia status --root ./MEMIA

# project the canonical instruction (AGENTS.md · CLAUDE.md · Cursor · MCP)
memia projections write --root ./MEMIA
memia projections check --root ./MEMIA

memia projections write --root ./MEMIA creates .mcp.json. From 0.3.0, this file calls the absolute paths to Node and the MEMIA binary. The MCP client no longer requires memia in PATH.
Published version: 0.3.2. Check your installation with memia version.
Inspectable local memory, commitments, scheduled operations and fictional demo. Gmail/Outlook (OAuth), WhatsApp (Baileys) and Signal connector code is present and inactive by default. Connections need validation in your installation; OAuth application credentials are not supplied.

Update

Version 0.2.1 has no update command. The first upgrade uses npm:

npm install -g @kairros/memia@latest
memia version

From 0.3.0: memia update --check. No background checks. The existing workspace is preserved, with no destructive migration.

After changing the global npm path, prefix or nvm version: memia projections reparer-mcp --root ./MEMIA.

One-off try without a global install: npx -y @kairros/memia@latest init ./MEMIA. It creates the workspace once, without permanently installing memia. The service stays inactive by default. It is installed only when you explicitly request it.

Try local commitments

Fictional data only. From the created workspace:

cd ./MEMIA
memia demo engagements
memia engagements relances
memia revue
memia engagements cloturer demo-eng-compte-rendu --preuve "Fictional minutes reviewed"

Follow-ups and review run manually. The local service only runs capture. Nothing is sent.

With --appliquer, follow-ups are journaled once per commitment and local system day. Timestamps remain UTC.

A detected or proposed commitment needs prior confirmation. Explicit --confirmer journals that confirmation before closure with proof.

Track your projects

From 0.3.2, each project has a record, a status and a history. From the workspace you created:

memia projets creer --titre "Website" --description "Redesign"
memia projets list
memia projets show website
memia projets pause website --motif "waiting for quote"
memia projets reprendre website
memia projets terminer website
memia projets abandonner website

A new project is active by default. show displays the record, the history and linked commitments. To link a commitment: memia engagements creer --titre "Mock-up" --echeance 2026-11-01 --projet website. memia projects is an alias of memia projets.

By default, the MEMIA MCP server is read-only. With memia mcp serve --write, it also exposes memia_project_create, memia_project_set_status and memia_engagement_create: local writes, logged, nothing sent. To enable it in a client, add "--write" at the end of the args of mcpServers.memia in .mcp.json. memia projections write always generates the read-only form.