chat-memory-sync 0.1.3__tar.gz

chat_memory_sync-0.1.3/.gitignore

@@ -0,0 +1,8 @@
+__pycache__/
+*.pyc
+.DS_Store
+**/.DS_Store
+build/
+dist/
+*.egg-info/
+.venv/

chat_memory_sync-0.1.3/CODE_OF_CONDUCT.md

@@ -0,0 +1,36 @@
+# Code of Conduct
+
+## Our pledge
+
+We as members, contributors, and maintainers pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body size,
+visible or invisible disability, ethnicity, sex characteristics, gender identity and
+expression, level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our standards
+
+Examples of behavior that contributes to a positive environment:
+
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Focusing on what is best for the community
+- Showing empathy toward other community members
+
+Unacceptable behavior includes:
+
+- Harassment, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information without explicit permission
+- Other conduct which could reasonably be considered inappropriate
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to
+the maintainers via a GitHub issue or direct contact. All complaints will be reviewed
+and investigated promptly and fairly. Maintainers are obligated to respect the privacy
+and security of the reporter of any incident.
+
+This Code of Conduct is adapted from the [Contributor Covenant][cc], version 2.1.
+
+[cc]: https://www.contributor-covenant.org/version/2/1/code_of_conduct/

chat_memory_sync-0.1.3/CONTRIBUTING.md

