@agent-watch-ai/edge 0.5.0 → 0.7.0
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.
- package/CHANGELOG.md +238 -7
- package/README.md +308 -8
- package/dist/billing/billing-mode.d.ts +37 -5
- package/dist/billing/billing-mode.js +28 -19
- package/dist/billing/constants/billing.constants.d.ts +0 -2
- package/dist/billing/constants/billing.constants.js +0 -2
- package/dist/billing/index.d.ts +2 -1
- package/dist/billing/index.js +1 -1
- package/dist/billing/session-billing.d.ts +3 -2
- package/dist/billing/session-billing.js +8 -8
- package/dist/billing/types/billing.types.d.ts +7 -0
- package/dist/capture/capture-env.d.ts +147 -0
- package/dist/capture/capture-env.js +301 -0
- package/dist/capture/captured-step.d.ts +88 -0
- package/dist/capture/captured-step.js +479 -0
- package/dist/capture/constants/capture.constants.d.ts +70 -0
- package/dist/capture/constants/capture.constants.js +72 -0
- package/dist/capture/launched-runs.d.ts +16 -0
- package/dist/capture/launched-runs.js +151 -0
- package/dist/capture/node.cjs +697 -0
- package/dist/capture/node.d.cts +32 -0
- package/dist/capture/python/sitecustomize.py +823 -0
- package/dist/capture/schemas/capture.schema.d.ts +35 -0
- package/dist/capture/schemas/capture.schema.js +31 -0
- package/dist/capture/types/capture.types.d.ts +20 -0
- package/dist/cli/constants/cli.constants.d.ts +2 -6
- package/dist/cli/constants/cli.constants.js +3 -7
- package/dist/cli/context.d.ts +19 -22
- package/dist/cli/context.js +23 -54
- package/dist/cli/doctor-run-capture.d.ts +13 -0
- package/dist/cli/doctor-run-capture.js +19 -0
- package/dist/cli/doctor.js +16 -67
- package/dist/cli/hook.d.ts +14 -0
- package/dist/cli/hook.js +40 -0
- package/dist/cli/index.d.ts +1 -1
- package/dist/cli/index.js +1 -1
- package/dist/cli/misc.js +10 -2
- package/dist/cli/replay.d.ts +33 -0
- package/dist/cli/replay.js +193 -0
- package/dist/cli/setup.d.ts +10 -2
- package/dist/cli/setup.js +154 -26
- package/dist/cli/status.js +45 -5
- package/dist/cli/toggle.js +10 -0
- package/dist/cli/types/cli.types.d.ts +15 -1
- package/dist/cli/uninstall.js +8 -22
- package/dist/cli.js +104 -17
- package/dist/config/config.d.ts +0 -2
- package/dist/config/config.js +0 -1
- package/dist/config/constants/config.constants.js +2 -0
- package/dist/config/events-transport.d.ts +15 -0
- package/dist/config/events-transport.js +29 -0
- package/dist/config/index.d.ts +2 -1
- package/dist/config/index.js +1 -0
- package/dist/config/root-config.d.ts +12 -0
- package/dist/config/root-config.js +24 -0
- package/dist/config/schemas/config.schema.d.ts +13 -0
- package/dist/config/schemas/config.schema.js +42 -6
- package/dist/config/types/config.types.d.ts +7 -0
- package/dist/core/index.d.ts +1 -1
- package/dist/core/index.js +1 -1
- package/dist/core/version.d.ts +9 -0
- package/dist/core/version.js +14 -0
- package/dist/core/which.d.ts +11 -0
- package/dist/core/which.js +18 -0
- package/dist/credentials/cloud-claim.d.ts +32 -0
- package/dist/credentials/cloud-claim.js +42 -0
- package/dist/credentials/constants/credentials.constants.d.ts +8 -1
- package/dist/credentials/constants/credentials.constants.js +9 -2
- package/dist/credentials/device-api.d.ts +15 -1
- package/dist/credentials/device-api.js +12 -1
- package/dist/credentials/sign-in.d.ts +27 -0
- package/dist/credentials/sign-in.js +31 -1
- package/dist/credentials/token-refresher.d.ts +5 -1
- package/dist/credentials/token-refresher.js +10 -2
- package/dist/events/constants/events.constants.d.ts +8 -2
- package/dist/events/constants/events.constants.js +7 -1
- package/dist/events/index.d.ts +2 -0
- package/dist/events/product-event.d.ts +10 -4
- package/dist/events/types/events.types.d.ts +6 -0
- package/dist/events/types/replay-progress.types.d.ts +26 -0
- package/dist/events/types/replay-progress.types.js +1 -0
- package/dist/events/types/repo-snapshot.types.d.ts +1 -4
- package/dist/events/types/repo-tree.types.d.ts +25 -0
- package/dist/events/types/repo-tree.types.js +1 -0
- package/dist/feature/ticket-candidates.d.ts +1 -1
- package/dist/git/checkout-root.d.ts +15 -0
- package/dist/git/checkout-root.js +18 -0
- package/dist/git/code-state.d.ts +2 -16
- package/dist/git/code-state.js +11 -12
- package/dist/git/constants/git.constants.d.ts +31 -11
- package/dist/git/constants/git.constants.js +36 -12
- package/dist/git/constants/tree.constants.d.ts +71 -0
- package/dist/git/constants/tree.constants.js +92 -0
- package/dist/git/fingerprint.d.ts +3 -6
- package/dist/git/fingerprint.js +5 -8
- package/dist/git/git-context.d.ts +1 -0
- package/dist/git/git-context.js +8 -3
- package/dist/git/index.d.ts +1 -2
- package/dist/git/index.js +1 -1
- package/dist/git/repo-snapshot.d.ts +13 -4
- package/dist/git/repo-snapshot.js +47 -9
- package/dist/git/repo-tree.d.ts +69 -0
- package/dist/git/repo-tree.js +130 -0
- package/dist/git/types/git.types.d.ts +5 -2
- package/dist/git/types/snapshot.types.d.ts +14 -0
- package/dist/pipeline/constants/pipeline.constants.d.ts +3 -0
- package/dist/pipeline/constants/pipeline.constants.js +3 -0
- package/dist/pipeline/hook-pipeline.js +112 -72
- package/dist/privacy/product-capture.js +36 -5
- package/dist/providers/antigravity/antigravity.capture.d.ts +2 -0
- package/dist/providers/antigravity/antigravity.capture.js +5 -0
- package/dist/providers/antigravity/antigravity.detect.js +8 -22
- package/dist/providers/antigravity/antigravity.provider.js +10 -3
- package/dist/providers/antigravity/constants/antigravity.constants.d.ts +1 -0
- package/dist/providers/antigravity/constants/antigravity.constants.js +1 -0
- package/dist/providers/claude/claude.adapter.js +9 -6
- package/dist/providers/claude/claude.detect.js +2 -17
- package/dist/providers/claude/claude.otel.d.ts +21 -3
- package/dist/providers/claude/claude.otel.js +216 -61
- package/dist/providers/claude/claude.provider.js +17 -1
- package/dist/providers/claude/claude.version.d.ts +9 -0
- package/dist/providers/claude/claude.version.js +28 -0
- package/dist/providers/claude/constants/claude.constants.d.ts +27 -0
- package/dist/providers/claude/constants/claude.constants.js +27 -0
- package/dist/providers/claude/constants/claude.otel.constants.d.ts +27 -0
- package/dist/providers/claude/constants/claude.otel.constants.js +45 -5
- package/dist/providers/claude/types/claude.types.d.ts +13 -0
- package/dist/providers/codex/codex.capture.d.ts +76 -0
- package/dist/providers/codex/codex.capture.js +454 -0
- package/dist/providers/codex/codex.detect.js +2 -4
- package/dist/providers/codex/codex.otel.d.ts +38 -2
- package/dist/providers/codex/codex.otel.js +50 -6
- package/dist/providers/codex/codex.provider.js +8 -0
- package/dist/providers/codex/codex.surface.d.ts +9 -0
- package/dist/{turns/codex-originator.js → providers/codex/codex.surface.js} +17 -3
- package/dist/providers/codex/codex.titles.d.ts +14 -0
- package/dist/providers/codex/codex.titles.js +35 -0
- package/dist/providers/codex/constants/codex.constants.d.ts +4 -0
- package/dist/providers/codex/constants/codex.constants.js +4 -0
- package/dist/providers/cursor/constants/cursor.constants.d.ts +17 -4
- package/dist/providers/cursor/constants/cursor.constants.js +25 -5
- package/dist/providers/cursor/cursor-mcp-memo.d.ts +34 -0
- package/dist/providers/cursor/cursor-mcp-memo.js +94 -0
- package/dist/providers/cursor/cursor.adapter.js +20 -82
- package/dist/providers/cursor/cursor.capture.d.ts +1 -0
- package/dist/providers/cursor/cursor.capture.js +4 -0
- package/dist/providers/cursor/cursor.detect.d.ts +5 -1
- package/dist/providers/cursor/cursor.detect.js +11 -26
- package/dist/providers/cursor/cursor.hooks.js +2 -2
- package/dist/providers/cursor/cursor.provider.js +16 -7
- package/dist/providers/cursor/cursor.titles.d.ts +14 -0
- package/dist/providers/cursor/cursor.titles.js +20 -0
- package/dist/providers/cursor/schemas/cursor.schema.d.ts +3 -3
- package/dist/providers/cursor/schemas/cursor.schema.js +5 -3
- package/dist/providers/gemini/constants/gemini.constants.d.ts +16 -0
- package/dist/providers/gemini/constants/gemini.constants.js +17 -0
- package/dist/providers/gemini/gemini.capture.d.ts +81 -0
- package/dist/providers/gemini/gemini.capture.js +210 -0
- package/dist/providers/gemini/gemini.detect.js +57 -24
- package/dist/providers/gemini/gemini.otel.d.ts +38 -2
- package/dist/providers/gemini/gemini.otel.js +56 -125
- package/dist/providers/gemini/gemini.provider.js +5 -0
- package/dist/providers/index.d.ts +1 -0
- package/dist/providers/index.js +1 -0
- package/dist/providers/provider.d.ts +8 -0
- package/dist/providers/provider.js +9 -0
- package/dist/providers/registry.d.ts +14 -0
- package/dist/providers/registry.js +14 -0
- package/dist/providers/shared/constants/hook-config.constants.d.ts +2 -0
- package/dist/providers/shared/constants/hook-config.constants.js +2 -0
- package/dist/providers/shared/constants/terminal-capture.constants.d.ts +6 -0
- package/dist/providers/shared/constants/terminal-capture.constants.js +6 -0
- package/dist/providers/shared/editor-paths.d.ts +8 -0
- package/dist/providers/shared/editor-paths.js +18 -0
- package/dist/providers/shared/hook-config.d.ts +5 -0
- package/dist/providers/shared/hook-config.js +39 -1
- package/dist/providers/shared/hooks-marker.d.ts +14 -0
- package/dist/providers/shared/hooks-marker.js +23 -0
- package/dist/providers/shared/install-record.d.ts +29 -0
- package/dist/providers/shared/install-record.js +52 -0
- package/dist/providers/shared/session-title-store.d.ts +23 -0
- package/dist/providers/shared/session-title-store.js +50 -0
- package/dist/providers/shared/terminal-capture.d.ts +41 -0
- package/dist/providers/shared/terminal-capture.js +109 -0
- package/dist/providers/shared/tooling.d.ts +21 -0
- package/dist/providers/shared/tooling.js +36 -1
- package/dist/providers/types/provider.types.d.ts +57 -4
- package/dist/replay/checkout-resolver.d.ts +29 -0
- package/dist/replay/checkout-resolver.js +69 -0
- package/dist/replay/codex-turns.d.ts +24 -0
- package/dist/replay/codex-turns.js +221 -0
- package/dist/replay/constants/replay.constants.d.ts +99 -0
- package/dist/replay/constants/replay.constants.js +102 -0
- package/dist/replay/describe.d.ts +10 -0
- package/dist/replay/describe.js +31 -0
- package/dist/replay/gemini-turns.d.ts +36 -0
- package/dist/replay/gemini-turns.js +192 -0
- package/dist/replay/machine.d.ts +34 -0
- package/dist/replay/machine.js +68 -0
- package/dist/replay/progress-event.d.ts +21 -0
- package/dist/replay/progress-event.js +45 -0
- package/dist/replay/replay-runner.d.ts +58 -0
- package/dist/replay/replay-runner.js +529 -0
- package/dist/replay/replay-scan.d.ts +83 -0
- package/dist/replay/replay-scan.js +170 -0
- package/dist/replay/replay-state.d.ts +108 -0
- package/dist/replay/replay-state.js +199 -0
- package/dist/replay/resume.d.ts +18 -0
- package/dist/replay/resume.js +34 -0
- package/dist/replay/start.d.ts +23 -0
- package/dist/replay/start.js +39 -0
- package/dist/replay/throttle.d.ts +35 -0
- package/dist/replay/throttle.js +41 -0
- package/dist/replay/transcript-turns.d.ts +35 -0
- package/dist/replay/transcript-turns.js +215 -0
- package/dist/replay/turn-event.d.ts +38 -0
- package/dist/replay/turn-event.js +116 -0
- package/dist/replay/types/replay.types.d.ts +162 -0
- package/dist/replay/types/replay.types.js +1 -0
- package/dist/replay/window.d.ts +28 -0
- package/dist/replay/window.js +41 -0
- package/dist/snapshot/branch-selection.d.ts +40 -23
- package/dist/snapshot/branch-selection.js +74 -42
- package/dist/snapshot/budget.js +2 -2
- package/dist/snapshot/constants/snapshot-stages.constants.d.ts +10 -0
- package/dist/snapshot/constants/snapshot-stages.constants.js +10 -0
- package/dist/snapshot/constants/snapshot.constants.d.ts +37 -4
- package/dist/snapshot/constants/snapshot.constants.js +37 -4
- package/dist/snapshot/index.d.ts +6 -1
- package/dist/snapshot/index.js +3 -1
- package/dist/snapshot/snapshot-event.d.ts +7 -0
- package/dist/snapshot/snapshot-event.js +8 -5
- package/dist/snapshot/snapshot-pipeline.js +89 -26
- package/dist/snapshot/snapshot-state.js +24 -2
- package/dist/snapshot/tree-event.d.ts +14 -0
- package/dist/snapshot/tree-event.js +91 -0
- package/dist/snapshot/tree-pipeline.d.ts +12 -0
- package/dist/snapshot/tree-pipeline.js +172 -0
- package/dist/snapshot/types/snapshot.types.d.ts +62 -2
- package/dist/storage/schemas/storage.schema.d.ts +2 -0
- package/dist/storage/schemas/storage.schema.js +6 -0
- package/dist/transport/constants/transport.constants.d.ts +5 -0
- package/dist/transport/constants/transport.constants.js +5 -0
- package/dist/transport/delivery-stats.d.ts +13 -1
- package/dist/transport/delivery-stats.js +18 -2
- package/dist/transport/delivery.d.ts +4 -3
- package/dist/transport/delivery.js +21 -7
- package/dist/transport/identity-delivery.d.ts +20 -0
- package/dist/transport/identity-delivery.js +41 -0
- package/dist/transport/index.d.ts +2 -0
- package/dist/transport/index.js +1 -0
- package/dist/transport/queue.js +40 -6
- package/dist/transport/types/delivery-flow.types.d.ts +7 -0
- package/dist/turns/claude-transcript.js +4 -12
- package/dist/turns/codex-transcript.d.ts +9 -0
- package/dist/turns/codex-transcript.js +27 -19
- package/dist/turns/constants/turns.constants.d.ts +13 -12
- package/dist/turns/constants/turns.constants.js +15 -19
- package/dist/turns/gemini-transcript.d.ts +19 -1
- package/dist/turns/gemini-transcript.js +29 -18
- package/dist/turns/index.d.ts +3 -4
- package/dist/turns/index.js +2 -3
- package/dist/turns/run-state.d.ts +71 -0
- package/dist/turns/run-state.js +114 -0
- package/dist/turns/tool-events.d.ts +11 -1
- package/dist/turns/tool-events.js +32 -9
- package/dist/turns/transcript.d.ts +15 -14
- package/dist/turns/transcript.js +23 -4
- package/dist/turns/turn-state.d.ts +49 -7
- package/dist/turns/turn-state.js +78 -10
- package/dist/turns/turn-summary.js +10 -6
- package/dist/turns/turn-tracker.d.ts +9 -16
- package/dist/turns/turn-tracker.js +162 -86
- package/dist/turns/types/transcript.types.d.ts +11 -1
- package/dist/turns/types/turn-provider.types.d.ts +33 -0
- package/dist/turns/types/turn-provider.types.js +1 -0
- package/dist/turns/types/turn-state.types.d.ts +9 -0
- package/dist/turns/types/turn-summary.types.d.ts +20 -6
- package/dist/turns/types/turn-tracker.types.d.ts +3 -1
- package/dist/turns/work-checkout.js +1 -2
- package/docs/AUDIT_PROMPT.md +10 -0
- package/docs/DATA_HANDLING.md +269 -32
- package/docs/ENTERPRISE_DEPLOYMENT.md +1 -1
- package/docs/PERFORMANCE.md +27 -0
- package/package.json +3 -2
- package/dist/events/canonical-event.d.ts +0 -10
- package/dist/events/canonical-event.js +0 -9
- package/dist/git/repository-root.d.ts +0 -39
- package/dist/git/repository-root.js +0 -131
- package/dist/git/types/repository-root.types.d.ts +0 -11
- package/dist/transport/transport.d.ts +0 -6
- package/dist/turns/codex-originator.d.ts +0 -11
- package/dist/turns/cursor-transcript.d.ts +0 -21
- package/dist/turns/cursor-transcript.js +0 -66
- package/dist/turns/native-session-titles.d.ts +0 -26
- package/dist/turns/native-session-titles.js +0 -102
- /package/dist/{git/types/repository-root.types.js → billing/types/billing.types.js} +0 -0
- /package/dist/{transport/transport.js → capture/types/capture.types.js} +0 -0
package/docs/AUDIT_PROMPT.md
CHANGED
|
@@ -83,6 +83,16 @@ absent with `capture.git: false` (at build time and again before send), and
|
|
|
83
83
|
which git processes a check runs on the hook path. Say what a guessed common
|
|
84
84
|
command's hash lets someone confirm.
|
|
85
85
|
|
|
86
|
+
Beside them, under the same `capture.git` gate, Claude Code turns carry two
|
|
87
|
+
names: `tool_events[].skill` (the skill a `Skill` call ran) and the summary's
|
|
88
|
+
`command` (the slash command the first prompt opens with, without its slash).
|
|
89
|
+
Verify that each is only the matched name token, never a skill's arguments,
|
|
90
|
+
never the text after the command and never any other part of the prompt; that
|
|
91
|
+
a value failing `^[A-Za-z0-9][A-Za-z0-9_.:/-]{0,79}$` is dropped without
|
|
92
|
+
failing the summary; that a prompt opening with a path (`/Users/...`) sends no
|
|
93
|
+
command; and that both are absent with `capture.git: false`, at build time and
|
|
94
|
+
again before send.
|
|
95
|
+
|
|
86
96
|
## 5. The consent gate
|
|
87
97
|
Explain how content capture is enabled. Can a repository-level config file,
|
|
88
98
|
an environment variable, a command-line flag, or a corrupt or missing global
|
package/docs/DATA_HANDLING.md
CHANGED
|
@@ -12,10 +12,11 @@ require root, proxy model requests, or enforce an administrator-proof policy.
|
|
|
12
12
|
## Defaults and upgrade consent
|
|
13
13
|
|
|
14
14
|
**Prompt text and tool content are opt-in; response text is never collected.**
|
|
15
|
-
By default a prompt or response is
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
knows); the prompt
|
|
15
|
+
By default nothing about a prompt or response is sent: not its text, not its
|
|
16
|
+
length, not a digest of it. The first ticket key named in the session's opening
|
|
17
|
+
prompt is the one exception: it is extracted on the machine and sent as
|
|
18
|
+
`prompt_jira_ids` (the platform keeps it only if it knows the key); the prompt
|
|
19
|
+
text is not.
|
|
19
20
|
There is no capture flag for response text.
|
|
20
21
|
|
|
21
22
|
Prompt text, tool input and tool output bodies, and session titles, are not collected by default.
|
|
@@ -75,7 +76,7 @@ fields.
|
|
|
75
76
|
Current policy is reapplied to old turn state before queueing, and to every queued
|
|
76
77
|
record before HTTP delivery: summaries always lose `prompt` and `response` text an
|
|
77
78
|
older release may have written, lose `prompt_text`, `tool_inputs`, `session_name` and `session_title` unless their
|
|
78
|
-
flag is on with consent, lose every path list once `capture.files` is off, lose `tool_events` once `capture.git` is off, and repository snapshots are dropped entirely once
|
|
79
|
+
flag is on with consent, lose every path list once `capture.files` is off, lose `tool_events` and `command` once `capture.git` is off, and repository snapshots are dropped entirely once
|
|
79
80
|
`capture.git` is off. Old files are not erased by an upgrade; their original content
|
|
80
81
|
may remain locally until consumed or expired, but it is never sent.
|
|
81
82
|
|
|
@@ -99,13 +100,17 @@ puts the totals on the turn summary; no rollout content is read into it or sent.
|
|
|
99
100
|
|
|
100
101
|
## Outbound records
|
|
101
102
|
|
|
102
|
-
There are
|
|
103
|
+
There are six public event types, not a raw lifecycle or tool event stream:
|
|
103
104
|
|
|
104
105
|
| Type | Source and purpose |
|
|
105
106
|
| --- | --- |
|
|
106
107
|
| `turn.summary` | Edge hooks assemble one completed turn and send it to the events endpoint, or queue it. |
|
|
107
108
|
| `llm.call` | Agents export native OTLP directly. The backend/library normalizes supported completed request records into per-call usage. Edge does not proxy native OTLP. |
|
|
109
|
+
| `llm.call` (captured) | Edge's shim records the provider calls of a process the coding agent starts through its shell tool, and Edge queues them as calls of the launching session and turn. See "Captured runs". |
|
|
108
110
|
| `repo.snapshot` | Edge queues changed repository branch/commit metadata after a closed turn when Git capture is enabled. |
|
|
111
|
+
| `session.billing` | Edge states how the session's developer pays (`api` or `subscription`, detected from the agent's local auth state), once, when the session opens. |
|
|
112
|
+
| `repo.tree` | Edge queues the default branch's source file paths and top-level declaration names after a closed turn when Git and file capture are enabled, once per repository per install identity. Never file contents. |
|
|
113
|
+
| `replay.progress` | Edge states how far a replay of the developer's earlier Claude Code, Codex and Gemini CLI sessions has got: counts and the window, nothing else. See "Replay of earlier sessions". |
|
|
109
114
|
|
|
110
115
|
Generated records share `schemaVersion`, `id`, `timestamp`, `event.type`,
|
|
111
116
|
`event.providerEventType`, `agent.provider`, `agent.name`, session identifiers,
|
|
@@ -115,23 +120,27 @@ availability determines which identifiers and usage values exist.
|
|
|
115
120
|
### `turn.summary`
|
|
116
121
|
|
|
117
122
|
The hook-generated flat fields are `provider`, `surface`, `session_id`, `turn_id`,
|
|
118
|
-
`developer_id`, `repository`, `branch`, `commit`, `jira_ids`, `prompt_jira_ids`, `work_evidence`,
|
|
123
|
+
`developer_id`, `account_email`, `session_mode`, `is_cloud_agent`, `repository`, `branch`, `commit`, `jira_ids`, `prompt_jira_ids`, `work_evidence`,
|
|
119
124
|
`parent_session_id`, `content_hashes`, `manifest_repository`, `files_changed`, `files_touched`, `files_read`, `external_files_touched`,
|
|
120
|
-
`external_files_read`, `
|
|
121
|
-
`tool_calls`, `tools_used`, `tool_events`, `model`, `billing_mode`, `input_tokens`,
|
|
125
|
+
`external_files_read`, `prompt_text`, `session_name`, `session_title`, `tool_inputs`,
|
|
126
|
+
`tool_calls`, `tools_used`, `tool_events`, `command`, `model`, `billing_mode`, `input_tokens`,
|
|
122
127
|
`cached_input_tokens`, `cache_creation_input_tokens`, `output_tokens`,
|
|
123
128
|
`usage_status`, `started_at`, and `ended_at`. The nested `session` contains `id`,
|
|
124
129
|
`providerId`, and optionally `turnId`.
|
|
125
130
|
|
|
126
|
-
`prompt_jira_ids`
|
|
127
|
-
found in the session's opening prompt, extracted on the machine and
|
|
128
|
-
turn at every tier, with no consent step
|
|
129
|
-
text. `capture.git: false`
|
|
131
|
+
`prompt_jira_ids` holds the first ticket key (same syntax as the branch keys in
|
|
132
|
+
`jira_ids`) found in the session's opening prompt, extracted on the machine and
|
|
133
|
+
sent on every turn at every tier, with no consent step: at most one key, since
|
|
134
|
+
the platform reads only the first. Never the prompt text. `capture.git: false`
|
|
135
|
+
withholds it, as it does `jira_ids`. A prompt's length and SHA-256 are not sent
|
|
136
|
+
(older releases sent them as `prompt_evidence` and `response_evidence`; a summary
|
|
137
|
+
they queued loses them at delivery).
|
|
130
138
|
|
|
131
139
|
A prompt is free text, so a string like `INV-204391`, `MRN-123456` or `UTF-8`
|
|
132
|
-
matches the key syntax too. The edge
|
|
133
|
-
deduplicated and capped at 50; the platform matches
|
|
134
|
-
(branch names, connected trackers) and ignores
|
|
140
|
+
matches the key syntax too. The edge keeps the candidates on the machine in
|
|
141
|
+
order, deduplicated and capped at 50, and sends the first; the platform matches it
|
|
142
|
+
against the keys it knows (branch names, connected trackers) and ignores it
|
|
143
|
+
otherwise, so an unknown key is inert.
|
|
135
144
|
|
|
136
145
|
On the machine the keys are kept in `prompt-tickets.json` in the session's local
|
|
137
146
|
turn state (mode 0600): keys only, written once by the opening prompt, and an
|
|
@@ -142,10 +151,8 @@ every key the prompt named. The 24-hour
|
|
|
142
151
|
sweep deletes it, counted from SessionEnd, so a session resumed within a day of
|
|
143
152
|
ending keeps its keys.
|
|
144
153
|
|
|
145
|
-
No field carries response text
|
|
146
|
-
text the developer typed
|
|
147
|
-
and lengths can still reveal information about short or guessable text. The
|
|
148
|
-
prompt evidence hashes the prompt as the agent reported it.
|
|
154
|
+
No field carries response text, and no field carries a length or a hash of the
|
|
155
|
+
text the developer typed or the agent answered.
|
|
149
156
|
|
|
150
157
|
- `prompt_text` (only under `promptText` with consent): the turn's first prompt,
|
|
151
158
|
with `<system-reminder>` blocks the agent's harness injected removed, secrets
|
|
@@ -187,7 +194,7 @@ prompt evidence hashes the prompt as the agent reported it.
|
|
|
187
194
|
calls), `started_at` (from the provider's duration, or from the call's start
|
|
188
195
|
hook paired on its call id or Antigravity's step index; a call with neither, such
|
|
189
196
|
as a Gemini CLI call without `tool_use_id`, sends none), `ended_at`, `input_fp`, `check`,
|
|
190
|
-
`commit` and `
|
|
197
|
+
`commit`, `diff_fp` and `skill`. There is no field for a command, a path, arguments or
|
|
191
198
|
an output.
|
|
192
199
|
- `input_fp`: for a shell call, the sha256 of the command after normalization
|
|
193
200
|
(quotes undone, whitespace collapsed, `cd` segments, redirections and leading
|
|
@@ -195,9 +202,8 @@ prompt evidence hashes the prompt as the agent reported it.
|
|
|
195
202
|
connector (MCP) call, the sha256 of its arguments as JSON. Other tools send
|
|
196
203
|
none. The command and arguments are read in memory in the hook, hashed and
|
|
197
204
|
dropped: the text is never stored, queued, logged or sent without `toolInput`.
|
|
198
|
-
|
|
199
|
-
|
|
200
|
-
the same guess. The platform re-keys every stored fingerprint with a key per
|
|
205
|
+
A hash is not the text, but a hash of a short or common command (`npm test`,
|
|
206
|
+
`git status`) can be confirmed by anyone who hashes the same guess. The platform re-keys every stored fingerprint with a key per
|
|
201
207
|
tenant, so a stored value cannot be compared across tenants or confirmed
|
|
202
208
|
without that key.
|
|
203
209
|
- `check`: the command is on a fixed allowlist of test, lint, typecheck and build
|
|
@@ -214,6 +220,17 @@ prompt evidence hashes the prompt as the agent reported it.
|
|
|
214
220
|
only extra work a check costs the hook: `git rev-parse HEAD` and `git diff`,
|
|
215
221
|
both read-only and run with `--no-optional-locks`, so they write nothing to
|
|
216
222
|
the repository and never take the agent's index lock.
|
|
223
|
+
- `skill`, on a Claude Code `Skill` call only: the name of the skill it ran
|
|
224
|
+
(`build-ticket`, `plugin:name`), read in memory from the call's input. Never
|
|
225
|
+
its arguments. A name that is not 1-80 characters of letters, digits and
|
|
226
|
+
`_ . : / -` (starting with a letter or digit) is dropped; the call is still sent.
|
|
227
|
+
- `command` (under `git`, on by default, withheld with `tool_events`): the name of
|
|
228
|
+
the slash command the turn's first prompt opens with, without the slash and
|
|
229
|
+
without anything after it: `/ship-it now` sends `ship-it`. Read in memory from
|
|
230
|
+
the prompt in the hook; nothing else of the prompt is kept for it. A first
|
|
231
|
+
token holding a further `/` (a path such as `/Users/me/a.ts`) or failing the
|
|
232
|
+
name rule above sends nothing. Claude Code only: Codex, Cursor, Gemini CLI and
|
|
233
|
+
Antigravity send neither field.
|
|
217
234
|
|
|
218
235
|
On the machine, a tool call's start is kept in local turn state (mode 0600) until
|
|
219
236
|
the turn closes, only while `capture.git` is on: its time and the agent's call id
|
|
@@ -275,15 +292,88 @@ but the content gate above can prevent their provider configuration; traces and
|
|
|
275
292
|
metrics default off. See [Claude telemetry](https://code.claude.com/docs/en/monitoring-usage)
|
|
276
293
|
and [Gemini telemetry](https://geminicli.com/docs/cli/telemetry/) for provider gates.
|
|
277
294
|
|
|
295
|
+
### Captured runs
|
|
296
|
+
|
|
297
|
+
Setup copies Edge's shims to `<data dir>/capture/`, mode 0600 in a 0700 folder,
|
|
298
|
+
overwriting them on every run, and adds that copy to what a coding agent's shell tool
|
|
299
|
+
starts: `NODE_OPTIONS` gains `--require <data dir>/capture/node.cjs`, and `PYTHONPATH`
|
|
300
|
+
gains `<data dir>/capture/python`. Both run inside that process, as the developer. The
|
|
301
|
+
target is a copy because Node refuses to start when a `--require` target is missing, so
|
|
302
|
+
it must not depend on the package staying where it is. A value the developer already
|
|
303
|
+
had is kept beside ours. Setup and uninstall remove an entry only when it lies in an
|
|
304
|
+
Edge install or is this copy, or when it is a shim-shaped `--require` whose target is
|
|
305
|
+
gone. `agentwatch uninstall` removes the entries, and the copy once no agent's hooks are
|
|
306
|
+
left. `agentwatch off` keeps the copy, because sessions already running still load it;
|
|
307
|
+
restart those sessions after an uninstall. A process whose entry is a coding agent
|
|
308
|
+
(`claude`, `codex`, `gemini`, `cursor`, `cursor-agent`, `antigravity`, `agy`) captures
|
|
309
|
+
nothing. `AGENTWATCH_CAPTURE=off` in a process's environment turns the shim off for it.
|
|
310
|
+
|
|
311
|
+
The entries live in Claude Code's `settings.json` `env` block, in
|
|
312
|
+
`[shell_environment_policy.set]` of Codex's `config.toml`, and in `~/.gemini/.env`. For
|
|
313
|
+
Cursor and Antigravity nothing is written, and status says there is no environment route,
|
|
314
|
+
until that route is verified on the app. Capture is usage only, so it does not wait on
|
|
315
|
+
`contentCaptureConsent`, which holds back the native export of Codex and Gemini CLI
|
|
316
|
+
because those logs carry tool content.
|
|
317
|
+
|
|
318
|
+
Codex's default sandbox denies a command's write outside the workspace, so setup also adds
|
|
319
|
+
`<data dir>/captured`, and only that folder, to `[sandbox_workspace_write] writable_roots`
|
|
320
|
+
in `config.toml`. A sandboxed command can therefore write to the spool, and nothing else in
|
|
321
|
+
the data dir: credentials stay outside the sandbox's writable set. Entries already in the
|
|
322
|
+
array stay, and uninstall takes out only that one, along with the table if Edge created it
|
|
323
|
+
and nothing else is in it. With `default_permissions` set, nothing is added, as Codex says
|
|
324
|
+
not to combine the two; status warns that what runs is counted only if that profile allows
|
|
325
|
+
the write. `sandbox_mode = "read-only"` and `codex exec`'s read-only default deny it too.
|
|
326
|
+
Inside the workspace-write sandbox on macOS the write is allowed but `ps` is denied, so the
|
|
327
|
+
shim cannot record its ancestors and such a record is dropped, and the network is off unless
|
|
328
|
+
`network_access = true`. A script's call is counted under `danger-full-access` or as an
|
|
329
|
+
escalated command; status says so.
|
|
330
|
+
|
|
331
|
+
For a response from Anthropic, OpenAI, Google (Gemini, Vertex AI) or Bedrock, a shim
|
|
332
|
+
reads the request's host, method and URL path up to `?` (a Gemini key can follow it),
|
|
333
|
+
and the response's status, request id header, model and usage fields. It holds a
|
|
334
|
+
non-streamed body in memory, up to 8 MB, only to find those fields. It never reads a
|
|
335
|
+
request body or a request header other than the host, and it opens no socket.
|
|
336
|
+
|
|
337
|
+
It appends one line per call to `<data dir>/captured/<pid>.jsonl`, mode 0600, at most
|
|
338
|
+
10,000 lines per file: `pid`, `started`, `ancestors` (pid and start time of the
|
|
339
|
+
processes above it), `at`, `seq`, `script` (its own file name, used only to find its
|
|
340
|
+
run), `provider`, `model`, `request_id`, `status`, `usage`.
|
|
341
|
+
To read its ancestors, a shim runs `ps -A` once, at the process's first provider call,
|
|
342
|
+
and keeps only its own chain. The shims write only while the `captured` folder exists:
|
|
343
|
+
a hook creates it when Edge holds a credential, and removes it and its contents when
|
|
344
|
+
Edge does not. So a signed-out machine captures nothing and holds nothing back.
|
|
345
|
+
|
|
346
|
+
At the next hook on the machine, Edge reads and deletes those files. It discards `pid`,
|
|
347
|
+
`ancestors`, `script` and the other process details, and queues an `llm.call` per record, with
|
|
348
|
+
`billing_mode: api` and two more fields:
|
|
349
|
+
|
|
350
|
+
- `run_entry`: the file the shell command ran, relative to its checkout, or the file
|
|
351
|
+
name alone outside one. An inline program (`python -c`), a package script
|
|
352
|
+
(`npm run dev`) or any other command is named by its runner or first word, and
|
|
353
|
+
`capture.files: false` keeps it to that. It is scrubbed like a turn summary's paths.
|
|
354
|
+
The command's other text is read in memory and kept nowhere, and a `VAR=value`
|
|
355
|
+
prefix is not read.
|
|
356
|
+
- `platform`: which provider's API served the call.
|
|
357
|
+
|
|
358
|
+
To name the entry file, each session keeps a list of its shell calls' entries in its
|
|
359
|
+
own state folder, removed with the session. A record no session or run claims is
|
|
360
|
+
dropped and counted in `agentwatch status`, and no event is built from it. On a
|
|
361
|
+
machine with several identities, a hook leaves another tenant's spool file for that
|
|
362
|
+
session's own hook.
|
|
363
|
+
|
|
278
364
|
### `repo.snapshot` and Git metadata
|
|
279
365
|
|
|
280
366
|
Snapshots contain `provider`, `surface`, `repository`, optional `developer_id`,
|
|
281
|
-
`default_branch`, `captured_at`, and `branches`.
|
|
282
|
-
|
|
283
|
-
|
|
284
|
-
|
|
285
|
-
|
|
286
|
-
|
|
367
|
+
`default_branch`, `captured_at`, and `branches`. A branch whose work is already
|
|
368
|
+
on the default branch (no commits of its own, or a squash or rebase merge git can
|
|
369
|
+
see), or whose upstream is gone, is left out, and the ten branches sent are the
|
|
370
|
+
newest ten that remain. Each branch has `name`,
|
|
371
|
+
`head_sha` and `commits`; each commit has `sha`, `subject` and optional `files`.
|
|
372
|
+
`files` lists the files that commit changed as `{ path }`, repository-relative as
|
|
373
|
+
git names it (a rename is listed as both its old and its new path). No commit or
|
|
374
|
+
branch times and no change-type letter are sent (older releases sent
|
|
375
|
+
`authored_at`, `last_commit_at` and a `status`; a snapshot they queued loses them
|
|
376
|
+
at delivery). **Names only, never file contents.**
|
|
287
377
|
Files named like credentials (`.env`, `.env.*`, `*.pem`, `*.key`, `*.p12`, `*.pfx`,
|
|
288
378
|
`id_rsa`/`id_ed25519`/`id_ecdsa`, `credentials`, `credentials.*`, `.npmrc`, `.netrc`), paths
|
|
289
379
|
over 1,024 characters and paths holding control characters are left out. A
|
|
@@ -301,6 +391,137 @@ sensitive business information even though they are classified as metadata.
|
|
|
301
391
|
Set global `capture.git: false` to disable new snapshots; already-queued snapshots
|
|
302
392
|
are then discarded at delivery rather than sent.
|
|
303
393
|
|
|
394
|
+
### Replay of earlier sessions
|
|
395
|
+
|
|
396
|
+
`agentwatch setup` starts, in the background, a replay of the developer's
|
|
397
|
+
**earlier Claude Code, Codex and Gemini CLI sessions** so the platform shows
|
|
398
|
+
the developer's recent history right after install. It sends nothing the live
|
|
399
|
+
hooks do not already send, built by the same code. It reads:
|
|
400
|
+
|
|
401
|
+
- **Claude Code:** `~/.claude/projects/<folder>/<session>.jsonl`.
|
|
402
|
+
- **Codex:** `$CODEX_HOME/sessions/YYYY/MM/DD/rollout-*.jsonl` (`~/.codex` by
|
|
403
|
+
default). Only the session row (session id, folder, how Codex was started,
|
|
404
|
+
and the branch, remote address and commit it records at session start) and
|
|
405
|
+
the turn, model and token-count rows are decoded; message, reasoning and
|
|
406
|
+
tool-output rows are skipped without being parsed.
|
|
407
|
+
- **Gemini CLI:** `$GEMINI_HOME/tmp/<project>/chats/session-*.jsonl`
|
|
408
|
+
(`~/.gemini` by default), placed in a folder through `projects.json`. Only
|
|
409
|
+
message ids, times, types, models and reply token counts are kept; reply and
|
|
410
|
+
thought content never is.
|
|
411
|
+
|
|
412
|
+
Only metadata leaves the machine, as listed below:
|
|
413
|
+
|
|
414
|
+
- **What each replayed turn carries.** A `turn.summary` per typed prompt: the
|
|
415
|
+
session and turn ids, the turn's start and end time, model and token counts
|
|
416
|
+
(summed once per message), tool counts and names, the files the agent's tools
|
|
417
|
+
named (checkout-relative, and only inside a checkout), the repository (read
|
|
418
|
+
from the folder the agent was in when the turn ended if that folder is still
|
|
419
|
+
a checkout; otherwise the checkout of a file the agent's tools edited, or,
|
|
420
|
+
for a folder that is gone, the remote address a Codex rollout recorded), the
|
|
421
|
+
branch the transcript records, and ticket keys from the branch name.
|
|
422
|
+
`work_evidence` is `cwd`, or `changed` when the repository came from an edited
|
|
423
|
+
file. Codex turns carry the branch recorded at session start (and so ticket
|
|
424
|
+
keys from it) and no tool names or files; Gemini CLI turns carry no branch
|
|
425
|
+
and no tool names or files: their files do not record them per turn.
|
|
426
|
+
- **What it does not carry.** No commit, except the full commit id a Codex
|
|
427
|
+
rollout recorded at session start, sent only for a folder that is gone and
|
|
428
|
+
never for a folder that is still a checkout; no `tool_events`, no session names or titles, no shell or
|
|
429
|
+
connector inputs, no response text, ever. **No prompt text** unless the
|
|
430
|
+
developer has already turned `capture.promptText` on (and given content
|
|
431
|
+
consent); it is then scrubbed and bounded as a live prompt is.
|
|
432
|
+
- **Status.** Every replayed turn is sent with `usage_status: pending` and its
|
|
433
|
+
token counts, so it can never overwrite the same turn if a live hook sent it.
|
|
434
|
+
- **Which turns.** Those that started in the last `--replay-days` days (30 by
|
|
435
|
+
default) and **never before the start of the open charge period**: the start
|
|
436
|
+
of the current UTC month, or of the previous month during the first four days
|
|
437
|
+
of a month. Money already settled is never reopened. A turn that ended in the
|
|
438
|
+
last ten minutes is left to the live hook.
|
|
439
|
+
- **Same turns as live, once.** A replayed Claude Code turn's `turn_id` is the
|
|
440
|
+
transcript's prompt id, and a Codex turn's is the rollout's `turn_id`: both are
|
|
441
|
+
the id the live hook sends, and the event id is derived from the agent, the
|
|
442
|
+
session and that id, so replaying twice, or replaying a turn a hook already
|
|
443
|
+
sent, changes nothing on the platform. Gemini CLI's chat files do not record
|
|
444
|
+
the live hook's id, so a Gemini turn is replayed only when it began before
|
|
445
|
+
AgentWatch first installed Gemini hooks on the machine; an install that hooked
|
|
446
|
+
Gemini before that time was recorded replays no Gemini turns. A Gemini session
|
|
447
|
+
written before gemini-cli 0.46 records no token counts and is not replayed.
|
|
448
|
+
- **After the turns.** One `repo.snapshot` and, with `capture.files`, one
|
|
449
|
+
`repo.tree` per repository the turns ran in that still exists on the machine:
|
|
450
|
+
the same records a live turn sends, with the same bounds.
|
|
451
|
+
- **`replay.progress`.** Counts and times only: `replay_id`, `state`
|
|
452
|
+
(`scanning`, `running`, `paused`, `done`, `stopped`), `window_start`,
|
|
453
|
+
`window_end`, `turns_total`, `turns_sent`, `sessions_total`, `sessions_sent`,
|
|
454
|
+
`started_at` and the developer id. No path or text. `turns_sent` counts turns
|
|
455
|
+
handed to the backend, not turns the backend has finished processing.
|
|
456
|
+
- **Gentle by design.** It runs at the lowest scheduling priority in a process of
|
|
457
|
+
its own with a small memory ceiling, 20 turns per request, one request every
|
|
458
|
+
five seconds, newest sessions first. It waits while the machine is busy (load
|
|
459
|
+
above half the cores), on battery power, or while an agent is closing turns,
|
|
460
|
+
and backs off on `429`, `5xx` and network errors. One run works for at most 20
|
|
461
|
+
minutes; an unfinished replay continues when the next agent session starts.
|
|
462
|
+
- **Control.** `agentwatch setup --no-replay` skips without claiming the machine's
|
|
463
|
+
one automatic replay; `--replay-days N` changes that first window. After the
|
|
464
|
+
detached replay has initialized, it atomically writes `replay-attempted` in
|
|
465
|
+
the config directory; a process that never starts leaves setup free to retry.
|
|
466
|
+
Later setups, including one after a new sign-in, start nothing.
|
|
467
|
+
Existing replay state from an older Edge also creates that marker. Explicit
|
|
468
|
+
`agentwatch replay --machine` or `--root <path>` can still start fresh; add
|
|
469
|
+
`--resume` to carry on or `--stop` to abandon that selected identity's run.
|
|
470
|
+
`agentwatch replay --dry-run` builds and counts every record and sends and
|
|
471
|
+
writes nothing. `agentwatch status` shows its progress. The same
|
|
472
|
+
capture switches that govern live records govern replay: `capture.git: false`
|
|
473
|
+
sends no repository, branch or ticket keys; `capture.files: false` no paths.
|
|
474
|
+
- **On disk.** `replay-attempted` in the config directory records the machine's
|
|
475
|
+
automatic attempt. `identity/<id>/replay.json` holds progress and completed
|
|
476
|
+
transcript files; an empty `replay-pending` marker exists while one is unfinished. The
|
|
477
|
+
transcripts themselves are only read, never copied or changed. `uninstall
|
|
478
|
+
--purge` removes both.
|
|
479
|
+
|
|
480
|
+
### `repo.tree`
|
|
481
|
+
|
|
482
|
+
A tree contains the same identity fields as a snapshot (`provider`, `surface`,
|
|
483
|
+
`repository`, optional `developer_id`), plus `captured_at`, `truncated` and
|
|
484
|
+
`files`. Each file is `{ path, names }`: no blob id, no tree id and no branch
|
|
485
|
+
name are sent. It is what a tenant with no GitHub App gets its code feature
|
|
486
|
+
catalog named from.
|
|
487
|
+
|
|
488
|
+
- **Which tree.** The default branch as the remote knows it (`origin/<trunk>`),
|
|
489
|
+
the local trunk only when that ref does not exist. Read from git's object
|
|
490
|
+
store (`git ls-tree`, `git grep <tree>`), never the working copy: uncommitted
|
|
491
|
+
files, local edits and other branches are not in it.
|
|
492
|
+
- **Which files.** Source files only, by extension (TS/JS, Python, Go, Ruby,
|
|
493
|
+
Rust, Java, Kotlin, Elixir, PHP, Dart, C#, SQL, Prisma, C/C++/Objective-C,
|
|
494
|
+
IDL), minus tests, fixtures, vendored, built and `node_modules` trees, docs,
|
|
495
|
+
migrations and `.d.ts`. Credential-named files, over-long paths and paths
|
|
496
|
+
with control characters are left out, as in a snapshot.
|
|
497
|
+
- **`names`.** The identifiers a file declares at top level, as `git grep -o`
|
|
498
|
+
prints the matching declaration line's head: exported TS/JS declarations,
|
|
499
|
+
column-0 Python and Ruby `def`/`class`/`module`, exported Go functions, Java,
|
|
500
|
+
Kotlin, C#, PHP, Rust and Dart type names and column-0 functions, Elixir
|
|
501
|
+
modules. The one string content read is a **route path** from a Nest, Express
|
|
502
|
+
or Spring route declaration (`'v1/invoices'`). **No function body, comment,
|
|
503
|
+
string literal or other code is read out of git.** A blob over 1 MiB or
|
|
504
|
+
binary sends no names. At most 64 names per file, 200 characters each.
|
|
505
|
+
- **Bounds.** At most 20,000 files and ~4 MiB per record; over a bound, files
|
|
506
|
+
are kept in `ls-tree` order and `truncated` is `true`.
|
|
507
|
+
- **When.** Once per repository per install identity: on the first closed turn
|
|
508
|
+
in that repository, inside the snapshot's one-second budget. Once queued, it is
|
|
509
|
+
never sent again for that identity — later trunk changes are not re-sent (the
|
|
510
|
+
files a session changes already travel in its turn summary and branch
|
|
511
|
+
snapshot). A re-setup with a new credential, or another account, sends it
|
|
512
|
+
again. A failed attempt (no trunk, listing failed, budget spent) is retried at
|
|
513
|
+
most hourly until the first tree is queued; the queue then retries delivery.
|
|
514
|
+
The snapshot state file on the machine records that the tree was sent, its
|
|
515
|
+
git tree id and a digest of the identity it was sent as — never the
|
|
516
|
+
credential; none of these is sent.
|
|
517
|
+
- **Consent.** Needs both `capture.git` and `capture.files`; a repository's own
|
|
518
|
+
`capture.files: false` stops the listing from running at all. A queued tree is
|
|
519
|
+
discarded at delivery when either flag is off.
|
|
520
|
+
|
|
521
|
+
Declaration and route names are identifiers chosen by developers and can reveal
|
|
522
|
+
product or business vocabulary, the same as file paths do; they are metadata,
|
|
523
|
+
not code, and run through the same secret scrubber as every record.
|
|
524
|
+
|
|
304
525
|
Remote URL userinfo is removed before normalization. Normalization yields
|
|
305
526
|
`host/org/repo`, omitting scheme, query, fragment and `.git` suffix. A SHA-256 hash
|
|
306
527
|
of that normalized identity is available for Git attribution. **Repository names
|
|
@@ -436,7 +657,8 @@ blob id: the SHA-1 Git itself assigns the content (`git hash-object`). A file ov
|
|
|
436
657
|
on both the named path and its real target; other names such as `.envrc` or
|
|
437
658
|
`credentials-prod.json` are not skipped), and a file whose real path lies
|
|
438
659
|
outside the session folder, symlinks included, is skipped. The summary carries up
|
|
439
|
-
to 20 `{
|
|
660
|
+
to 20 `{blob_sha}` entries, without the file's path (older releases sent the path
|
|
661
|
+
beside it; a summary they queued loses it at delivery). This feature adds no file content and no path from outside the session folder: a file whose real path lies outside it is skipped, and only its name can appear, under `external_files_touched` or `external_files_read` when `files` is on, as described above. With debug logging on, a failed read can log that file's path on this machine. A blob id is an object id of the same kind as the commit SHAs already
|
|
440
662
|
sent, but a guessable file's id can still be confirmed by someone who has that
|
|
441
663
|
file.
|
|
442
664
|
|
|
@@ -466,6 +688,21 @@ them, with the rest of the message, in the dead-letter topic until Pub/Sub expir
|
|
|
466
688
|
Developer identity is the configured `developerEmail`, falling back to Git email
|
|
467
689
|
resolution. Setup requires an identity. The email is sent as `developer_id` and
|
|
468
690
|
used for enforcement. It is not currently pseudonymized with a tenant HMAC.
|
|
691
|
+
Cursor also names the email its own account is signed in as (`user_email` on
|
|
692
|
+
every hook). That address is sent as `account_email` on Cursor turn summaries,
|
|
693
|
+
beside `developer_id` and never in its place, under the same rule: identity, not
|
|
694
|
+
content, so no capture flag gates it and it is not pseudonymized. It can differ
|
|
695
|
+
from the git or configured email; the platform uses it to join Cursor's own
|
|
696
|
+
usage export to the turns. It is the login for the whole machine, while
|
|
697
|
+
`developer_id` is chosen per root, so it is withheld on a machine whose config
|
|
698
|
+
serves more than one tenant (two install keys or devices). Cursor's
|
|
699
|
+
`composer_mode` and `is_background_agent`, named on its sessionStart only, are
|
|
700
|
+
kept in local turn state (mode 0600) and sent as `session_mode` and
|
|
701
|
+
`is_cloud_agent` on each later turn summary of that session. The memo survives
|
|
702
|
+
SessionEnd, like the opening prompt keys, for a conversation continued without
|
|
703
|
+
a new start, and goes with the 24 h idle sweep. They state the mode the session
|
|
704
|
+
started in; a switch inside the conversation is not seen, and a conversation
|
|
705
|
+
idle past the sweep, or started before AgentWatch was installed, carries none.
|
|
469
706
|
An installation UUID also identifies the installation. Native providers may send
|
|
470
707
|
their own session/account/resource identifiers independently.
|
|
471
708
|
|
|
@@ -514,7 +751,7 @@ The data root is `$XDG_DATA_HOME/agentwatch`, falling back to
|
|
|
514
751
|
is used; Windows deployment is not verified. `AGENTWATCH_DATA_DIR` overrides it.
|
|
515
752
|
|
|
516
753
|
The data root contains `queue/`, `turns/`, `backups/`, `locks/`, `snapshots/`,
|
|
517
|
-
`checkouts/`, delivery/cooldown/enforcement state, and `disabled.json` when off.
|
|
754
|
+
`checkouts/`, delivery/cooldown/enforcement state, replay progress (`identity/<id>/replay.json`), and `disabled.json` when off.
|
|
518
755
|
The queue contains sanitized product records and their destination, attempts,
|
|
519
756
|
and retry timestamps. Defaults are 2,000 events, 20 attempts, and 7 days.
|
|
520
757
|
Expiration is processed during activity, not by a daemon or scheduled erasure.
|
|
@@ -135,7 +135,7 @@ did, so no dependency lifecycle script executes in the job that builds the
|
|
|
135
135
|
published tarball; `npm audit --omit=dev --audit-level=high` gates on advisories
|
|
136
136
|
in what actually ships; the release workflow is dispatch-only, nothing runs on pull requests; and Dependabot
|
|
137
137
|
opens grouped weekly updates for both npm and the pinned actions. Package verification permits built JS/types and public
|
|
138
|
-
documentation only, with a
|
|
138
|
+
documentation only, with a 3 MB unpacked review ceiling. Hundreds of small files
|
|
139
139
|
are expected from the existing module layout and declarations; bundling solely
|
|
140
140
|
to reduce the file count is deferred.
|
|
141
141
|
|
package/docs/PERFORMANCE.md
CHANGED
|
@@ -57,6 +57,33 @@ a ten-branch snapshot whose every branch is at the cap carries at most ~210 KB o
|
|
|
57
57
|
25 such snapshots in one drain pass stay under the gateway's 8 MiB body limit. If the output
|
|
58
58
|
ceiling (1 MiB) cuts a listing short, the commits it did not reach are sent without `files`.
|
|
59
59
|
|
|
60
|
+
Branches already on trunk, October 25, 2026: same machine, git 2.50. Each checked branch
|
|
61
|
+
with commits costs one `merge-tree --write-tree` and one `rev-parse` more (~25–50 ms on
|
|
62
|
+
agent-watch-core); a branch with no delta or a `[gone]` upstream costs less than before, and a
|
|
63
|
+
remembered merged one costs nothing. Merged branches take no slot, so the walk reads deeper:
|
|
64
|
+
agent-watch-core (294 local branches) found its ten live branches 46 down the listing, with 18
|
|
65
|
+
git checks and 27 gone upstreams. First snapshot from an empty cache, one-second budget:
|
|
66
|
+
agent-watch-core 561 ms, agent-watch-edge 544 ms, infra-live 464 ms, the rest under 110 ms;
|
|
67
|
+
every repository finished in that first turn, and the next turn stopped at the cache diff in
|
|
68
|
+
20–31 ms.
|
|
69
|
+
|
|
70
|
+
Trunk tree in `repo.tree`, October 25, 2026: same machine. Once per repository per
|
|
71
|
+
install identity, the first closing hook in a repository runs `ls-tree -r -l -z` and three
|
|
72
|
+
`git grep -o <tree>` searches side by side (the spike's declarations as one anchored ERE,
|
|
73
|
+
route paths as PCRE, the extra languages over their own files), inside the snapshot's
|
|
74
|
+
one-second budget. Every later turn reads the snapshot state file and stops: no git
|
|
75
|
+
process. Five runs each, warm cache, real state file, event bytes after sanitizing:
|
|
76
|
+
|
|
77
|
+
| Repository | Source files | Names | Event bytes | First turn | Every later turn |
|
|
78
|
+
| --- | ---: | ---: | ---: | ---: | ---: |
|
|
79
|
+
| agent-watch-core | 1,704 | 6,080 | 341,340 | 195–236 ms | 0.15–0.35 ms, 0 git |
|
|
80
|
+
| tripPlanner | 699 | 2,372 | 141,447 | 95–180 ms | 0.15–0.28 ms, 0 git |
|
|
81
|
+
| agent-watch-edge | 266 | 1,366 | 55,407 | 81–142 ms | 0.12–0.14 ms, 0 git |
|
|
82
|
+
|
|
83
|
+
Anchoring matters: one search mixing anchored and unanchored patterns took ~800 ms on
|
|
84
|
+
agent-watch-core, because git can no longer reject a line at its first byte. A tree is
|
|
85
|
+
drained last and alone in its own batch, so it never shares the gateway's 8 MiB body limit.
|
|
86
|
+
|
|
60
87
|
These are observations, not an SLA or a cross-machine comparison. At 30 samples,
|
|
61
88
|
p99 is effectively the maximum. CI retains its own JSON measurements on Linux
|
|
62
89
|
and macOS rather than enforcing unstable absolute timing thresholds on shared
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@agent-watch-ai/edge",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.7.0",
|
|
4
4
|
"description": "Usage and cost telemetry for Claude Code, Codex, Cursor, Gemini CLI and Antigravity. No daemon, no proxy.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"type": "module",
|
|
@@ -34,6 +34,7 @@
|
|
|
34
34
|
},
|
|
35
35
|
"files": [
|
|
36
36
|
"dist",
|
|
37
|
+
"!dist/capture/python/__pycache__",
|
|
37
38
|
"README.md",
|
|
38
39
|
"SECURITY.md",
|
|
39
40
|
"docs/AUDIT_PROMPT.md",
|
|
@@ -44,7 +45,7 @@
|
|
|
44
45
|
"CHANGELOG.md"
|
|
45
46
|
],
|
|
46
47
|
"scripts": {
|
|
47
|
-
"build": "tsc -p tsconfig.build.json",
|
|
48
|
+
"build": "tsc -p tsconfig.build.json && node -e \"require('node:fs').cpSync('src/capture/python/sitecustomize.py','dist/capture/python/sitecustomize.py')\"",
|
|
48
49
|
"typecheck": "tsc --noEmit",
|
|
49
50
|
"coverage": "vitest run --coverage",
|
|
50
51
|
"benchmark": "npm run build && node scripts/benchmark.mjs",
|
|
@@ -1,10 +0,0 @@
|
|
|
1
|
-
/**
|
|
2
|
-
* The canonical event vocabulary and shape.
|
|
3
|
-
*
|
|
4
|
-
* Kept as the module's stable entry point: the vocabulary lives in
|
|
5
|
-
* `constants/events.constants.ts` and the shape in `types/events.types.ts`, so
|
|
6
|
-
* a reader looking for "what can happen" and a reader looking for "what a
|
|
7
|
-
* record looks like" each land in one file.
|
|
8
|
-
*/
|
|
9
|
-
export { CANONICAL_EVENT_TYPES, EVENT_SCHEMA_VERSION, INTERNAL_HOOK_EVENT_TYPES, PRODUCT_EVENT_TYPES, PRODUCT_EVENT_TYPE_SET, TURN_CLOSING_EVENT_TYPE } from './constants/events.constants.js';
|
|
10
|
-
export type { AgentWatchEvent, CanonicalEventType, ContentEvidence, EventAi, EventGit, EventIdInput, EventPatch, EventSession, EventTool, EventUsage, FeatureCandidate, InternalHookEventType, ProductEventType, UsageBillingMode, UsageSource } from './types/events.types.js';
|
|
@@ -1,9 +0,0 @@
|
|
|
1
|
-
/**
|
|
2
|
-
* The canonical event vocabulary and shape.
|
|
3
|
-
*
|
|
4
|
-
* Kept as the module's stable entry point: the vocabulary lives in
|
|
5
|
-
* `constants/events.constants.ts` and the shape in `types/events.types.ts`, so
|
|
6
|
-
* a reader looking for "what can happen" and a reader looking for "what a
|
|
7
|
-
* record looks like" each land in one file.
|
|
8
|
-
*/
|
|
9
|
-
export { CANONICAL_EVENT_TYPES, EVENT_SCHEMA_VERSION, INTERNAL_HOOK_EVENT_TYPES, PRODUCT_EVENT_TYPES, PRODUCT_EVENT_TYPE_SET, TURN_CLOSING_EVENT_TYPE } from './constants/events.constants.js';
|
|
@@ -1,39 +0,0 @@
|
|
|
1
|
-
import type { RepositoryRootFinder } from './types/repository-root.types.js';
|
|
2
|
-
export type { RepositoryRootFinder } from './types/repository-root.types.js';
|
|
3
|
-
/**
|
|
4
|
-
* A finder for the repository each file belongs to, when the session's own
|
|
5
|
-
* folder is not one.
|
|
6
|
-
*
|
|
7
|
-
* Bounded by `boundary` — the folder the session started in — for two reasons:
|
|
8
|
-
* a repository outside it is another project's, possibly another tenant's, and
|
|
9
|
-
* a bounded walk is a handful of `stat` calls rather than an unbounded climb to
|
|
10
|
-
* the filesystem root.
|
|
11
|
-
*
|
|
12
|
-
* ponytail: presence of a `.git` entry is the whole test, and the answer is the
|
|
13
|
-
* *nearest* ancestor that has one — so a file inside a submodule or a vendored
|
|
14
|
-
* checkout belongs to that inner repository, which is also what git itself
|
|
15
|
-
* would answer from that directory. It does not understand `GIT_DIR`, a bare
|
|
16
|
-
* repository, or a `.git` file pointing outside the tree. The upgrade path is
|
|
17
|
-
* `git rev-parse --show-toplevel` behind this same cache — deliberately not the
|
|
18
|
-
* implementation: a subprocess per tool call would sit on the coding agent's
|
|
19
|
-
* critical path.
|
|
20
|
-
*
|
|
21
|
-
* @param boundary - Folder the walk stops at, inclusive.
|
|
22
|
-
* @returns A finder whose answers are memoized per directory.
|
|
23
|
-
*/
|
|
24
|
-
export declare function repositoryRootFinder(boundary: string): RepositoryRootFinder;
|
|
25
|
-
/**
|
|
26
|
-
* Whether a path is a directory or lies inside it.
|
|
27
|
-
*
|
|
28
|
-
* The two answers that disqualify it are a relative path that climbs out and
|
|
29
|
-
* one that stays absolute (a different drive or root). A sibling named
|
|
30
|
-
* `..foo` climbs nowhere, which is why the separator is part of the test.
|
|
31
|
-
*
|
|
32
|
-
* Exported because the same question is asked of a repository path read back
|
|
33
|
-
* out of local turn state: one answer, not two that could disagree.
|
|
34
|
-
*
|
|
35
|
-
* @param boundary - Folder that bounds the walk.
|
|
36
|
-
* @param target - Path to test against it.
|
|
37
|
-
* @returns True when the target is the boundary or beneath it.
|
|
38
|
-
*/
|
|
39
|
-
export declare function isBeneath(boundary: string, target: string): boolean;
|