chat-memory-sync 0.1.3__py3-none-any.whl

chat_memory_sync-0.1.3.dist-info/METADATA

@@ -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.dist-info/RECORD

@@ -0,0 +1,13 @@
+chat_memory_sync/__init__.py,sha256=6rWdLf8_K9ddrf-lqnbCtzb4NKzZzwjY_OcC6VUoCsc,103
+chat_memory_sync/__main__.py,sha256=2ExmvLBObyZQez6mTNIG2PKwUGjSu4RV73bwdy-YNRA,87
+chat_memory_sync/cli.py,sha256=W6Dzb4J2RuCm3DMf8Y2qrH1rNneWFazGhgn_qKzozSw,2237
+chat_memory_sync/cmlib.py,sha256=XxVwXPrJeTSbif9XAc_LWfoRJ2JekD00SlFqBrLRCbQ,2069
+chat_memory_sync/install.py,sha256=uytL0iNyqhKAOPmPDJj1K8mIxec2jPVE3UXilf_SuLE,9149
+chat_memory_sync/recall.py,sha256=RHkKV77sNVG5PYQrL7KD5sTh2fEGl8Sipi3_3Z7nQdI,8892
+chat_memory_sync/run.py,sha256=pXn5qEeUkORcGiZ7M1Qp0ieS1AcBpWMdrwB3CZvwBTM,3037
+chat_memory_sync/sync.py,sha256=ekNcRojQ4IugUdFYdpGKkuyDqMrX_6FF0FWeMBtTqQU,39044
+chat_memory_sync-0.1.3.dist-info/METADATA,sha256=Qns82ydT8a_v8UyAX_c4uy1SZmlvB9MgFLFHB_r_b4Q,8379
+chat_memory_sync-0.1.3.dist-info/WHEEL,sha256=2iZrJkDIkeDh0k9SikKMqFuRP-ua6mb4Ir1AsER4BEw,87
+chat_memory_sync-0.1.3.dist-info/entry_points.txt,sha256=wSYpQfn74zfhmOmCzSafBsR6eZXbnRkpTnVBmnHEAcE,96
+chat_memory_sync-0.1.3.dist-info/licenses/LICENSE,sha256=rl9AmolPLExELNf7mZEkUEtEsRD95JbA8cVIoQgdV-o,1070
+chat_memory_sync-0.1.3.dist-info/RECORD,,

chat_memory_sync-0.1.3.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: hatchling 1.33.0
+Root-Is-Purelib: true
+Tag: py3-none-any

chat_memory_sync-0.1.3.dist-info/entry_points.txt

@@ -0,0 +1,3 @@
+[console_scripts]
+chat-memory = chat_memory_sync.cli:main
+recall = chat_memory_sync.recall:main

chat_memory_sync-0.1.3.dist-info/licenses/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.