@@ -0,0 +1,123 @@
+# Contributing to chat-memory-sync
+
+Thanks for helping! The whole point of this project is that **no one person can keep up
+with every AI coding harness** — so adapters are community-driven. Most contributions
+are a single new adapter function.
+
+- 🐛 **Found a bug?** Open an issue.
+- 🔌 **Want a harness supported?** Open a *Harness request* issue (even if you can't code
+  it — the storage-location details are the hard part, and you can help gather them).
+- 🛠 **Adding/​fixing an adapter?** Read ["Adding a harness"](#adding-a-harness) below.
+
+By contributing you agree your work is licensed under the repo's [MIT License](LICENSE)
+and that you follow the [Code of Conduct](CODE_OF_CONDUCT.md).
+
+## Project shape
+
+| File | Role |
+| ---- | ---- |
+| `cmlib.py` | config + paths (data dir, state dir, client) |
+| `sync.py` | **harness adapters** + Markdown writer + index builder |
+| `run.py` | runner: git pull → sync → commit → push |
+| `recall.py` | full-text search |
+| `install.py` | installer + schedulers |
+
+No dependencies beyond the Python standard library (`sqlite3`, `json`, `glob`, …). Please
+keep it that way — this has to run anywhere with just `python3` + `git`.
+
+## Adding a harness
+
+A harness adapter is a generator in `sync.py` that reads that tool's native chat store
+and `yield`s normalized chat dicts. Everything else (writing Markdown, project grouping,
+client tagging, indexing, syncing) is handled for you.
+
+### 1. Find where the harness stores chats
+
+This is usually the biggest part. Look under:
+
+- `~/.<tool>/`, `~/.config/<tool>/`, `~/.local/share/<tool>/`
+- macOS: `~/Library/Application Support/<Tool>/`
+- VS Code forks: `…/<Tool>/User/globalStorage/state.vscdb` + `workspaceStorage/`
+
+Chats are usually **JSONL** (one event/message per line), a **SQLite DB**, or per-session
+**JSON** files. Record the exact path and format in your PR/issue so others can verify.
+
+### 2. Write the adapter
+
+Yield one dict per conversation:
+
+```python
+{
+  "harness": "myharness",            # short, kebab-case; becomes a folder name
+  "id": "<stable session id>",       # unique per chat (used in the filename)
+  "project": canonical_project(cwd), # use the helper; maps cwd → repo name
+  "source_path": cwd,                # absolute path the chat ran in (may be "")
+  "title": "<short title>",          # first user line is fine if none stored
+  "created": <epoch_ms>,             # use toms(...) to normalize ISO/sec/ms
+  "updated": <epoch_ms>,
+  "models": {"model-name"},          # set(); may be empty
+  "messages": [
+    {
+      "role": "user" | "assistant",
+      "model": "",                   # optional, per-message
+      "thinking": "",                # reasoning text, optional
+      "text": "...",                 # main content
+      "tools": [                     # tool calls, optional
+        {"name": "Shell", "args": {...} | "raw", "result": "..." | None},
+      ],
+    },
+  ],
+}
+```
+
+Then register it:
+
+```python
+ADAPTERS = [cursor_chats, ..., myharness_chats]
+```
+
+Guidelines:
+
+- **Skip empties** — don't yield chats with no renderable messages.
+- **OS-aware paths** — branch on `platform.system()` or probe candidate paths with
+  `_first_existing(...)`; degrade gracefully (just `return` if the store isn't present).
+- **Don't crash the run** — wrap risky parsing in `try/except`; a bad file should skip,
+  not abort. (Adapters are already isolated, but be defensive.)
+- **Timestamps** via `toms(...)`; **project** via `canonical_project(...)`.
+- **Truncate** giant tool args/results if needed (the writer already caps them).
+
+### 3. Test it
+
+```bash
+# point at a throwaway data dir so you don't touch your real one
+export CHAT_MEMORY_DATA_DIR=/tmp/cm-test CHAT_MEMORY_HOME=/tmp/cm-home
+python3 sync.py
+ls -R /tmp/cm-test/projects            # inspect the generated Markdown
+```
+
+Check: titles are sensible, messages are ordered, projects resolve, no tracebacks.
+Run twice — the second run should report everything `unchanged` (idempotent).
+
+### 4. Open a PR
+
+Include:
+
+- [ ] the adapter + `ADAPTERS` entry
+- [ ] the harness's storage path/format in the PR description
+- [ ] a row added to the **Harness support** table in `README.md`
+- [ ] (if the format is non-obvious) a short note in the PR on how you decoded it
+
+## Style
+
+- Standard library only, Python 3.8+.
+- Match the surrounding style (no formatter enforced; keep it clean and readable).
+- Keep adapters self-contained and defensive.
+
+## Not a coder? Still useful.
+
+Open a **Harness request** issue with:
+- the tool name + link
+- where it stores chats on your OS (paths)
+- one small (redacted) example file
+
+That alone makes it easy for someone else to write the adapter.

chat_memory_sync-0.1.3/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Aayush Gautam
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

chat_memory_sync-0.1.3/PKG-INFO

@@ -0,0 +1,204 @@
+Metadata-Version: 2.5
+Name: chat-memory-sync
+Version: 0.1.3
+Summary: Unified, searchable memory bank of your AI coding chats across Cursor, Claude Code, OpenCode, Codex, Gemini CLI, Pi and more — synced across machines.
+Project-URL: Homepage, https://github.com/insideaayush/chat-memory-sync
+Project-URL: Repository, https://github.com/insideaayush/chat-memory-sync
+Project-URL: Issues, https://github.com/insideaayush/chat-memory-sync/issues
+Author: Aayush Gautam
+License-Expression: MIT
+License-File: LICENSE
+Keywords: ai,chat-history,claude-code,cli,codex,cursor,developer-tools,gemini,memory,opencode
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development
+Classifier: Topic :: Utilities
+Requires-Python: >=3.8
+Description-Content-Type: text/markdown
+
+# chat-memory-sync
+
+Turn your AI coding assistants' chat history into a unified, searchable **memory bank**.
+
+`chat-memory-sync` exports conversations from every AI coding harness you use into one
+project-organized Markdown repo, syncs it across all your machines via git, and gives
+agents a `recall` command to look up relevant past chats — so an assistant working on a
+feature can learn from what you discussed about it in a *different* tool weeks ago.
+
+- **Many harnesses** → one place: Cursor, Cursor Agent CLI, Claude Code, OpenCode, Pi,
+  Codex, Gemini CLI. (Antigravity is stubbed — opaque local store.)
+- **Project-organized** so memory is scoped to the repo you're in (worktrees/sub-apps
+  merged into the parent repo).
+- **Multi-machine** via a *client* dimension (mac / pc / cloud) — each machine syncs
+  independently; no machine ever clobbers another's chats.
+- **Private by design**: the tooling is open source; your chats live in a **separate
+  private data repo** you own.
+- **Incremental & idempotent**: only changed chats are rewritten; updates to old chats
+  are picked up; deleted chats are pruned.
+
+## How it's split
+
+| Repo | Visibility | Contents |
+| ---- | ---------- | -------- |
+| **chat-memory-sync** (this) | public | the scripts + installer + background job |
+| **your data repo** (e.g. `chat-memory`) | **private** | `projects/` + `INDEX.md` (your chats) |
+
+The tool reads `~/.config/chat-memory/config.json` for your data repo's location.
+Machine-local state (search index, client name, logs) also lives under
+`~/.config/chat-memory/` — never inside the data repo.
+
+## Install
+
+Get the `chat-memory` CLI (pure Python, no dependencies):
+
+```bash
+# Homebrew
+brew install insideaayush/tap/chat-memory-sync
+
+# pipx (recommended for pip users)
+pipx install chat-memory-sync
+
+# pip
+pip install --user chat-memory-sync
+
+# from source
+git clone https://github.com/insideaayush/chat-memory-sync.git
+pip install ./chat-memory-sync
+```
+
+Then set it up on this machine:
+
+```bash
+chat-memory install \
+    --data-remote git@github.com:<you>/chat-memory.git \
+    --client "macbook-air" \
+    --time 21:00
+```
+
+That one command: writes config, clones (or inits) your private data repo, runs the
+first sync, registers a **daily background job** for your OS, and ensures the `recall`
+command is available.
+
+### Commands
+
+```
+chat-memory install   # config + data repo + daily job + recall
+chat-memory sync      # pull -> export -> commit -> push (what the job runs)
+chat-memory export    # export only (no git)
+chat-memory recall …  # search past chats (also the standalone `recall` command)
+chat-memory doctor    # config, detected harnesses, chat counts
+```
+
+| OS | Background job |
+| -- | -------------- |
+| macOS | launchd LaunchAgent `com.user.chat-memory-sync` |
+| Windows | Task Scheduler task `ChatMemorySync` |
+| Linux | systemd **user** timer (falls back to cron) |
+
+Only needs `git` + `python3`. Re-running `chat-memory install` is safe.
+
+> No private data repo yet? Create an empty **private** repo on your git host first,
+> then pass its URL as `--data-remote`. Or omit `--data-remote` to keep it local-only.
+
+Releases are automated (PyPI + Homebrew) — see [RELEASING.md](RELEASING.md).
+
+## Finding relevant chats — `recall`
+
+```bash
+cd ~/code/my-project
+recall "auth token refresh"        # ranked (BM25) hits for THIS repo, with snippets
+recall "rate limiting" --all       # every project
+recall "payout bug" --harness cursor --since 2026-09 -k 10
+recall "..." --full                # just file paths (pipe-friendly)
+```
+
+Auto-scopes to the project you're in (via CWD), builds a local SQLite full-text index
+that rebuilds when chats change. The index is machine-local (`~/.config/chat-memory/
+index.db`), never synced.
+
+**For agents:** run `recall "<topic>"` from the repo you're working in, read the top
+hits, then open those `.md` files for full context. Add a line to your project's
+`AGENTS.md`/`CLAUDE.md` so assistants do this automatically.
+
+## Multi-machine
+
+Every machine runs the same job independently. Each run:
+
+1. `git pull --rebase` the data repo (other machines' chats)
+2. export **this** machine's chats (tagged with its `client` id)
+3. prune only **this client's** deleted chats
+4. rebuild indexes from the union, `git commit`, `git push`
+
+Set a machine's name with `--client` (default: hostname), or
+`CHAT_MEMORY_CLIENT=cloud-vm`.
+
+## Harness support
+
+Legend: ✅ supported · 🧪 partial · 🔜 stub/planned · ❓ wanted (help us!)
+
+| Harness | Status | Source | Notes |
+| ------- | :----: | ------ | ----- |
+| Cursor | ✅ | `…/Cursor/User/globalStorage/state.vscdb` (OS-aware) | IDE chats / composers |
+| Cursor Agent CLI | ✅ | `~/.cursor/acp-sessions/<uuid>/store.db` + `meta.json` | blob store |
+| Claude Code | ✅ | `~/.claude/projects/<enc>/<uuid>.jsonl` | |
+| OpenCode | ✅ | `~/.local/share/opencode/opencode.db` | |
+| Pi | ✅ | `~/.pi/agent/sessions/<enc>/<ts>_<id>.jsonl` | |
+| Codex | ✅ | `~/.codex/sessions/**/rollout-*.jsonl` (+ `archived_sessions/`) | |
+| Gemini CLI | 🧪 | `~/.gemini/tmp/<key>/checkpoint-*.json` (+ `logs.json`) | full via checkpoints; else prompts only |
+| Antigravity | 🔜 | opaque protobuf LevelDB (`shared_proto_db`) | needs a decoder |
+| Windsurf, Aider, Cline, Continue, Zed, Copilot Chat, … | ❓ | — | [request](../../issues/new?template=harness_request.md) or PR |
+
+Can't track every tool in the world — **adapters are community-driven**. Adding one is
+usually a single function; see **[CONTRIBUTING.md](CONTRIBUTING.md)** and the
+**[ROADMAP](ROADMAP.md)**.
+
+## How it works
+
+| File | Role |
+| ---- | ---- |
+| `cmlib.py` | config + paths (data dir, state dir, client) |
+| `sync.py` | export every harness's native store → Markdown; rebuild indexes |
+| `run.py` | runner: `git pull → sync → commit → push` (+ warms recall index) |
+| `recall.py` | full-text (BM25) search, auto-scoped to the current project |
+| `install.py` | one-command setup + scheduler + `recall` command |
+
+### Adding a harness
+
+Adapters are community-driven — adding one is usually a single generator function in
+`sync.py`. See **[CONTRIBUTING.md](CONTRIBUTING.md)** for the full contract and the
+support table above.
+
+## Config reference
+
+`~/.config/chat-memory/config.json`:
+
+```json
+{ "data_dir": "/Users/you/chat-memory", "client": "macbook-air" }
+```
+
+Env overrides: `CHAT_MEMORY_DATA_DIR`, `CHAT_MEMORY_CLIENT`, `CHAT_MEMORY_HOME`.
+
+## Give your agents memory
+
+Any assistant with shell access can query all your past chats via `recall`. Add a short
+snippet to your project's `AGENTS.md` / `CLAUDE.md` / `GEMINI.md` so assistants do it
+automatically — copy-paste blocks per harness are in
+**[docs/agent-integration.md](docs/agent-integration.md)**.
+
+## Contributing & community
+
+- **[CONTRIBUTING.md](CONTRIBUTING.md)** — add a harness adapter (the main ask) or fix a bug.
+- **[ROADMAP.md](ROADMAP.md)** — planned work; pick anything up.
+- **[CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md)**.
+- Not a coder? A [harness request](../../issues/new?template=harness_request.md) with
+  storage paths + a redacted sample is hugely useful.
+
+## License
+
+MIT — see [LICENSE](LICENSE). Contributions accepted under the same license.
+
+> The tooling is open source; **your chats stay in your own private data repo.**
+> This project reads local chat stores and writes Markdown — review the code before running it.

chat_memory_sync-0.1.3/README.md

@@ -0,0 +1,183 @@
+# chat-memory-sync
+
+Turn your AI coding assistants' chat history into a unified, searchable **memory bank**.
+
+`chat-memory-sync` exports conversations from every AI coding harness you use into one
+project-organized Markdown repo, syncs it across all your machines via git, and gives
+agents a `recall` command to look up relevant past chats — so an assistant working on a
+feature can learn from what you discussed about it in a *different* tool weeks ago.
+
+- **Many harnesses** → one place: Cursor, Cursor Agent CLI, Claude Code, OpenCode, Pi,
+  Codex, Gemini CLI. (Antigravity is stubbed — opaque local store.)
+- **Project-organized** so memory is scoped to the repo you're in (worktrees/sub-apps
+  merged into the parent repo).
+- **Multi-machine** via a *client* dimension (mac / pc / cloud) — each machine syncs
+  independently; no machine ever clobbers another's chats.
+- **Private by design**: the tooling is open source; your chats live in a **separate
+  private data repo** you own.
+- **Incremental & idempotent**: only changed chats are rewritten; updates to old chats
+  are picked up; deleted chats are pruned.
+
+## How it's split
+
+| Repo | Visibility | Contents |
+| ---- | ---------- | -------- |
+| **chat-memory-sync** (this) | public | the scripts + installer + background job |
+| **your data repo** (e.g. `chat-memory`) | **private** | `projects/` + `INDEX.md` (your chats) |
+
+The tool reads `~/.config/chat-memory/config.json` for your data repo's location.
+Machine-local state (search index, client name, logs) also lives under
+`~/.config/chat-memory/` — never inside the data repo.
+
+## Install
+
+Get the `chat-memory` CLI (pure Python, no dependencies):
+
+```bash
+# Homebrew
+brew install insideaayush/tap/chat-memory-sync
+
+# pipx (recommended for pip users)
+pipx install chat-memory-sync
+
+# pip
+pip install --user chat-memory-sync
+
+# from source
+git clone https://github.com/insideaayush/chat-memory-sync.git
+pip install ./chat-memory-sync
+```
+
+Then set it up on this machine:
+
+```bash
+chat-memory install \
+    --data-remote git@github.com:<you>/chat-memory.git \
+    --client "macbook-air" \
+    --time 21:00
+```
+
+That one command: writes config, clones (or inits) your private data repo, runs the
+first sync, registers a **daily background job** for your OS, and ensures the `recall`
+command is available.
+
+### Commands
+
+```
+chat-memory install   # config + data repo + daily job + recall
+chat-memory sync      # pull -> export -> commit -> push (what the job runs)
+chat-memory export    # export only (no git)
+chat-memory recall …  # search past chats (also the standalone `recall` command)
+chat-memory doctor    # config, detected harnesses, chat counts
+```
+
+| OS | Background job |
+| -- | -------------- |
+| macOS | launchd LaunchAgent `com.user.chat-memory-sync` |
+| Windows | Task Scheduler task `ChatMemorySync` |
+| Linux | systemd **user** timer (falls back to cron) |
+
+Only needs `git` + `python3`. Re-running `chat-memory install` is safe.
+
+> No private data repo yet? Create an empty **private** repo on your git host first,
+> then pass its URL as `--data-remote`. Or omit `--data-remote` to keep it local-only.
+
+Releases are automated (PyPI + Homebrew) — see [RELEASING.md](RELEASING.md).
+
+## Finding relevant chats — `recall`
+
+```bash
+cd ~/code/my-project
+recall "auth token refresh"        # ranked (BM25) hits for THIS repo, with snippets
+recall "rate limiting" --all       # every project
+recall "payout bug" --harness cursor --since 2026-09 -k 10
+recall "..." --full                # just file paths (pipe-friendly)
+```
+
+Auto-scopes to the project you're in (via CWD), builds a local SQLite full-text index
+that rebuilds when chats change. The index is machine-local (`~/.config/chat-memory/
+index.db`), never synced.
+
+**For agents:** run `recall "<topic>"` from the repo you're working in, read the top
+hits, then open those `.md` files for full context. Add a line to your project's
+`AGENTS.md`/`CLAUDE.md` so assistants do this automatically.
+
+## Multi-machine
+
+Every machine runs the same job independently. Each run:
+
+1. `git pull --rebase` the data repo (other machines' chats)
+2. export **this** machine's chats (tagged with its `client` id)
+3. prune only **this client's** deleted chats
+4. rebuild indexes from the union, `git commit`, `git push`
+
+Set a machine's name with `--client` (default: hostname), or
+`CHAT_MEMORY_CLIENT=cloud-vm`.
+
+## Harness support
+
+Legend: ✅ supported · 🧪 partial · 🔜 stub/planned · ❓ wanted (help us!)
+
+| Harness | Status | Source | Notes |
+| ------- | :----: | ------ | ----- |
+| Cursor | ✅ | `…/Cursor/User/globalStorage/state.vscdb` (OS-aware) | IDE chats / composers |
+| Cursor Agent CLI | ✅ | `~/.cursor/acp-sessions/<uuid>/store.db` + `meta.json` | blob store |
+| Claude Code | ✅ | `~/.claude/projects/<enc>/<uuid>.jsonl` | |
+| OpenCode | ✅ | `~/.local/share/opencode/opencode.db` | |
+| Pi | ✅ | `~/.pi/agent/sessions/<enc>/<ts>_<id>.jsonl` | |
+| Codex | ✅ | `~/.codex/sessions/**/rollout-*.jsonl` (+ `archived_sessions/`) | |
+| Gemini CLI | 🧪 | `~/.gemini/tmp/<key>/checkpoint-*.json` (+ `logs.json`) | full via checkpoints; else prompts only |
+| Antigravity | 🔜 | opaque protobuf LevelDB (`shared_proto_db`) | needs a decoder |
+| Windsurf, Aider, Cline, Continue, Zed, Copilot Chat, … | ❓ | — | [request](../../issues/new?template=harness_request.md) or PR |
+
+Can't track every tool in the world — **adapters are community-driven**. Adding one is
+usually a single function; see **[CONTRIBUTING.md](CONTRIBUTING.md)** and the
+**[ROADMAP](ROADMAP.md)**.
+
+## How it works
+
+| File | Role |
+| ---- | ---- |
+| `cmlib.py` | config + paths (data dir, state dir, client) |
+| `sync.py` | export every harness's native store → Markdown; rebuild indexes |
+| `run.py` | runner: `git pull → sync → commit → push` (+ warms recall index) |
+| `recall.py` | full-text (BM25) search, auto-scoped to the current project |
+| `install.py` | one-command setup + scheduler + `recall` command |
+
+### Adding a harness
+
+Adapters are community-driven — adding one is usually a single generator function in
+`sync.py`. See **[CONTRIBUTING.md](CONTRIBUTING.md)** for the full contract and the
+support table above.
+
+## Config reference
+
+`~/.config/chat-memory/config.json`:
+
+```json
+{ "data_dir": "/Users/you/chat-memory", "client": "macbook-air" }
+```
+
+Env overrides: `CHAT_MEMORY_DATA_DIR`, `CHAT_MEMORY_CLIENT`, `CHAT_MEMORY_HOME`.
+
+## Give your agents memory
+
+Any assistant with shell access can query all your past chats via `recall`. Add a short
+snippet to your project's `AGENTS.md` / `CLAUDE.md` / `GEMINI.md` so assistants do it
+automatically — copy-paste blocks per harness are in
+**[docs/agent-integration.md](docs/agent-integration.md)**.
+
+## Contributing & community
+
+- **[CONTRIBUTING.md](CONTRIBUTING.md)** — add a harness adapter (the main ask) or fix a bug.
+- **[ROADMAP.md](ROADMAP.md)** — planned work; pick anything up.
+- **[CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md)**.
+- Not a coder? A [harness request](../../issues/new?template=harness_request.md) with
+  storage paths + a redacted sample is hugely useful.
+
+## License
+
+MIT — see [LICENSE](LICENSE). Contributions accepted under the same license.
+
+> The tooling is open source; **your chats stay in your own private data repo.**
+> This project reads local chat stores and writes Markdown — review the code before running it.

chat_memory_sync-0.1.3/ROADMAP.md

@@ -0,0 +1,48 @@
+# Roadmap
+
+Ideas and planned work. Contributions welcome — pick anything, or open an issue to
+propose something. Ordering is rough priority, not a commitment.
+
+## Harness coverage
+
+- [ ] **Antigravity** — decode the Cascade protobuf LevelDB (`shared_proto_db`).
+- [ ] **Windsurf** (Cascade) — same family; likely similar store.
+- [ ] **Aider** — `.aider.chat.history.md` / input history.
+- [ ] **Cline / Roo Code** (VS Code) — task history in global/workspace storage.
+- [ ] **Continue.dev** — `~/.continue/sessions/`.
+- [ ] **Zed** — assistant/agent threads.
+- [ ] **GitHub Copilot Chat** — VS Code chat session JSON.
+- [ ] **Amp**, **Goose**, **Cody**, **Windmill**, … — PRs welcome.
+
+See [CONTRIBUTING.md](CONTRIBUTING.md#adding-a-harness) for the adapter contract.
+
+## Retrieval & memory quality
+
+- [ ] **MCP server** exposing `recall` as a tool, so MCP-capable harnesses can query
+      memory natively (no shell needed).
+- [ ] **Semantic search** option (local embeddings + vector index) alongside BM25.
+- [ ] **Cross-harness dedup** — collapse the same conversation captured by two tools.
+- [ ] **Per-chat summaries** / auto-tags in frontmatter for better ranking & scanning.
+- [ ] **Incremental indexing** (only re-index changed files) for very large histories.
+
+## Sync & scale
+
+- [ ] **Conflict-free multi-machine** hardening (large concurrent pushes).
+- [ ] **History/size management** — optional squash, or Git LFS for the data repo.
+- [ ] **Selective sync** — include/exclude projects or harnesses via config.
+- [ ] **Redaction/secret-scrubbing** pass before commit (configurable patterns).
+- [ ] **Encryption at rest** option for the data repo.
+
+## Tooling & DX
+
+- [ ] **`doctor` command** — verify config, detect installed harnesses, report counts.
+- [ ] **One-line installers** (curl | sh) per OS.
+- [ ] **CI** — lint + a smoke test that runs adapters against fixture data.
+- [ ] **Fixture corpus** — tiny redacted sample stores per harness for tests.
+- [ ] **Web/TUI browser** for the data repo.
+
+## Docs
+
+- [ ] Per-harness "where are my chats" reference with screenshots.
+- [ ] Example `AGENTS.md`/`CLAUDE.md` snippets per tool (started in
+      [docs/agent-integration.md](docs/agent-integration.md)).