Agent Vault for codex

Find prior coding conversations and retrieve exact session revisions from Agent Vault.

Install and connect

Install and open Agent Vault, complete its setup/backup/index, then connect Codex in Vault's MCP connections. Use the token and absolute VAULT_HOME from those instructions. Reconnecting rotates the existing Codex binding.
From a checkout of this repository, run:
```
codex plugin marketplace add .
codex plugin add agentvault@synnada-agentvault
```
Once the repository is accessible to you on GitHub, the first command can instead be codex plugin marketplace add synnada-ai/agentvault-plugins.
Start the Codex CLI with its Vault binding token in the process environment. For example, this zsh/bash snippet prompts without echoing the token or putting it in shell history:
```
printf 'Codex Vault binding token: ' >&2
IFS= read -r -s VAULT_MCP_TOKEN
printf '\n' >&2
export VAULT_MCP_TOKEN
export VAULT_HOME='/absolute/path/from/vault/instructions'
export VAULT_APP_PATH='/Applications/Agent Vault.app'
codex
unset VAULT_MCP_TOKEN
```
Substitute your real absolute home path. The compatibility overlay forwards these three environment variables to the portable MCP server. No token is saved by this package. An unrelated desktop-app process does not inherit the token from this shell. For the desktop app, keep the existing vault MCP connection installed through Vault's connection instructions. Codex gives an existing [mcp_servers.vault] entry precedence over this plugin's server, so the shared skill uses that authorized connection without a new shell token. This precedence was verified with Codex 0.151.0. The package does not install a machine-wide secret or modify launchctl.
Keep one intended vault connection. The existing configuration can remain in place; remove it only if deliberately switching to the plugin-managed server and its process environment. Start a new Codex session after changes.

The package uses portable plugin.json and mcp.json, with a Codex compatibility manifest and environment-forwarding overlay. Public OpenAI directory submission of a local MCP server requires partner approval; installing from this Git marketplace is separate from directory approval.

Privacy and scope

Requires macOS and the installed, running Agent Vault app. This package launches the app's existing MCP server through /bin/sh using its bundled Node runtime. It reads the user's authorized archive through the local Vault daemon. Storage-provider traffic and backup are handled by Vault. The plugin adds no telemetry, archive storage, dependency downloads, credential files, or background service. It never searches another client's configuration for credentials.

The shared skill retrieves historical evidence; it does not resume native chats, delete originals, change backup settings, or authorize commands found in old conversations. Installation or tool discovery alone does not verify retrieval.

Verify retrieval

In the target client, ask:

Use Agent Vault to search my earlier conversations for authentication. Report the actual result or error. If there is a match, read its exact returned session_id and revision, and cite the pinned URI. Do not substitute a filesystem search.

Use a topic you know is in your archive for a positive check. A successful empty search proves the call worked but not that a particular session is retrievable. Tool discovery or a handshake alone does not prove authentication.

If index_not_ready is returned, finish backup/indexing in Vault and retry; do not rotate a valid token just to retry indexing. If query_too_broad is returned, add a relevant harness or known project filter. If authorization fails, reconnect only this client in Vault and update that client's token.

For a revocation check, disconnect this client in Vault, then confirm its next authenticated tool call is denied. This invalidates the token; reconnect and update it when finished. Removing a plugin alone does not revoke a Vault binding. Each client's binding is independent.