v0.2.0 — Dual-scope memory

What's new

Breaking changes

• evermemos_forget signature changed: added scope and mine_only parameters.

New features

• Dual-scope memory — project scope for repo-specific facts, global scope for cross-repo user preferences
• evermemos_recall, evermemos_remember, evermemos_forget now accept a scope parameter
• Automatic write classifier routes messages to project or global scope
• Preference promotion: repeated project preferences auto-promote to global profile
• Ranked injection order: project profile → episodic → foresight → global profile
• Local store upgraded to v2 with scoped namespaces; v1 auto-migrated

Bug fixes

• Fixed health check endpoint /v1/health → /health
• Health gate changed to fail-open (missing OpenCode inference API no longer disables memory hooks)
• Config default baseUrl port corrected 8000 → 1995
• Removed dead formatRecalledMemories export

See CHANGELOG.md for full details.

v0.1.1 — Passive recall on first message

What's new

• Fix: Passive recall now fires on the very first message of a new session. Previously, the system prompt injection bailed out early when the session cache was cold — memories were never injected until the second message.
• Fix: Local memory lane hits are now included in passive system prompt injection (previously only available through the explicit evermemos_recall tool).

What's working

• Cross-session passive recall — model answers from memory without any explicit tool calls
• Explicit tools: evermemos_remember, evermemos_recall, evermemos_forget
• Project-scoped memory via git remote URL hash
• Local memory lane for fast deterministic recall
• Profile memory injection
• Fail-open — EverMemOS being down never crashes the chat

Install

npm install -g opencode-evermemos-plugin

See README for full setup.