overlapdev 1.7.4 → 1.7.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +48 -14
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -22,7 +22,7 @@ Developer uses Claude Code → writes JSONL session logs
22
22
  Overlap dashboard
23
23
  ```
24
24
 
25
- The tracer extracts **signals, not code**. File contents, assistant responses, and thinking blocks never leave your machine. See [Privacy](#privacy) for the full breakdown.
25
+ The tracer extracts **signals, not code**. File contents and tool outputs never leave your machine. Session metadata, prompts, and assistant responses are sent to your self-hosted Overlap instance. See [Privacy](#privacy) for the full breakdown.
26
26
 
27
27
  ## Install
28
28
 
@@ -65,8 +65,11 @@ overlap status
65
65
 
66
66
  ```bash
67
67
  overlap join # Join a team (prompts for instance URL + token)
68
+ overlap login # Open dashboard in browser
68
69
  overlap check # Check for team overlaps (used by Claude Code hook)
69
70
  overlap status # Show tracer status, teams, and tracked repos
71
+ overlap update # Update to the latest version
72
+ overlap backfill # Re-sync all sessions (optionally for one team)
70
73
  overlap leave # Leave a team
71
74
  overlap start # Start the tracer daemon
72
75
  overlap stop # Stop the tracer daemon
@@ -82,7 +85,7 @@ overlap version # Show version
82
85
 
83
86
  2. **The daemon watches `~/.claude/projects/`** for JSONL session files. When you start a Claude Code session in a repo that matches your team's registered repos, the tracer starts tailing the session file.
84
87
 
85
- 3. **Events are extracted, enriched, and batched** — session starts, file operations (with line ranges and function names), prompts, and session ends are parsed from JSONL lines, batched (every 2s or 50 events), and sent to your team's Overlap instance via `POST /api/v1/ingest`.
88
+ 3. **Events are extracted, enriched, and batched** — session starts, file operations (with line ranges and function names), prompts, and session ends are parsed from JSONL lines, batched (every 2s or 100 events), and sent to your team's Overlap instance via `POST /api/v1/ingest`.
86
89
 
87
90
  4. **The daemon polls for team state** — every 30 seconds, the daemon fetches active sessions from your team's instance and caches them locally at `~/.overlap/team-state.json`. This powers the real-time coordination hook.
88
91
 
@@ -120,18 +123,49 @@ The tracer is built on an agent adapter system — each agent gets its own parse
120
123
 
121
124
  ## Privacy
122
125
 
123
- | Sent to your team's Overlap instance | Stays on your machine |
124
- |--------------------------------------|----------------------|
125
- | Session ID, timestamps | Assistant response text |
126
- | Agent type, version | File contents |
127
- | File paths (relative, stripped of home dir) | Tool outputs / results |
128
- | Tool names (Write, Edit, Bash, etc.) | Thinking blocks |
129
- | User prompts | Full absolute paths |
130
- | Git branch name | API keys, env vars |
131
- | Cost, tokens, duration | System environment variables |
132
- | Model name | |
133
- | Bash commands | |
134
- | Hostname | |
126
+ Overlap has three data zones:
127
+
128
+ ### Stays on your machine
129
+
130
+ These are never sent anywhere not to your instance, not to overlap.dev:
131
+
132
+ - File contents (source code, diffs, file bodies)
133
+ - Tool outputs / results
134
+ - Full absolute paths (paths are stripped to relative before sending)
135
+ - API keys, env vars, system environment variables
136
+
137
+ ### Sent to your self-hosted instance
138
+
139
+ Sent to the Overlap dashboard you deployed on your own Cloudflare account:
140
+
141
+ - Session ID, timestamps, status
142
+ - Agent type, version, model name
143
+ - File paths (relative, home directory stripped)
144
+ - Tool names (Write, Edit, Bash, etc.)
145
+ - User prompts
146
+ - Assistant response text
147
+ - Thinking blocks
148
+ - Git branch name
149
+ - Cost, tokens, duration
150
+ - Bash commands
151
+ - Hostname
152
+
153
+ Your instance is under your control — you own the Cloudflare account, the D1 database, and the encryption keys.
154
+
155
+ ### Anonymous telemetry to overlap.dev
156
+
157
+ On startup and periodically, lightweight pings are sent to `overlap.dev` for version checks and anonymous usage stats:
158
+
159
+ | Data | Purpose |
160
+ |------|---------|
161
+ | Hashed instance URL | Anonymous instance counting |
162
+ | Hashed user token | Anonymous user counting |
163
+ | Tracer/dashboard version | Update notifications |
164
+ | OS, architecture | Platform analytics |
165
+ | User count, repo count | Aggregate usage (heartbeat only) |
166
+ | Overlap/warn/block counts | Feature adoption (heartbeat only) |
167
+
168
+ No session content, file paths, prompts, or response text is sent to overlap.dev. All identifiers are SHA-256 hashed and truncated. To opt out, block `overlap.dev` at the network level.
135
169
 
136
170
  ## Configuration
137
171
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "overlapdev",
3
- "version": "1.7.4",
3
+ "version": "1.7.5",
4
4
  "description": "Overlap - Stop your coding agents from writing conflicting code",
5
5
  "type": "module",
6
6
  "bin": {