Practical overview
When it fits
Use it when an LLM agent must carry project context across sessions and its memory needs bounded growth, source traceability, and a review path for conflicts.
Who it is for
- Developers building LLM agents that need to resume project work across sessions.
- Teams evaluating memory-update behavior or handling contradictory project interaction history.
Documented uses
- Retain useful project state without placing complete interaction logs into every prompt.
- Extract and select candidate memories from ongoing interaction evidence.
- Recall relevant memories in a later session and apply feedback to memory value.
- Route conflicting memory proposals for human review.
- Assess memory behavior changes with causal-replay evaluations.
Requirements & limits
- The core memory engine is described as LLM-free, but semantic judgment and relevant-set operations use a separate provider path; setup lists a ZAI_API_KEY.
- The repository describes an OpenCode plugin and sidecar integration, with SQLite-backed evidence and task stores.
- The memory pools have stated capacity limits, while unresolved conflicts are routed to a human-review queue.
- The README labels the project a research preview and identifies PENDING-08 as awaiting manual acceptance.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Start the memory sidecar for a project
Install the listed Python dependencies, configure the environment file, and start the project-scoped memory server.
Before you start
- Python environment
- NumPy and pytest installed with pip
- A copy of the repository
- A .env file populated with ZAI_API_KEY
Steps
Run the command below.
pip install numpy pytestCopy
.env.exampleto.envand setZAI_API_KEY.Run the command below, replacing `` with the project directory.
python -m hybrid_memory.server --project
Expected outcome
The memory server starts with the specified project directory.
Guide limitations
- This setup path does not document an end-to-end agent session or retrieval workflow.
- The README labels the project a research preview and notes PENDING-08 as awaiting manual acceptance.
Load the bridge through OpenCode
Use the repository’s OpenCode plugin to load the memory bridge and launch the sidecar.
Before you start
- Node package manager
- OpenCode CLI installed as
opencode-ai - A local copy of the Dynamics Memory repository
Steps
Install the CLI with the command below.
npm i -g opencode-aiChange into the repository directory.
Run
opencode; the README says the.opencode/plugin/memory-bridge.tsplugin loads and launches the sidecar.
Expected outcome
The repository’s OpenCode plugin bridge is loaded and starts the sidecar.
Guide limitations
- For use in another project, the README describes linking
memory-bridge.tsinto that project’s.opencode/plugin/directory and resolving@opencode-ai/pluginfrom the link’s real path. - The README does not provide a full configuration or verification procedure for a separate project.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 16 October 2026
- Original website title
- 1173591564/Dynamics-memory · Official homepage title · retained in its source language

