EchoesVault for Codex plugin
Codex plugin that keeps a markdown project wiki in the repository and restores it each session, for OpenCode and Claude Code too.
- 127 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The `SessionStart` hook runs Python at session start, and initialization adds files and instruction blocks to the repository.
Install
- Works in
Manual install
codex plugin marketplace add psinetron/echoes-vault-codex
codex plugin add echoes-vault-codex@echoes-vaultThe first command adds the marketplace and the second installs the plugin. Then start a new Codex task.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The `SessionStart` hook runs Python at session start, and initialization adds files and instruction blocks to the repository.
This is third-party code. Review the repository files before installing.
What it does
EchoesVault creates an `EchoesVault/` folder in the repository with markdown pages, daily entries and an index. Install the plugin in Codex once, then ask in the target project: "Initialize EchoesVault for this project". In other repositories the plugin stays silent. It ships five skills: `echoes-init`, `echoes-start`, `echoes-vault`, `echoes-end` and `echoes-status`. Initialization copies a portable dependency-free Python engine into the project, blocks for `AGENTS.md` and `CLAUDE.md`, and adapters for OpenCode and Claude Code. After that those agents use the same memory without the plugin installed.
Who it is for. Teams and solo developers whose agents share one repository while decisions get lost between sessions.
Good fit when
- A new session must know which architecture decisions are already made.
- Codex and Claude Code both work in the repository and need shared memory.
- Project knowledge is kept in git and opened as an Obsidian vault.
- After a task the session results are saved with one phrase: "Save and finish this session".
Not a fit when
- You need semantic memory with vector search: this uses plain markdown files and a deterministic index.
- You need the plugin in the Codex IDE extension: plugins are not supported there yet.
- The repository must not receive service files and blocks in `AGENTS.md`.
Example request
Initialize EchoesVault for this project and record the decision about choosing a database.Limitations
The plugin runs in Codex from the ChatGPT desktop app or the Codex CLI, and the IDE extension does not support plugins. It needs Python 3.9 or later as `python3`, plus Git for installing from GitHub. The plugin registers a `SessionStart` hook that runs Python at session start, so review the hook code beforehand. Initialization adds `EchoesVault/`, `.echoes-vault/`, blocks in `AGENTS.md` and `CLAUDE.md` and OpenCode adapters to the repository, and these files are committed. Removing the plugin does not erase knowledge or the engine in already initialized projects. The last repository commit dates from September 2026.
How to disable. Disable or uninstall the plugin through `/plugins` in Codex and optionally drop the source with `codex plugin marketplace remove echoes-vault`. Remove the `EchoesVault/` and `.echoes-vault/` folders from projects by hand.
FAQ
How do I check that the plugin is installed?
Run `codex plugin list`: the entry `echoes-vault-codex@echoes-vault` should read `installed, enabled`. Start a new task after installing, because open tasks do not receive the skills.
Is Codex required to keep using the memory?
No. After initialization the `.echoes-vault/echoes_vault.py` engine lives in the project, and OpenCode and Claude Code work through it.
Where is the project knowledge stored?
In the `EchoesVault/` folder: pages in `pages/` and daily entries in `daily/`. The `index.md` index is built locally and stays out of git.
How do I set up EchoesVault without Codex?
Clone the repository and run `python3 echoes-vault-codex/scripts/echoes_vault.py --workspace /path/to/your/project --agent codex --adapter-version 1.1.1 init`. The command creates the vault and adapters for other agents.
Which phrases trigger the skills?
Plain wording works: "Restore project memory", "Show EchoesVault status", "Remember this architectural decision", "Save and finish this session". Skills can also be called by name, for example `$echoes-init`.
Discussion
No questions or reviews yet.
Related
PluginsEchoesVault keeps project memory as markdown pages in git: OpenCode, Codex and Claude Code read the same decisions and fixes.
A Codex plugin of five independent meta-skills and one tldraw skill: improves prompts, goals, research, plans and commits.
Persistent memory for Codex CLI through hooks: stack, decisions and lessons are recalled automatically and saved after each turn.
Codex on Crack splits Codex work across models: the lead plans, a worker implements and the lead reviews the result.
ECX ties Claude Code and Codex together with shared memory so each sees the other latest messages, plus 19 skills and 21 hooks.
An operating layer for Claude Code and Codex: one /do entry point, project memory across sessions, safety hooks, cost telemetry and parallel agents
README in short
The memory follows an open protocol 1.0.0: page schema, locking, conflict checks and alignment with the OKF format. The vault reads without any agent and opens as an Obsidian vault.