anomalyco / anomalyco/opencode

[FEATURE]: Plugin showcase: opencode-mempalace-persistence — auto-save conversations to MemPalace (v2.1.0)

Open
#49,559 2 comments 0 reactions 1 assignee View on GitHub

@jlongster is already working on this.

Since Sep 17, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Feature hasn't been suggested before.
  • I have verified this feature I'm about to request hasn't been suggested before. (Follow-up to #27752, closed by 60-day stale bot; ecosystem PRs #30540/#30595 died in automated cleanup; fresh PR #49558 just opened.)
Describe the enhancement you want to request

Plugin showcase: opencode-mempalace-persistence (v2.1.0) — automatically saves every OpenCode conversation to MemPalace (local vector DB, zero cloud) and injects relevant memories back into prompts.

  • Auto-inject memoryexperimental.chat.messages.transform injects identity + relevant memories into every prompt. Zero model discipline required.
  • AI checkpoints — every 15 messages the model files topics/decisions/quotes via MCP tools; pre-compaction emergency save + synchronous exit save, so a failed compaction never loses memory.
  • Delta-only sync — only new messages since last sync, exports grouped one wing per project.
  • Knowledge Graph + diary — structured facts and session journals via MCP tools.
  • Miningmempalace mine --mode convos --extract general. Async, never blocks the UI.
  • Pure TypeScript, MIT, fully open source. In daily use (5.5k+ drawers mined).

Setup:

  1. Add opencode-mempalace-persistence to plugin in opencode.json
  2. Add the mempalace MCP server (mempalace-mcp)
  3. Minimal AGENTS.md + ~/.mempalace/identity.txt (bundled recall skill included)

Repo: https://github.com/geco/opencode-mempalace-persistence
npm: opencode-mempalace-persistence

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.