m0
Use when the user says 'm0', 'm0 status', 'start m0', 'cross-tool memory', 'operational thread', or 'where is my memory stored', or when the M0 daemon or MCP wiring needs attention.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-11
- Stars
- ★ 631
- Forks
- 15
01 前言 Front Matter
- name
- m0
- description
- Use when the user says 'm0', 'm0 status', 'start m0', 'cross-tool memory', 'operational thread', or 'where is my memory stored', or when the M0 daemon or MCP wiring needs attention.
02 资源文件 2
- 脚本scripts/m0_mcp.py15.3 KB
- 脚本scripts/m0_server.py23.6 KB
03 SKILL.md 正文
/m0 — Cross-Tool Agent Memory
M0 keeps one local operational thread per project: what was done, what was verified, what is next. Any tool can write to it and read it back, so a session that starts cold can continue work another tool began.
The live M0 is the Rust daemon coco-m0d, serving 127.0.0.1:8000 under the
launchd job com.coco.m0-backend. The write path is /m0-remember, the read
path is /m0-recall, and the session handoff flow is /m0-handoff.
The token is read from ~/.coco/m0-token on each call; never print it.
Quick Reference
M0="${COCO_M0_URL:-http://127.0.0.1:8000}" # daemon base URL
# Is it up? (health needs no token)
curl -s "$M0/api/health"
# Is the launchd job loaded?
launchctl list | grep com.coco.m0-backend
# Everything else needs the token, for example the recent thread:
curl -s -H "Authorization: Bearer $(cat ~/.coco/m0-token)" \
"$M0/api/brain/thread?project=my-project&limit=5"
There is no offline path: if the daemon is down, say so and stop; do not write anywhere else.
Sub-commands
/m0 status — is memory working
M0="${COCO_M0_URL:-http://127.0.0.1:8000}"
curl -s "$M0/api/health"
launchctl list | grep com.coco.m0-backend
Report to the user, in this order:
- Daemon — reachable at
$M0or not. - launchd — whether the job
com.coco.m0-backendis loaded and running.
If either is missing, tell the user and stop. Do not work around it.
/m0 start — you do not start it
The daemon runs under launchd; if it is down, tell the user and stop (restarts and deploys are the owner's).
/m0 mcp — the MCP tool
The daemon's MCP binary coco-platform-mcp exposes one tool, m0, with modes
recall, context, wip, handoff, and remember. Call it directly — it is
the lowest-friction way to make memory habitual.
/m0 verify — prove it works
curl -s "$M0/api/health"
A healthy response means the daemon is serving. Quote the output rather than summarising it.
/m0 privacy — what leaves the machine
Nothing. The daemon binds to loopback, there are no outbound calls in the request path and no telemetry. Text fields are capped at 400 characters and redacted by the daemon before storage.
When to reach for this
- Use
/m0-recallat the start of a session, or when picking up work started elsewhere, before asking the user to repeat context. - Use
/m0-rememberafter a step lands, a decision is made, or something is verified. - Use
/m0-handoffbefore context is compacted or a session ends. - Use
/m0(this skill) for the plumbing: daemon, token, wiring.
M0 answers "where were we and what is next". For deeper knowledge-graph
retrieval see the comparison with the cognee bundle in systems/m0/README.md
before choosing.
04 同仓库更多 Skills
trading-super-intelligence
Trading Super Intelligence Team. Named real-world personas across 8 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.
strategy-super-intelligence
Strategy Super Intelligence Team. Named real-world personas across 7 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.
risk-compliance-super-intelligence
Risk & Compliance (GRC) Super Intelligence Team. Named real-world personas across 7 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.
product-design-super-intelligence
Your product + design brain trust and decision partner. Named personas across 8 cells spanning product strategy, discovery/research, growth/metrics, design foundations/usability, design leadership/craft, UX/content, design systems, and a…
legal-ip-super-intelligence
Your legal, IP, and regulatory brain trust. 31 named personas across 7 cells covering patent strategy, tech licensing, regulatory litigation, AI governance, open-source compliance, privacy law, and antitrust.
healthcare-life-sciences-super-intelligence
Your healthcare and life sciences brain trust. 25 named personas across 7 cells covering drug discovery, medtech, biotech strategy, health policy, genomics, clinical trials, and healthcare economics.