# AI use cases for Echoes Vault Codex (psinetron/echoes-vault-codex) Repo: [psinetron/echoes-vault-codex](https://github.com/psinetron/echoes-vault-codex) | Use cases: 4 | Page: https://dedupedai.com/use-cases/psinetron-echoes-vault-codex/ EchoesVault is a Codex plugin that keeps a repository's memory as plain Markdown that survives across sessions and can be read by other coding agents. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Set up persistent project memory for a repo in Codex: https://dedupedai.com/use-cases/psinetron-echoes-vault-codex/set-up-project-memory-in-codex/ - Share one project memory across teammates and agents: https://dedupedai.com/use-cases/psinetron-echoes-vault-codex/share-project-memory-with-team-and-agents/ - Bootstrap a project's memory from the terminal: https://dedupedai.com/use-cases/psinetron-echoes-vault-codex/bootstrap-memory-without-codex/ - Restore project memory at task start and save it at the end: https://dedupedai.com/use-cases/psinetron-echoes-vault-codex/restore-and-save-codex-session-memory/ ## How to set up persistent project memory for a repo in Codex with Echoes Vault Codex Repo: [psinetron/echoes-vault-codex](https://github.com/psinetron/echoes-vault-codex) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Install the EchoesVault plugin and initialize memory in one project so Codex keeps context between tasks. **Who it is for:** A developer who starts many Codex tasks in the same repository and keeps re-explaining the architecture and past decisions. **The problem:** Each new Codex task starts without the project history, so decisions and context must be repeated. **The outcome:** The project has an EchoesVault folder and a portable runtime, and later Codex tasks show a status card and can restore memory. ### Steps 1. Run `codex plugin marketplace add psinetron/echoes-vault-codex` once in a terminal. 2. Run `codex plugin add echoes-vault-codex@echoes-vault`. 3. Run `codex plugin list` and confirm the entry shows installed, enabled. 4. Start a new Codex task in your project and send: Initialize EchoesVault for this project. 5. Commit the generated EchoesVault/, .echoes-vault/echoes_vault.py, and adapter files with Git. ### Prompt to paste into your agent ```text Using the EchoesVault plugin from psinetron/echoes-vault-codex, initialize project memory in and list the files it created. Expected output: an EchoesVault/ folder and a .echoes-vault/ folder containing echoes_vault.py. Verify that EchoesVault/.gitignore ignores index.md. ``` ### Caveat Initialization is project-local, and the plugin stays silent in repositories that have not been initialized, so each project needs its own setup. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/psinetron-echoes-vault-codex/set-up-project-memory-in-codex/ ## How to share one project memory across teammates and agents with Echoes Vault Codex Repo: [psinetron/echoes-vault-codex](https://github.com/psinetron/echoes-vault-codex) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Commit the EchoesVault files so teammates and Claude or OpenCode follow the same memory rules. **Who it is for:** A team lead whose members use different coding agents on the same repository. **The problem:** Each person and each agent keeps separate context, so the team gives conflicting instructions and loses decisions. **The outcome:** Every agent in the repo reads the same AGENT_PROTOCOL.md and uses the same committed runtime, so memory stays consistent. ### Steps 1. Initialize EchoesVault in the project by sending: Initialize EchoesVault for this project. 2. Commit the generated protocol, portable runtime, and adapters with Git. 3. Push the branch so teammates receive the EchoesVault folder and .echoes-vault/echoes_vault.py. 4. Teammates clone the repo and do not need a global EchoesVault install to use the committed runtime. 5. Ask Claude or OpenCode in the project to restore project memory and confirm it reads AGENT_PROTOCOL.md. ### Prompt to paste into your agent ```text In the project at , use the committed EchoesVault files from psinetron/echoes-vault-codex to restore project memory with Claude or OpenCode. Expected output: a short summary of the latest session entries and the protocol version. Verify that the agent reads EchoesVault/AGENT_PROTOCOL.md before writing. ``` ### Caveat Teammates must use the same protocol version, and the README says a protocol mismatch should stop writes until the adapter or plugin is updated. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/psinetron-echoes-vault-codex/share-project-memory-with-team-and-agents/ ## How to bootstrap a project's memory from the terminal with Echoes Vault Codex Repo: [psinetron/echoes-vault-codex](https://github.com/psinetron/echoes-vault-codex) | Difficulty: Advanced | Time: 30 minutes | Basis: From the README Run the bundled engine directly to create EchoesVault files in a project without opening Codex. **Who it is for:** A developer or automation owner who manages repositories from scripts or works in an agent other than Codex. **The problem:** Codex is not always available, but the project still needs the same memory files and runtime. **The outcome:** The target project contains the protocol, portable runtime, and adapters, ready to be committed. ### Steps 1. Run `git clone https://github.com/psinetron/echoes-vault-codex.git` once. 2. Run `python3 echoes-vault-codex/scripts/echoes_vault.py --workspace /path/to/your/project --agent codex --adapter-version 1.1.1 init`, replacing the workspace path with your project. (inferred, check the README) 3. Open the target project and check that EchoesVault/ and .echoes-vault/ were created. 4. Commit the generated files in the target project. ### Prompt to paste into your agent ```text Clone psinetron/echoes-vault-codex and run its scripts/echoes_vault.py init against with --agent codex and --adapter-version 1.1.1. Expected output: the EchoesVault/ and .echoes-vault/ folders in that project. Verify that .echoes-vault/echoes_vault.py exists in the target project. ``` ### Caveat The README says the generated runtime is the execution source after bootstrap, so the bootstrap step is only needed once per project. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/psinetron-echoes-vault-codex/bootstrap-memory-without-codex/ ## How to restore project memory at task start and save it at the end with Echoes Vault Codex Repo: [psinetron/echoes-vault-codex](https://github.com/psinetron/echoes-vault-codex) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Use the status, restore, and final save commands in Codex to carry context from one task to the next. **Who it is for:** A developer working on an initialized project over several Codex tasks who wants each task to pick up where the last one ended. **The problem:** Important decisions made late in one task are lost when the next task begins. **The outcome:** The new task starts with the restored index and recent session entries, and the finished task is saved as memory. ### Steps 1. Open the initialized project in a new Codex task and read the status card in the first response. 2. Send: Restore project memory. 3. Send: Show EchoesVault status to check size, index integrity, and warnings. 4. Work on the task, then send: Remember this architectural decision for any key choice. 5. Send: Save and finish this EchoesVault session. ### Prompt to paste into your agent ```text In the initialized project at , restore EchoesVault memory in Codex, show the status, and then save the session. Expected output: the restored index with the three latest session entries, a status summary, and a saved session file. Verify that the status reports no index integrity problems. ``` ### Caveat Already-open Codex tasks do not load newly installed skills and hooks, so a new task is needed after installation or update. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/psinetron-echoes-vault-codex/restore-and-save-codex-session-memory/