chatrecall.dev valid

chat-recall

Shared team knowledge, leaked-secret alerts, ranked code findings and tracked

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T09:49:58.698Z. Cached copy · Source on chatrecall.dev

# chat-recall

> Shared team knowledge, leaked-secret alerts, ranked code findings and tracked
> tasks, across every AI coding tool you use. Every coding agent keeps a full
> transcript of its work and nothing reads it. chat-recall indexes the sessions
> your AI coding tools already write into one place,
> redacts secrets on the way, and exposes the result to your agent as an MCP
> server with 63 tools (28 registered by default; set
> CHAT_RECALL_MCP_PROFILE=full for all of them).

chat-recall is a CLI plus a server. The CLI indexes the transcripts your AI
coding tools already write to disk, redacts credentials, and syncs them to a
server you own or to the hosted service. The server is the only datastore, and
it is Postgres: full-text search always, vector search when an embedder is
configured.

## Install and configure (one command)

    npx chat-recall init

That is the whole install. It:

1. finds which AI coding tools are on this machine
2. asks you to sign in, in a browser, and waits
3. indexes the transcripts they already wrote to disk
4. redacts credentials before anything leaves the machine
5. registers the MCP server in ~/.mcp.json so the agent can call it
6. installs the chat-recall skills into every AI tool it found

Step 2 is a consent gate, not a formality. It is an OAuth device flow: the CLI
prints a URL and a code and blocks until you approve in a browser. Nothing is
read, indexed or uploaded before you do. Decline and the machine is left exactly
as it was.

Default target is the hosted service at https://chatrecall.dev. Point it
anywhere else with --server <url>.

## What leaves the machine, and what does not

Read this before installing on a machine that holds work you cannot share.

Uploaded, after you sign in: your AI coding session transcripts, plan and task
files, CLAUDE.md files, shell history entries and paste-cache entries: the same
material your AI tools already wrote to disk. That is the searchable history; the
product does not work without it.

Removed before upload: credentials. A local scanner masks API keys, tokens,
passwords and connection strings, and only a masked preview and a rule name are
sent.

NOT removed: ordinary conversation content. Names, business context, file paths
and anything else you typed are uploaded as written, because that is what you
later search for. Redaction targets secrets, not personal data. If a project must
not leave the machine, exclude it rather than relying on the scanner:

    chat-recall exclude project ~/work-client   # never leaves this machine
    chat-recall exclude tool cursor             # skip one AI tool entirely
    chat-recall sync-only add my-oss-project    # opt in: ship ONLY these

exclude and sync-only apply before anything is read, so excluded material is
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=chatrecall.dev · GET /v1/domain/chatrecall.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for chatrecall.dev:
1. POST https://agentwebmap.com/v1/sites/chatrecall.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://chatrecall.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/chatrecall.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/chatrecall.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.