OpticLM × Nowledge Mem
Use OpticLM's own Nowledge SDK for thread continuity, then add Mem MCP when you also want agent-facing recall and durable memory tools.
Optic-owned integration
OpticLM maintains @opticlm/nmem for Optic's Extension functionality. It is an internal integration SDK, not a package Mem users need to install themselves.
OpticLM is stateless by default and lets users choose their own memory layer. Its official Nowledge path connects directly to Mem's HTTP API for Space and thread operations.
Before You Start
- Nowledge Mem is running on the Optic machine, or Optic can reach your Mem server
- Optic is up to date
- You can open Optic's Extension settings
For the default local path:
nmem statusMem normally listens at:
http://127.0.0.1:14242Enable The Built-In Integration
- Open Optic's Extension settings.
- Find Nowledge Mem and enable it when the integration is available in your build.
- Point it at the Mem endpoint you want Optic to use.
- Start a short conversation, then confirm it appears in Mem's Threads view.
There is no Nowledge community plugin to install. Do not install @opticlm/nmem as an end-user extension; Optic owns that dependency and its lifecycle.
What Optic's Public SDK Supports
The published SDK currently exposes:
- list and create Mem Spaces
- create a thread
- append messages with optional deduplication and idempotency keys
- reconcile a changed thread tail
- delete one thread or a bounded set of threads
This is a direct thread bridge. Optic decides when these operations run.
Add Agent-Facing Memory Through MCP
The public Optic SDK does not expose Working Memory, memory search, durable memory writes, or graph exploration. If you want the Optic agent to use those capabilities while it works, add Mem's standard MCP server through Optic's MCP Extension support:
{
"mcpServers": {
"nowledge-mem": {
"url": "http://127.0.0.1:14242/mcp/",
"type": "streamableHttp"
}
}
}For a protected or remote server, use the endpoint and authentication supported by your Optic MCP configuration. Keep the built-in thread integration and MCP together: one provides thread continuity, the other gives the agent retrieval and memory tools.
Verify
First, confirm Optic thread continuity by checking Mem's Threads view after a short conversation.
If you also configured MCP, ask Optic:
Use Nowledge Mem to read my Working Memory and summarize the current focus.These are separate checks. A saved Optic thread does not prove that the agent has retrieval tools, and working MCP tools do not prove that Optic's thread bridge is enabled.
Troubleshooting
Nowledge Mem is not listed in Optic
Update Optic first. The integration is owned and shipped by OpticLM, so there is no Mem-side package that can add the missing settings surface.
MCP tools work but no Optic thread appears
Enable Optic's built-in Nowledge integration. MCP does not import or mirror the host transcript by itself.
The thread appears but the agent never recalls knowledge
Add the Mem MCP server. The public @opticlm/nmem SDK focuses on Spaces and thread synchronization, not retrieval.