teammate-sync 0.1.0__tar.gz

teammate_sync-0.1.0/PKG-INFO

@@ -0,0 +1,151 @@
+Metadata-Version: 2.4
+Name: teammate-sync
+Version: 0.1.0
+Summary: Cross-engineer Claude Code context sharing — type /share, your teammate queries your context.
+Author-email: Om Divyatej <om@turgon.ai>
+License: MIT
+Project-URL: Homepage, https://omdivyatej.github.io/teammate-sync-site/
+Project-URL: Source, https://github.com/omdivyatej/teammate-sync
+Keywords: claude,claude-code,mcp,team,context,sharing
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+Requires-Dist: mcp>=1.0.0
+Requires-Dist: anthropic>=0.40.0
+Requires-Dist: watchdog>=4.0.0
+Requires-Dist: httpx>=0.27
+
+# teammate-sync
+
+**Cross-engineer Claude Code context sharing.** Your teammate types `/share`
+in their Claude Code session. From your own terminal, your Claude can ask
+theirs anything and gets back a cited answer in seconds.
+
+No pasted transcripts. No GitHub pushes. No shared bucket setup.
+
+- Landing: https://omdivyatej.github.io/teammate-sync-site/
+- Source: https://github.com/omdivyatej/teammate-sync
+
+---
+
+## The problem
+
+You and your teammate are both using Claude Code on the same project. You
+need to know what they decided about the database schema, or which file
+they touched, or why they picked one library over another.
+
+Today, two bad options:
+
+1. **Ping them on Slack and wait.** Forty-five minutes of context-switching.
+2. **Get them to send their session transcript.** Their `.jsonl` is 50k
+   lines. You paste it into your Claude and immediately blow past the
+   200k token context window.
+
+`teammate-sync` is the third option: their Claude becomes a queryable
+context server. Your Claude calls it, gets back a cited synthesis, your
+context window stays clean.
+
+## Install
+
+```
+pip install teammate-sync
+teammate-sync init
+teammate-sync daemon
+```
+
+That's it. Full setup walkthrough: [INSTALL.md](INSTALL.md).
+
+`init` opens GitHub OAuth (your workspace = your GitHub org, no separate
+account), installs the `/share` slash commands into `~/.claude/commands/`,
+wires session lifecycle hooks into `~/.claude/settings.json`, and registers
+the MCP server. `daemon` runs in the foreground in a terminal you leave open.
+
+## How sharing works
+
+```
+/share                              in any Claude Code session
+```
+
+Daemon log immediately prints `share-mode ACTIVATED -> uploading`. That
+session's `.jsonl` plus your `CLAUDE.md` start syncing to your team's
+backend in real time as you work.
+
+```
+/unshare                            same session
+```
+
+Daemon wipes that session's content from the backend immediately.
+
+```
+/shared                             any session
+```
+
+Lists which sessions are currently shared.
+
+## How teammates query you
+
+From any Claude Code session in your org, your teammate types:
+
+> Use `mcp__teammate-sync__query_teammate_context` with
+> `teammate=<your-github-handle>` and `question="..."`
+
+The MCP server pulls your active-session state + your shared session
+transcripts, hands them to a Claude Sonnet synthesis call, and returns a
+cited answer. Citations point to specific session IDs and file names so
+they can verify.
+
+## Privacy model
+
+Default: **nothing is shared.** The daemon is running but idle.
+
+- **Sessions** are opted in one at a time via `/share`. Unshared sessions
+  never leave your machine, no matter how many you have running.
+- **Your GitHub OAuth token** sits in `~/.teammate-sync/auth.json` (mode
+  0600) and is **never** in the synced tree.
+- **Your org** is the unit of trust. Only members of your GitHub org can
+  query you. Discovery happens via the GitHub API, no manual invites.
+
+## What syncs where
+
+| Path | What it holds | Synced to cloud? |
+| ---- | ------------- | --------------- |
+| `~/.teammate-sync/auth.json` | Your GitHub OAuth token | **NEVER** (local only) |
+| `~/.teammate-sync/state/.shared-sessions.json` | List of currently-shared session IDs | No (local gate) |
+| `~/.teammate-sync/state/.active-sessions.json` | Which sessions are active right now (cwd, last activity) | Yes |
+| `~/.claude/projects/<encoded-cwd>/<sid>.jsonl` | Claude Code session transcripts | Only `/share`'d ones |
+
+## CLI
+
+| | |
+|---|---|
+| `teammate-sync init` | First-run setup. Re-runnable to refresh hooks / slash commands. |
+| `teammate-sync daemon` | Run the sync daemon (foreground). |
+| `teammate-sync share` / `unshare` / `shared` | Same as the slash commands, from any shell. |
+| `teammate-sync whoami` | Show your identity + workspace. |
+| `teammate-sync teammates` | List members of your workspace org. |
+| `teammate-sync logout` | Delete `~/.teammate-sync/auth.json`. |
+
+## Requirements
+
+- Python 3.11+
+- [Claude Code](https://docs.claude.com/en/docs/claude-code) CLI
+- `ANTHROPIC_API_KEY` exported in your shell (used by the MCP server's
+  synthesis calls)
+
+## Status
+
+Public beta. Backend runs on Fly.io (Singapore region, single-region by
+design — synthesis latency is dominated by Anthropic API not by storage).
+Per-session opt-in (`/share` / `/unshare`) is the privacy model; there is
+no "everything sync" mode and there won't be.
+
+## License
+
+MIT — see [LICENSE](LICENSE) if present, or `pyproject.toml`.

teammate_sync-0.1.0/README.md

@@ -0,0 +1,127 @@
+# teammate-sync
+
+**Cross-engineer Claude Code context sharing.** Your teammate types `/share`
+in their Claude Code session. From your own terminal, your Claude can ask
+theirs anything and gets back a cited answer in seconds.
+
+No pasted transcripts. No GitHub pushes. No shared bucket setup.
+
+- Landing: https://omdivyatej.github.io/teammate-sync-site/
+- Source: https://github.com/omdivyatej/teammate-sync
+
+---
+
+## The problem
+
+You and your teammate are both using Claude Code on the same project. You
+need to know what they decided about the database schema, or which file
+they touched, or why they picked one library over another.
+
+Today, two bad options:
+
+1. **Ping them on Slack and wait.** Forty-five minutes of context-switching.
+2. **Get them to send their session transcript.** Their `.jsonl` is 50k
+   lines. You paste it into your Claude and immediately blow past the
+   200k token context window.
+
+`teammate-sync` is the third option: their Claude becomes a queryable
+context server. Your Claude calls it, gets back a cited synthesis, your
+context window stays clean.
+
+## Install
+
+```
+pip install teammate-sync
+teammate-sync init
+teammate-sync daemon
+```
+
+That's it. Full setup walkthrough: [INSTALL.md](INSTALL.md).
+
+`init` opens GitHub OAuth (your workspace = your GitHub org, no separate
+account), installs the `/share` slash commands into `~/.claude/commands/`,
+wires session lifecycle hooks into `~/.claude/settings.json`, and registers
+the MCP server. `daemon` runs in the foreground in a terminal you leave open.
+
+## How sharing works
+
+```
+/share                              in any Claude Code session
+```
+
+Daemon log immediately prints `share-mode ACTIVATED -> uploading`. That
+session's `.jsonl` plus your `CLAUDE.md` start syncing to your team's
+backend in real time as you work.
+
+```
+/unshare                            same session
+```
+
+Daemon wipes that session's content from the backend immediately.
+
+```
+/shared                             any session
+```
+
+Lists which sessions are currently shared.
+
+## How teammates query you
+
+From any Claude Code session in your org, your teammate types:
+
+> Use `mcp__teammate-sync__query_teammate_context` with
+> `teammate=<your-github-handle>` and `question="..."`
+
+The MCP server pulls your active-session state + your shared session
+transcripts, hands them to a Claude Sonnet synthesis call, and returns a
+cited answer. Citations point to specific session IDs and file names so
+they can verify.
+
+## Privacy model
+
+Default: **nothing is shared.** The daemon is running but idle.
+
+- **Sessions** are opted in one at a time via `/share`. Unshared sessions
+  never leave your machine, no matter how many you have running.
+- **Your GitHub OAuth token** sits in `~/.teammate-sync/auth.json` (mode
+  0600) and is **never** in the synced tree.
+- **Your org** is the unit of trust. Only members of your GitHub org can
+  query you. Discovery happens via the GitHub API, no manual invites.
+
+## What syncs where
+
+| Path | What it holds | Synced to cloud? |
+| ---- | ------------- | --------------- |
+| `~/.teammate-sync/auth.json` | Your GitHub OAuth token | **NEVER** (local only) |
+| `~/.teammate-sync/state/.shared-sessions.json` | List of currently-shared session IDs | No (local gate) |
+| `~/.teammate-sync/state/.active-sessions.json` | Which sessions are active right now (cwd, last activity) | Yes |
+| `~/.claude/projects/<encoded-cwd>/<sid>.jsonl` | Claude Code session transcripts | Only `/share`'d ones |
+
+## CLI
+
+| | |
+|---|---|
+| `teammate-sync init` | First-run setup. Re-runnable to refresh hooks / slash commands. |
+| `teammate-sync daemon` | Run the sync daemon (foreground). |
+| `teammate-sync share` / `unshare` / `shared` | Same as the slash commands, from any shell. |
+| `teammate-sync whoami` | Show your identity + workspace. |
+| `teammate-sync teammates` | List members of your workspace org. |
+| `teammate-sync logout` | Delete `~/.teammate-sync/auth.json`. |
+
+## Requirements
+
+- Python 3.11+
+- [Claude Code](https://docs.claude.com/en/docs/claude-code) CLI
+- `ANTHROPIC_API_KEY` exported in your shell (used by the MCP server's
+  synthesis calls)
+
+## Status
+
+Public beta. Backend runs on Fly.io (Singapore region, single-region by
+design — synthesis latency is dominated by Anthropic API not by storage).
+Per-session opt-in (`/share` / `/unshare`) is the privacy model; there is
+no "everything sync" mode and there won't be.
+
+## License
+
+MIT — see [LICENSE](LICENSE) if present, or `pyproject.toml`.

teammate_sync-0.1.0/pyproject.toml

@@ -0,0 +1,48 @@
+[build-system]
+requires = ["setuptools>=68", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "teammate-sync"
+version = "0.1.0"
+description = "Cross-engineer Claude Code context sharing — type /share, your teammate queries your context."
+readme = "README.md"
+requires-python = ">=3.11"
+license = { text = "MIT" }
+authors = [
+    { name = "Om Divyatej", email = "om@turgon.ai" },
+]
+keywords = ["claude", "claude-code", "mcp", "team", "context", "sharing"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Environment :: Console",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: MIT License",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Software Development",
+]
+dependencies = [
+    "mcp>=1.0.0",
+    "anthropic>=0.40.0",
+    "watchdog>=4.0.0",
+    "httpx>=0.27",
+]
+
+[project.urls]
+Homepage = "https://omdivyatej.github.io/teammate-sync-site/"
+Source = "https://github.com/omdivyatej/teammate-sync"
+
+[project.scripts]
+# `pip install` puts this on the user's PATH. All functionality is reachable
+# via subcommands: init, daemon, share, unshare, shared, whoami, teammates,
+# install-commands, logout.
+teammate-sync = "teammate_sync.cli:main"
+
+[tool.setuptools]
+# Single flat module layout under teammate_sync/.
+packages = ["teammate_sync"]
+
+[tool.setuptools.package-dir]
+teammate_sync = "teammate_sync"

teammate_sync-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

teammate_sync-0.1.0/teammate_sync/auth.py

@@ -0,0 +1,51 @@
+"""
+Auth helper for teammate-sync clients (daemon + MCP).
+
+Reads ~/.teammate-sync/auth.json, written by `teammate-sync init` (Phase 5c).
+Format:
+    {
+      "token":       "gho_...",                   # GitHub OAuth access token
+      "org":         "SolarCheckr",               # workspace = GitHub org name
+      "backend_url": "https://teammate-sync-backend.fly.dev"
+    }
+"""
+import json
+import os
+from pathlib import Path
+
+
+DEFAULT_AUTH_FILE = "~/.teammate-sync/auth.json"
+DEFAULT_BACKEND_URL = "https://teammate-sync-backend.fly.dev"
+
+
+def auth_file_path() -> Path:
+    return Path(os.environ.get("TEAMMATE_AUTH_FILE", DEFAULT_AUTH_FILE)).expanduser()
+
+
+def read_auth() -> dict:
+    """Read the auth file. Raises with a clear message if missing or malformed."""
+    path = auth_file_path()
+    if not path.exists():
+        raise FileNotFoundError(
+            f"teammate-sync auth file not found at {path}.\n"
+            f"Run `teammate-sync init` to sign in with GitHub and create it."
+        )
+    try:
+        data = json.loads(path.read_text())
+    except json.JSONDecodeError as e:
+        raise ValueError(f"Auth file {path} is not valid JSON: {e}")
+    for required in ("token", "org"):
+        if not data.get(required):
+            raise ValueError(f"Auth file {path} missing required field: {required!r}")
+    data.setdefault("backend_url", DEFAULT_BACKEND_URL)
+    return data
+
+
+def write_auth(token: str, org: str, backend_url: str = DEFAULT_BACKEND_URL) -> Path:
+    """Persist the auth file with restrictive permissions (0600)."""
+    path = auth_file_path()
+    path.parent.mkdir(parents=True, exist_ok=True)
+    payload = {"token": token, "org": org, "backend_url": backend_url}
+    path.write_text(json.dumps(payload, indent=2))
+    path.chmod(0o600)
+    return path