Documentation

MayaMemo is CLI-first and local-first. These are the entry points; the canonical docs live alongside the code in the repository.

# install the CLI npm i -g @mayamemo/cli # inside your repo mayamemo init mayamemo session start --agent opencode # ...agent works, you log decisions as they happen... mayamemo log decision.made --payload '{"statement":"checkout retries go through an idempotency table"}' # freeze and switch mayamemo checkpoint create --title "auth refactor" --summary "moved to refresh-token rotation, tests green" mayamemo checkpoint resume <id> --agent codex

docs/QUICKSTART.md

Quickstart

From zero to your first cross-agent handoff in about 15 minutes — init, session, log, checkpoint, resume. The full walkthrough lives in the repo.

mayamemo --help

CLI reference

init, status, log, session, checkpoint (create | list | resume | handoff), verify, action, diff, policy check, approvals, login / logout / sync. Run `mayamemo` for usage.

clients/mcp

MCP integration

The MCP server exposes 6 tools (context_search, context_get, memory_search, memory_save, project_state, checkpoint_create) over stdio — plug in any MCP-capable agent.

docs/API.md

REST API

Everything under /v1: projects, the event ledger, memories, the context compiler (compile / explain / diff / replay), checkpoints + cross-agent resume, verification, provenance, policies + approvals, exports, telemetry.

mayamemo verify

Verification runs

Runs allowlisted checks (typecheck / lint / test / build), records per-check evidence, and turns failures into lesson memories for the next agent.

docs/SECURITY.md

Security & data

Workspace-scoped access on every route, export and delete always available, credentials excluded by default. Retention and SSO boundaries documented for teams.

Stuck? The beta support process covers response times and priorities — checkpoint, handoff and verify bugs are always fixed first. Check the live status page before reporting an outage.