Codex History Hub
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HISTORY_HUB_DB | No | Path to the SQLite database file for history-hub. Can be set via environment variable or --db argument. | data/history-hub.db |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| history_get_recent_contextB | Get a project overview plus recent primary conversation summaries. Subagents are excluded by default. |
| history_searchB | Search older cross-account history. Call only when the user explicitly asks to search past history, names an older date/source/topic, or recent context is insufficient. |
| history_get_threadB | Read a selected history thread after identifying it via recent context or search. Full mode should be used only when the user explicitly requests the full thread. |
| history_get_project_summaryA | Get the durable overview of a project without loading conversation transcripts. |
| history_update_project_summaryA | Update the confirmed durable project overview in the independent Hub only. Never writes to any source Codex account/session store. |
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 targets a distinct operation: recent context retrieval, cross-account search, thread reading, project summary retrieval, and project summary update. The overlap between recent context and project summary is intentional, and descriptions clarify the difference.
All tools share the 'history_' prefix and mostly follow a verb_noun pattern (get_recent_context, get_thread, get_project_summary, update_project_summary). The exception is 'history_search' which lacks an explicit object, but the pattern remains clear.
With five tools, the set is well-scoped for a history hub: retrieval, search, and update operations. Each tool serves a clear purpose without redundancy.
The surface covers core history workflows: recent context, search, thread retrieval, and project summary read/update. A minor gap is the lack of an explicit list projects tool, but search and recent context can compensate.