Perseus Vault Codex
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_MODEL | No | OpenAI model to use for synthesis | gpt-5.6 |
| OPENAI_API_KEY | No | OpenAI API key for the perseus_reflect synthesis tool | |
| PERSEUS_VAULT_BIN | No | Path to the perseus-vault binary (optional, default found on PATH) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| perseus_rememberA | Save a fact, decision, convention, or piece of context to persistent encrypted memory so it survives across Codex sessions. Call this whenever you learn something durable about the project: build commands, code style, architectural decisions, gotchas, or the user's preferences. Idempotent per (category, key). |
| perseus_recallA | Retrieve relevant memories from past Codex sessions. Call this at the start of a task, or whenever you need project context you might have learned before, e.g. 'how do we run tests here', 'what did we decide about auth'. Uses FTS5 keyword + hybrid ranking; returns the most relevant memories with a score. |
| perseus_forgetA | Remove a stale or incorrect memory. Soft-deletes by (category, key) — the memory is hidden from recall but recoverable. Use the key shown in a prior perseus_recall / perseus_remember result. |
| perseus_reflectA | Synthesize an insight from stored memories. Given a question, Perseus Vault recalls the most relevant memories and asks the configured LLM (your OpenAI/GPT-5.6 key by default) to produce a grounded answer citing them. If no LLM is configured, returns the assembled memory context so you can reason over it yourself. |
| perseus_statusA | Report the health of the memory store: how many memories are stored, whether encryption at rest is active, the database location, and whether reflect (LLM synthesis) is available. Zero-argument. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool serves a unique memory operation: storing, recalling, forgetting, synthesizing, or checking status. No two tools overlap in purpose.
All tools follow a consistent 'perseus_verb' pattern, making their actions immediately clear.
Five tools is an ideal size for a memory system, covering essential operations without redundancy or omission.
Core CRUD operations are present (create, read, soft-delete), and reflect provides synthesis. Missing explicit update, but idempotent remember can achieve the same effect.