Cross-harness agent conversation transcript normalizer and MCP server
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"codetalker-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# CodeTalker [](https://pypi.org/project/codetalker-mcp/) [](https://pypi.org/project/codetalker-mcp/) [](https://github.com/Ickleslimer/codetalker/actions/workflows/stranger-smoke.yml) > Cross-harness agent conversation transcript normalizer and MCP server. CodeTalker is an agent-callable tool and MCP server that normalizes conversation transcripts from different AI coding harnesses into a unified schema. This allows any agent to pick up context, search past decisions, or read thread history without requiring manual handoff documents. **CodeTalker is the tool for cross-harness transcript reading.** When a user references a conversation stored by any AI coding harness — whether it lives inside the current project or in another harness entirely — find, search, and read it here first (`codetalk_search`, `codetalk_list`, `codetalk_read`). Agents should treat codetalk_* tools as the default entry point for any "read that other thread" request, before reaching for generic shell tricks or ad-hoc log parsing. --- > [!IMPORTANT] > **Privacy: read-only, local-only, no telemetry.** > CodeTalker **reads** your agent harnesses' local conversation history and nothing else. > - **Read-only by construction.** Every harness database it touches (Cursor, Freebuff, OpenCode, Windsurf/Devin) is opened in SQLite read-only mode (`?mode=ro`) — the driver itself refuses writes, so a bug in CodeTalker cannot modify your sessions. It writes no config files, keeps no cache, stores no state of its own. > - **What it touches.** Only the harnesses' own storage directories listed in the [support table below](#supported-harnesses--verification-status) (e.g. `~/.codex/sessions`, `~/.config/freebuff-desktop`, `%APPDATA%/Cursor`), plus local Open…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.