Local-first agent memory
Retrieve the note you wrote, without a memory-model rewrite.
Fidelis Memory runs a local service that indexes your notes and returns stored passages verbatim to compatible agent clients.
$ python3 -m pip install "fidelis-memory==0.1.0"
fidelis init
fidelis healthA local retrieval path for notes that must keep their wording
Fidelis stores notes in a local service and returns the stored passage instead of generating a memory summary. The default retrieval path makes no LLM call; an agent can still use its usual model after receiving the passage.
Use it when the decisive wording in a project decision matters. It is a memory retrieval layer, not a truth check for the note and not a guarantee about an agent's final answer.
Get one local retrieval
Install Ollama and its local embedding model first. Then install the released package, initialize the local service, ingest a disposable note, and query it. fidelis init installs the persistent fidelis-server service under launchd or systemd; it starts on boot, logs to ~/.fidelis/server.log, and stores Chroma and SQLite data in ~/.cogito/.
$ ollama pull nomic-embed-text $ python3 -m pip install "fidelis-memory==0.1.0" $ fidelis init $ fidelis health
health reports a status: ok prefix when the service is reachable.
$ mkdir -p /tmp/fidelis-verify $ printf '%s\n' 'Release decision: use the blue deployment.' > /tmp/fidelis-verify/note.md $ fidelis watch /tmp/fidelis-verify --once $ fidelis query 'Which deployment did we choose?'
The query result contains Release decision: use the blue deployment.
Decision boundary. Windows is not supported by this release. The setup needs a reachable local Ollama service; it does not make an agent call recall automatically. Stop the persistent service with fidelis init --uninstall.
Connect an agent client
After the local health check passes, register the released MCP server for your client. For Codex, run fidelis mcp install --client codex; restart the client and use its MCP view to confirm the Fidelis server is available. The repository documents Claude Code, Copilot CLI, Gemini CLI, and OpenClaw paths as well.
Fidelis exposes recall, query, health, and orientation tools. Tool availability confirms registration; perform a query against a note you ingested to confirm the complete retrieval path.
Configuration, troubleshooting, and limits
Use fidelis health before debugging client registration. If it cannot report status: ok, make sure Ollama is running and the embedding model has been pulled, then rerun fidelis init. For a missing result, ingest a known file with watch --once and query a distinctive phrase from it.
The released service is local-first and the default retrieval path does not call an LLM. It does not turn stored content into verified facts, provide Windows support, or establish a compliance posture for a deployment. Read the full reference and user-fit guide before using it for a shared or regulated memory store.