You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -192,9 +192,10 @@ This creates a `.tracevault/` directory and installs a pre-push hook. The hook r
192
192
```sh
193
193
tracevault sync # sync repo metadata with server
194
194
tracevault check # evaluate policies against server rules (blocks push on failure)
195
-
tracevault push # upload traces to server
196
195
```
197
196
197
+
Session and commit data is streamed to the server continuously via the Claude Code hooks (`tracevault stream`) and the git post-commit hook (`tracevault commit-push`), so there is no separate upload step.
198
+
198
199
The command also installs the Claude Code hook configuration in `.claude/settings.json`. Each hook runs `tracevault stream --event <type>`, which records the event locally and pushes it to the server in real time:
199
200
200
201
```json
@@ -228,7 +229,7 @@ The command also installs the Claude Code hook configuration in `.claude/setting
228
229
}
229
230
```
230
231
231
-
### 7. Authenticate and push traces
232
+
### 7. Authenticate
232
233
233
234
```sh
234
235
# Log in to a TraceVault server.
@@ -238,12 +239,12 @@ The command also installs the Claude Code hook configuration in `.claude/setting
238
239
# force that behaviour with `--no-browser` or `TRACEVAULT_NO_BROWSER=1`.
That's it. From this point on, every Claude Code session in this repo is automatically traced — tool calls, file edits, token usage, and model info are captured and streamed to the TraceVault server. When you `git push`, the pre-push hook evaluates policies and uploads traces.
281
+
That's it. From this point on, every Claude Code session in this repo is automatically traced — tool calls, file edits, token usage, and model info are captured and streamed to the TraceVault server as they happen. When you `git push`, the pre-push hook evaluates policies and blocks the push if any rule fails.
0 commit comments