OpenCode + MemorySync

Overview

Add one line to your OpenCode config and memory is on: the opencode-memorysync plugin injects your profile and project context into the system prompt (recalled once per session, replayed identically from cache), captures both sides of every exchange as they happen, and registers the MemorySync MCP servers plus three slash commands — without ever overwriting configuration you wrote yourself. Every hook swallows every failure: a thrown plugin hook would break an OpenCode session, so none can throw, by contract and by test. Guaranteed injected recall — not model-optional retrieval that can silently skip.

Setup status and requirements

Supported version

opencode-memorysync 1.0.0

Last setup review

2026-08-24

Permissions

A MemorySync API key with read and write scopes (or OAuth on first tool use).

Limits

Requires an OpenCode build with plugin support (@opencode-ai/plugin 1.x). Set MEMORYSYNC_DISABLE=1 to switch off without uninstalling.

Capabilities

• One-line install: { "plugin": ["opencode-memorysync"] } — OpenCode auto-installs from npm
• Guaranteed recall via chat.system.transform, cached per session
• Automatic capture of both sides with content-hash dedup — retries converge
• Non-destructive config registration: user MCP/command entries always win
• Slash commands: /memorysync-recall, /memorysync-remember, /memorysync-status
• Compaction-aware: memory context survives session compacts
• Session-safe by contract: every hook wrapped, never throws, tested

Quick Start

# Add to ~/.config/opencode/opencode.json:
# { "plugin": ["opencode-memorysync"] }
# then set your key and restart OpenCode:
export MEMORYSYNC_API_KEY=ms_...

# MCP only instead:
npx memorysync-mcp-install --client opencode

Use Cases

Explore More