DEV Community

Antonio Zhu
Antonio Zhu

Posted on Edited on

OpenCode Plugin Memory v0.5–0.6: Less Maintenance, More Control Over Memory Audits

Keeping project memory useful should not create another maintenance job. These two releases make it easier to keep memory up to date and choose how background reviews run.

v0.5.0 — merged memories, without an extra sync step
Once a memory proposal is merged, it is available to subsequent requests without waiting for a separate index-generation workflow.

There is no generated index to maintain and no automation needed just to keep it current. Fewer moving parts, less housekeeping.

Existing memories stay intact. Users upgrading from an older version can remove the old index file and its regeneration workflow; the release notes explain what to clean up.

v0.6.0 — choose a separate model for memory reviews
Background reviews look for duplicate, outdated, or conflicting memories. They can now use a separately configured AI provider instead of depending on the main coding session’s credentials.

That gives users two practical benefits:

Restore reviews when host authentication gets in the way. OpenCode 2.x users affected by the account-token rejection can give the audit its own supported API key.
Control review costs separately. Keep the preferred model for coding and choose a lower-cost model for background reviews. Billing and limits still depend on the provider and account used.
This is optional. If background reviews already work, there is no need to change their configuration.

The approval rule stays the same
The agent proposes. A person reviews and merges. Background reviews can suggest removing a memory, but they cannot silently delete approved knowledge.

Top comments (0)