Fidelis Memory

io.github.hermes-labs-ai由 GitHub 账号 hermes-labs-ai 发布v0.2.0更新于 Oct 24, 2026

Recall locally stored agent memories through an MCP-compatible host.

发布方自己的服务:Memory.fit

已验证STDIO仅桌面文件与存储知识与记忆

概览

AI 生成的概览

本地记忆服务器,让助手逐字保存笔记并在后续会话中召回原始段落。

可以做什么
  • 从本地记忆库召回已保存的笔记与段落
  • 逐字保存新的文本与笔记供后续会话使用
  • 更正或取代旧记录,同时保留其历史状态
  • 获取并查看单条记忆记录及其有效性
  • 在共享库上执行关键词与向量混合检索
适用场景
适合需要把早前会话中的确切措辞、条件或注意事项带入新会话,而不是依赖摘要的场景。也适合希望笔记只留在本机、单机本地优先的使用方式。
运行要求
以本地 Python 包运行(Python 3.10+,macOS 或 Ubuntu),可通过 uvx 或 pip 启动。需要本地 Ollama 服务及 nomic-embed-text 模型生成嵌入,无需模型 API 密钥。环境变量 FIDELIS_PORT 指定本地服务端口(默认 19420)。安装会注册随登录启动的用户级后台服务。
安装前请注意
安装会注册后台服务(launchd 或 systemd --user)随登录运行,并在用户主目录下维护共享存储;召回会搜索整个存储,而不只是刚加入的笔记。删除存储会清空全部记忆。可选的抽取与模型辅助路径会转换或过滤输入,召回文本可能被发送给助手所用的模型提供方。该版本为单机预发布版。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Fidelis Memory,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Fidelis Memory

[Fidelis Memory mascot]

Your agent can forget a summary. Fidelis brings back the note.

Local memory for Codex, Claude Code, and other agents: save text across sessions and retrieve the original passage when it matters.

by Hermes Labs

PyPI · Connect an agent · Technical reference

A project summary might say “billing migration rolled back.” The original note says why it failed and do not retry until the idempotency fix is verified. When your next session depends on that condition, the missing sentence matters.

Fidelis stores your Markdown and text notes and retrieves their stored wording. Its default retrieval does not ask a generative model to rewrite your memory.

Try it with one note

This path supports Python 3.10+, macOS or Ubuntu, and a local Ollama service. Start Ollama if needed (ollama serve in a separate terminal). No model API key is required. The current release is 0.3.0rc1.

bash
ollama pull nomic-embed-textpython3 -m venv ~/.venvs/fidelissource ~/.venvs/fidelis/bin/activatepython3 -m pip install "fidelis-memory[hybrid]==0.3.0rc1"fidelis init
demo_dir=$(mktemp -d)cat > "$demo_dir/atlas.md" <<'NOTE'Atlas billing migration:Duplicate charges appeared in staging. Rolled back.Do not retry until the idempotency fix is verified.NOTE
fidelis watch "$demo_dir" --oncefidelis recall-hybrid "Atlas billing migration retry condition" --tier zero_llm

fidelis watch and fidelis recall-hybrid use the background service started by fidelis init.

Look for both the rollback and the retry condition in the retrieved text. This is retrieval of a saved note, not a generated answer. For your own files, replace "$demo_dir" with a notes directory. If retrieval fails, run fidelis health and confirm Ollama has nomic-embed-text available. Keep the virtual environment after fidelis init; the background service uses it.

What this changes on your machine: fidelis init installs a per-user background service (launchd on macOS, systemd --user on Linux) that starts fidelis-server automatically at login. fidelis watch sends the note to that server, which saves it in the local store at ~/.cogito/store by default, not in the temporary demo directory. fidelis recall-hybrid also queries that same running server and searches the whole shared store, so its results can include notes you saved earlier, not only the demo note. The watcher also records ingested files in ~/.fidelis/watched.json. To remove the default service on macOS, run fidelis init --uninstall; it stops the service and deletes the launchd plist only. On Linux, find the installed unit with systemctl --user list-unit-files '*fidelis-server*', then run systemctl --user disable --now <unit>, delete that unit file from ~/.config/systemd/user/, and run systemctl --user daemon-reload. Neither path deletes your data. The store is shared by everything you save with Fidelis, so deleting ~/.cogito/store erases all of it, not just the demo note; do that only on a throwaway install. Also delete the temporary demo directory ($demo_dir), and ~/.fidelis/watched.json if you want its record of the file path gone.

Connect an agent

Once the note is retrievable locally, install the MCP connection for your client:

bash
fidelis mcp install --client codex# Or, for Claude Code:fidelis mcp install

Restart the client and try: “Use Fidelis to find my Atlas billing migration note. What must happen before we retry? Quote the relevant text.”

The client gets tools to recall, store, correct, fetch, and inspect memory. It decides when to call them; installing the connection does not make every turn recall automatically. Other clients and uninstall commands include Cursor, Gemini CLI, Copilot CLI, and OpenClaw. A separate Pi extension provides prompt-time recall.

What Fidelis preserves

  • Original wording. watch, store, and other verbatim write paths keep the text you supplied, so retrieval can return the condition that a summary might omit.
  • Local retrieval. Fast vector search is the default MCP recall path. Explicit hybrid search combines keyword and vector results without a generative LLM at its zero_llm tier; local embeddings still require Ollama.
  • Corrections over time. A correction can supersede a prior record without erasing it. Recall can show validity and historical status instead of silently replacing the old note.

Fidelis also has optional extraction and model-assisted routes. Those can transform or filter inputs; use the verbatim path when the original wording is the point. Retrieved text can still be wrong or out of date, and your agent's model provider may see it when answering.

Current scope

Fidelis 0.3.0rc1 is a single-machine pre-release, not a hosted team memory service. The LongMemEval-S retrieval run measured whether the redesigned default path retrieved material across 470 questions; it did not measure answer accuracy. See the results, user-fit guide, and security policy for deeper detail.

Full reference · Upgrade notes · Contribute · Changelog

Apache-2.0. Hermes Labs builds agentic infrastructure for autonomous systems.

来源:README.md,提交 9504c4a

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

2
  1. v0.2.0最新Sep 20, 2026
  2. v0.1.0Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Memory 集成