Installation
Commands
mengram setup
One command does the whole onboarding: creates your account, saves the API key, installs Claude Code hooks, auto-detects and configures your other AI tools (Cursor, Claude Desktop, Windsurf), imports your existing Claude Code history so memory is useful from minute one, and verifies the round-trip.
Detected tool configs are merged safely (existing servers preserved, a backup is written, unparseable files are never overwritten). If you already have a key, it asks whether to reconfigure.
mengram weekly
Your AI’s memory, summarized for the past 7 days — including the one metric no other tool shows: repeated mistakes prevented (procedures with past failures that your memory recalled this week, each with the date you last got bitten by it).--no-weekly to mengram auto-context to disable.
mengram init
Interactive setup — creates config, vault, and Claude Desktop MCP integration.mengram server
Start the MCP server for Claude Desktop, Cursor, or Windsurf.mengram status
Check setup status — config, vault, vector index, Claude Desktop integration.mengram stats
Show vault statistics — entity counts, fact counts, vector index info.mengram rules
Generate a CLAUDE.md, .cursorrules, or .windsurfrules file from your cloud memory.mengram hook
Manage the memory hooks — session context, auto-recall, auto-save, policy gate, run outcomes, and the compaction checkpoint. See Claude Code Integration for details.mengram resume
Where the task in this repository stands. The hooks (Claude Code, Codex, Cursor) write a task card when an agent stops — keyed bygit remote + branch, so another session, another agent in another worktree of that branch or another machine finds it — and inject it at the next session start, saying whether the code has moved since the last check.
A session on a branch with no card of its own — a fresh Orca worktree, say — gets one line saying which cards exist, not another branch’s task, which is usually another agent’s. The agent’s draft of the task carries over only to the session that continues it; a task you confirmed carries over to any.
~/.mengram/resume/ and need no account; only the draft uses a model.
mengram try
Zero-account, local-only preview of what Mengram memory would know. Scans your Claude Code history on-device — nothing is uploaded, no API key needed:mengram import
Import existing data into memory.mengram import claude-code
Import your local Claude Code session transcripts (~/.claude/projects) into cloud memory — memory knows your projects from minute one instead of starting empty.
- Secrets are redacted before storage — on import (client-side) and again server-side in the extraction pipeline, so keys/tokens/JWTs pasted into a conversation never reach the model or get stored (→
[REDACTED]) - Each session counts as one add operation against your plan’s monthly quota
- Re-runs skip already-imported sessions;
--reimportforces a fresh pass