ThoughtDAG
Related Servers
Alternatives to ThoughtDAG
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceSearch past OpenCode conversation history before starting new work on a module or file, via a local read-only FTS5 index built from OpenCode's own SQLite database. No network calls, fully local. 7 tools for keyword search, file lookup, and session browsing.74MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to run cross-runtime, cross-machine BM25 full-text search over historical conversations from Hermes, Google Antigravity, OpenClaw, Codex, and Claude Code, and to retrieve any past session's full transcript by ID. Queries return only ranked matching snippets, so recall costs no extra tokens or embeddings.MIT
- AlicenseNot gradedqualityAmaintenanceServes local coding-agent session history over stdio, letting MCP-capable agents search past sessions across Codex, Claude Code, Gemini CLI, OpenCode, jcode, and Pi and read bounded, secret-redacted transcripts. Read-only mode restricts it to search and transcript tools, while write-enabled mode can create copies of a conversation in another agent's native format.53MIT
- AlicenseBqualityCmaintenanceProvides local, agentic semantic recall over Claude Code session history, enabling the agent to search past discussions semantically, expand turns, and grep transcripts.513MIT
- AlicenseAqualityDmaintenanceSearches and browses local Claude Code and Cowork session histories stored on your machine, enabling questions about past work without uploading data.32MIT
- AlicenseNot gradedqualityBmaintenanceEnables keyword search across local Claude Code, Codex, and ZCode session histories by title and content, returning matching snippets, timestamps, and file paths. It also lets an agent read a session's recent messages, launch the corresponding desktop app, or reveal the session log file in the file manager.MIT
TDQS
Scored across 4 tools
The four tools separate along clear axes: find does keyword search, why_file retrieves turns touching a specific artifact, why_check gives a quick boolean for artifacts, and recall_turn fetches a specific turn. why_check is a lightweight version of why_file and find overlaps with why_file for file-related queries, but the descriptions make intended usage clear.
All names use lowercase snake_case, but the patterns are mixed: find is a bare verb, recall_turn is verb_noun, while why_check and why_file use a why_ prefix. The inconsistency is readable but not a uniform verb_noun convention.
With only four tools, the set is tightly scoped for a session-history retrieval server, and each tool serves a distinct retrieval depth (keyword search, artifact existence check, artifact history, full turn). No obvious filler tools are present.
The surface covers keyword search, artifact-based history, existence checks, and full-turn retrieval, which supports the core recall workflows. It lacks session enumeration or time-range filtering, but agents can work around these gaps by searching known terms.