[KongchangAI]
Product

Slowave

An open-source, locally run memory layer tool for programming agents. It dynamically maintains memory salience through reinforcement and decay mechanisms, enabling agents to participate autonomously in memory management. Data is stored via SQLite and services are exposed through MCP endpoints.

Timeline (last 90 days)

Sep 16

Slowave is a fully locally-running open-source tool serving as a programming agent memory layer, using a lightweight multilingual embedding model with data stored in SQLite, requiring no external memory services or LLM APIs

Unverified50%
Sep 16

Slowave allows programming agents to participate in maintaining their own memory, adjusting memory salience through agent feedback signals (useful, irrelevant, or outdated)

Unverified50%
Sep 16

Slowave introduces a mechanism similar to biological memory: useful memories are reinforced, useless memories decay over time, and the rest are treated as noise.

Unverified50%
Sep 16

Slowave's memory cycle is: remember → recall → use → feedback → reinforce/weaken → decay.

Unverified50%
Sep 16

Slowave works through 5 MCP endpoints.

Unverified50%
Sep 16

Clients supported by Slowave include Claude Code, Codex, Cursor, Cline, OpenCode, Windsurf, and Claude Desktop.

Unverified50%
Sep 16

Slowave has been open-sourced on GitHub, with the repository at slowave-ai/slowave.

Unverified50%
Sep 16

Slowave's core assumption is that retrieval is only part of the memory problem, and what truly matters is whether memories that are helpful to the current task and goal can be retrieved.

Unverified50%
Sep 16

Because the agent itself evaluates whether a memory is useful, Slowave no longer needs a separate LLM judge to maintain memories, thereby avoiding token waste and the split-brain problem.

Unverified50%
Sep 16

Slowave's decay mechanism may carry the risk of accidentally deleting memories that are truly important but temporarily unused, and the accuracy of the agent's self-evaluation of memory usefulness also needs to be verified through real-world testing.

Unverified50%

All Facts (10)

Unverified

Slowave's decay mechanism may carry the risk of accidentally deleting memories that are truly important but temporarily unused, and the accuracy of the agent's self-evaluation of memory usefulness also needs to be verified through real-world testing.

50%
Unverified

Slowave allows programming agents to participate in maintaining their own memory, adjusting memory salience through agent feedback signals (useful, irrelevant, or outdated)

50%
Unverified

Slowave introduces a mechanism similar to biological memory: useful memories are reinforced, useless memories decay over time, and the rest are treated as noise.

50%
Unverified

Slowave's memory cycle is: remember → recall → use → feedback → reinforce/weaken → decay.

50%
Unverified

Slowave works through 5 MCP endpoints.

50%
Unverified

Clients supported by Slowave include Claude Code, Codex, Cursor, Cline, OpenCode, Windsurf, and Claude Desktop.

50%
Unverified

Slowave is a fully locally-running open-source tool serving as a programming agent memory layer, using a lightweight multilingual embedding model with data stored in SQLite, requiring no external memory services or LLM APIs

50%
Unverified

Slowave's core assumption is that retrieval is only part of the memory problem, and what truly matters is whether memories that are helpful to the current task and goal can be retrieved.

50%
Unverified

Because the agent itself evaluates whether a memory is useful, Slowave no longer needs a separate LLM judge to maintain memories, thereby avoiding token waste and the split-brain problem.

50%
Unverified

Slowave has been open-sourced on GitHub, with the repository at slowave-ai/slowave.

50%

Source Articles