cc-anywhere

Memory built for AI coding.  ·  Pick work back up with context, not guesswork.

I wanted to remember what we discussed about my projects, and couldn't find past discussions, decisions, or feedback. The AI agents also seemed to forget.

So I built cc-anywhere — for me and the AI coding agents. One memory layer; both audiences read it the same way.

Every Claude Code, Claude Cowork, Codex CLI / Desktop, and Gemini CLI session you run gets captured into a fast local SQLite database with full-text and natural-language search. Then you can ask any future session — Claude, Codex, Gemini, anything that can shell out to a CLI — "what did we decide about auth last week?" and get the actual past conversation back.

🌐 cc-anywhere.com

Try it out

pip install cc-anywhere
cc-anywhere --init

Prefer pipx, or pip blocked by externally-managed-environment (common with Homebrew Python)? pipx install cc-anywhere works the same.

Two minutes, fully local, no account. Open a fresh session and ask "what did we decide last week?" — recall fires automatically. Platform notes and manual commands are in Install below.

---

What you can do with it

• Search across all your AI coding chats. One query over every Claude Code, Codex, Cowork, and Gemini CLI session on your machine — ranked, with project, speaker, and timestamp.

  cc-anywhere --ask "what did we decide about auth?"
  

• Let Claude Code in on your Codex sessions — and vice versa. One shared local memory across every tool, so the work you did in one agent isn't invisible to the next.
• Get a new session up to speed on a previous one. Hand a fresh session the thread you left off on — the actual reasoning, not a summary you'd have to write yourself.

  cc-anywhere --ask "catch me up"
  

• Find what you discussed about a product feature. Recall the why behind a call — the alternative you rejected, the constraint that forced it — that never made it into the code.

  cc-anywhere --ask "the pricing page"
  

And under the hood:

• Automatic capture — every session is saved to a local SQLite database on session-end and hourly. Nothing to remember.
• Local-first & private — no cloud, no API key, no model inside. Your conversations stay in a SQLite file you own.
• Agent-callable — the integration contract is plain stdout. Any agent with command-line access can use it — no MCP, no SDK, no plugin.
• Digests & sync — --daily / --weekly / --monthly activity reports, plus opt-in cross-machine sync (your own private GitHub repo, an external SSD, or an iCloud / Dropbox / NAS folder).

---

The 30-second demo

pip install cc-anywhere
cc-anywhere --capture
cc-anywhere --ask "what did we decide about auth?"

That's the whole thing. The third command searches every Claude Code, Claude Cowork, and Codex session you've ever had on this machine and returns the conversations that match — ranked, with project, speaker, and timestamp.

The first time you run it, search will surface conversations from months ago that you'd half-forgotten. The moment people realize their entire AI coding history just became queryable is the moment this project earns its keep.

Two query modes — --ask routes automatically

# Topical recall — name a subject, get the relevant past conversations
cc-anywhere --ask "what did we decide about pricing"

# Temporal recall — name a time window, get a chronological pull (no keywords needed)
cc-anywhere --ask "what was I working on today"
cc-anywhere --ask "this week"
cc-anywhere --ask "catch me up"

Wide windows (this week / month) return a daily rollup with drill-in hints so you can walk back into a specific day. Narrow windows return a per-session list with previews.

Usage overview

cc-anywhere --usage

Modeled on Claude Code's /usage but with longer time horizons (not capped at 30 days), per-project breakdown, per-machine breakdown when sync data is present, and a marathon-sessions view.

For LLM agents

cc-anywhere --llm-guide

Prints the full LLM-facing usage reference (query patterns, drill-in, when not to use, code-vs-conversation interplay). Reachable from any cwd, so an agent in any session can fetch it. LLM-CHEATSHEET.md at the repo root mirrors the same content for human reading.

---

Why it exists

AI coding assistants are great at remembering inside a session and unaware of everything before it. ChatGPT memory is locked to ChatGPT. Claude memory is locked to Claude. Codex has no cross-tool memory at all. Vendors won't fix this — siloed memory is a feature of their lock-in, not a bug.

cc-anywhere is the local layer that gives that history back to you. User-owned, vendor-neutral, fully on your machine, free.

It also exposes that memory to coding agents. A human can use the CLI directly, or an agent can call --ask, --view, and --source on the user's behalf to recover project context before acting.

Once installed on a machine, any coding agent that can run local shell commands can theoretically use it as a memory layer. Today that means Claude Code and Codex are the concrete first-class examples; other CLI-capable agents can use the same interface as long as they can execute local commands and read the output.

---

Install

One command on macOS and Linux (including WSL):

pip install cc-anywhere
cc-anywhere --init

Prefer pipx, or pip blocked by externally-managed-environment? pipx install cc-anywhere works the same.

--init is idempotent and does three things:

1. Captures every existing Claude Code / Codex / Gemini session into the local SQLite DB and builds the search index.
2. Wires SessionStart + Stop hooks into ~/.claude/settings.json so future sessions auto-load past context and capture on exit. Existing hooks are preserved, never replaced.
3. Sets up an hourly capture safety net (launchd on macOS, cron on Linux).

以上为 README 的开头部分。其余内容请阅读原文。 查看完整 README ↗