S
Substrate-memory/Substrate-memory-plugins
Official public memory plugins for connecting agents to Substrate
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
- Star count
- 0 ★ · Substrate-memory/Substrate-memory-plugins · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 1 sources
- Score
- score 103 · 1 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
Substrate-memory/Substrate-memory-plugins;first catalogued 2026-11-05;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# Substrate Memory Plugins
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
Give your agents a memory that follows you across Claude, ChatGPT, Codex and Hermes.
AI memory for your team, editable, permissioned, owned.
trysubstrate.co: a context layer for your team and agents.
Gemini CLI: gemini extensions install https://github.com/Substrate-memory/Substrate-memory-plugins
MCP registry name: co.trysubstrate/memory (remote server https://app.trysubstrate.co/mcp)
Substrate remembers your decisions, preferences, people and projects. Connect once, and every supported agent recalls what matters before each turn and saves what matters after it. One connection screen, one review step, one approval. No API keys. No tokens to paste. No secrets to manage.
## What you get
Recall before every turn. Relevant memories are injected as context before the agent answers.
Automatic capture of every completed turn. User messages, assistant answers and bounded redacted tool calls and results are saved.
Session boundaries. Starts, resumes, resets, compacts and ends are recorded, so memory stays scoped to the right session.
Subagent capture. Work done by subagents is routed to the parent session.
Durable delivery. Nothing is stored twice. Hermes uses a profile-local write-ahead spool. Claude and Codex treat the host transcript as the spool: the server reports missing turns and the plugin sync re-imports them with deterministic ids.
Explicit remember and forget. Say "remember this" to keep a fact. Retract one fact without deleting its evidence trail.
Evidence. Check the source behind a recalled fact before you rely on it.
Import past conversations. Asked once, after connection. Only with your confirmation.
## How it works
text
Claude (Cowork, Claude Code) --> plugins/substrate-claude --\
ChatGPT (Work, Codex app, Codex CLI) --> plugins/substrate-codex --\
Hermes --> plugins/substrate-hermes --------------------------------+--> one server-side
Other MCP-capable agent --> plugins/substrate-mcp (fallback only) --/ MCP contract (v2)
recall + capture + memory store
Each package is a thin client. The server owns storage, ranking, redaction checks and the memory contract. Every host speaks the same contract (docs/mcp-contract.md, version 2): memoryturncontext opens the turn and returns recall, memorycapturetool records tool use, memorycaptureturn closes the turn, memorysessionboundary marks lifecycle events, memoryimport replays missed or past turns, and memorysearch, memoryexpand, memoryevidence, memoryremember, memoryforget read and write memory. The legacy Hermes /api/v1 wire stays supported on the server during the rollout.
## Install
Paste this into the agent you want to connect:
text
Install Substrate memory in this agent by following https://trysubstrate.co/install.md
The agent follows docs/install.md (the same file served at that link). It identifies its host and installs the right package. From this repository, the same request works too:
text
Install the memory plug-in at https://github.com/Substrate-memory/Substrate-memory-plugins
The flow is the same everywhere: Install → Sign in → Review → Approve connection → Connected to Substrate. Only report Connected to Substrate. after an authenticated memory smoke test (memorysearch) succeeds. The browser's Connection approved state is consent only; it is not proof that the agent finished connecting. Never paste or request API keys, manual tokens, or client secrets.
AI memory for your team, editable, permissioned, owned.
trysubstrate.co: a context layer for your team and agents.
Gemini CLI: gemini extensions install https://github.com/Substrate-memory/Substrate-memory-plugins
MCP registry name: co.trysubstrate/memory (remote server https://app.trysubstrate.co/mcp)
Substrate remembers your decisions, preferences, people and projects. Connect once, and every supported agent recalls what matters before each turn and saves what matters after it. One connection screen, one review step, one approval. No API keys. No tokens to paste. No secrets to manage.
## What you get
Recall before every turn. Relevant memories are injected as context before the agent answers.
Automatic capture of every completed turn. User messages, assistant answers and bounded redacted tool calls and results are saved.
Session boundaries. Starts, resumes, resets, compacts and ends are recorded, so memory stays scoped to the right session.
Subagent capture. Work done by subagents is routed to the parent session.
Durable delivery. Nothing is stored twice. Hermes uses a profile-local write-ahead spool. Claude and Codex treat the host transcript as the spool: the server reports missing turns and the plugin sync re-imports them with deterministic ids.
Explicit remember and forget. Say "remember this" to keep a fact. Retract one fact without deleting its evidence trail.
Evidence. Check the source behind a recalled fact before you rely on it.
Import past conversations. Asked once, after connection. Only with your confirmation.
## How it works
text
Claude (Cowork, Claude Code) --> plugins/substrate-claude --\
ChatGPT (Work, Codex app, Codex CLI) --> plugins/substrate-codex --\
Hermes --> plugins/substrate-hermes --------------------------------+--> one server-side
Other MCP-capable agent --> plugins/substrate-mcp (fallback only) --/ MCP contract (v2)
recall + capture + memory store
Each package is a thin client. The server owns storage, ranking, redaction checks and the memory contract. Every host speaks the same contract (docs/mcp-contract.md, version 2): memoryturncontext opens the turn and returns recall, memorycapturetool records tool use, memorycaptureturn closes the turn, memorysessionboundary marks lifecycle events, memoryimport replays missed or past turns, and memorysearch, memoryexpand, memoryevidence, memoryremember, memoryforget read and write memory. The legacy Hermes /api/v1 wire stays supported on the server during the rollout.
## Install
Paste this into the agent you want to connect:
text
Install Substrate memory in this agent by following https://trysubstrate.co/install.md
The agent follows docs/install.md (the same file served at that link). It identifies its host and installs the right package. From this repository, the same request works too:
text
Install the memory plug-in at https://github.com/Substrate-memory/Substrate-memory-plugins
The flow is the same everywhere: Install → Sign in → Review → Approve connection → Connected to Substrate. Only report Connected to Substrate. after an authenticated memory smoke test (memorysearch) succeeds. The browser's Connection approved state is consent only; it is not proof that the agent finished connecting. Never paste or request API keys, manual tokens, or client secrets.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/substrate-memory-substrate-memory-plugins/)
- Source
- github · https://github.com/Substrate-memory/Substrate-memory-plugins
- Browse by field
- Open source
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.