Install & setup

remindy is not a CLI you keep running. After init it lives inside your editor as an MCP server. The CLI is only for setup, seeding, and the dashboard.

It’s on npm. Install it globally so editors get a stable server path:

npm i -g remindy

1. Start Supermemory Local

Supermemory Local is the shared, on-machine store. It is a Unix binary; on Windows, run it inside WSL2. (remindy itself runs on the host; WSL forwards localhost:6767 to Windows.)

curl -fsSL https://supermemory.ai/install | bash
~/.local/bin/supermemory-server    # listens on http://localhost:6767

Note

The installer puts the binary in ~/.local/bin, which is often not on PATH, so the bare supermemory-server may say “command not found”. Call it by full path, or locate it with find ~ -name supermemory-server -type f 2>/dev/null.

Hand the key it prints on first boot to remindy (it writes to remindy’s gitignored .env):

remindy config set --supermemory-key <key-from-first-boot>
# and your compression model, e.g. b.ai:
remindy config set --provider bai --key <bai-key> --model claude-sonnet-5

Why it’s load-bearing

Each editor spawns its own remindy process. A shared external store is the only thing that lets a correction made in one tool show up in another, and the only thing that survives an editor restart. Nothing leaves your machine.

2. Initialise remindy in your project

npx remindy init --seed

This does three things:

• Registers the remindy MCP server in every detected editor: Kiro, Cursor, Windsurf, GitHub Copilot (VS Code), Claude Code, and Antigravity. For Codex/ChatGPT and Trae, init prints a one-line command to paste.
• Appends a one-line project rule to your agent rules file (AGENTS.md, CLAUDE.md, or .cursorrules).
• Seeds standards inferred from your repo, so recall is useful immediately (--seed).

3. Reload your editor

Your editor spawns the MCP server on reload. That’s it, now just code with your agent.

Verify

npx remindy doctor

doctor checks everything in one shot:

• resolved config (secrets masked)
• one real compression
• Supermemory Local probe + active backend

Anything other than Supermemory Local means cross-tool sharing and persistence are off: fix it before you rely on shared memory.

Setup for reviewers

If you are running from a clone rather than npx:

npm install
npm run build
node dist/bin/remindy.js doctor
node dist/bin/remindy.js init --seed

Uninstall

npx remindy uninstall

This reverses init in every detected editor:

• Removes the remindy entry from the MCP config (.kiro/settings/mcp.json, .cursor/mcp.json, .windsurf/mcp.json, or .agents/mcp_config.json).
• Strips the rule block between <!-- remindy --> and <!-- /remindy --> from AGENTS.md, CLAUDE.md, or .cursorrules.

Then reload your editor. Your stored standards stay in Supermemory Local; clear them from the dashboard for a clean slate, or run npm rm -g remindy if you installed globally.