@node9/proxy 1.10.1 → 1.10.3

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/README.md CHANGED
@@ -128,9 +128,13 @@ configure(agent_name="my-agent", policy="require_approval")
128
128
 
129
129
  ---
130
130
 
131
- ## Flight Recorder & HUD
131
+ ## Observability
132
132
 
133
- Every tool call your AI agent makes is recorded — command, arguments, result, and cost estimate. Node9 wires a live statusline into Claude Code that shows you what's happening in real time:
133
+ Every tool call your AI agent makes is recorded — command, arguments, result, and cost estimate. Node9 gives you four ways to see what your agent is doing.
134
+
135
+ ### Live HUD (statusline)
136
+
137
+ Node9 wires a live statusline into Claude Code that shows you what's happening in real time:
134
138
 
135
139
  ```
136
140
  🛡 node9 | standard | [bash-safe] | ✅ 12 allowed 🛑 2 blocked 🚨 0 dlp | ~$0.43 | ⚡ no-force-push
@@ -146,9 +150,20 @@ Every tool call your AI agent makes is recorded — command, arguments, result,
146
150
 
147
151
  The HUD is wired automatically by `node9 init`. Full session logs land in `~/.node9/audit.log`.
148
152
 
149
- ### Offline Report
153
+ ### `node9 tail` — live stream
154
+
155
+ Stream every tool call as it happens. Useful when you send an agent off to work and want to watch what it's doing:
156
+
157
+ ```bash
158
+ node9 tail # stream tool calls for the active session
159
+ node9 tail --all # include all projects
160
+ ```
161
+
162
+ Each line shows the tool name, a summary of its arguments, and the decision (allowed / blocked / DLP hit).
163
+
164
+ ### `node9 report` — security dashboard
150
165
 
151
- Run `node9 report` after a session to get a summary dashboard what was allowed, what was blocked, DLP hits, cost (Claude Code only), and daily activity:
166
+ Run after a session to get a summary of what was allowed, blocked, DLP hits, cost, and daily activity:
152
167
 
153
168
  ```
154
169
  $ node9 report --period 7d
@@ -175,6 +190,92 @@ $ node9 report --period 7d
175
190
 
176
191
  Periods: `today`, `7d` (default), `30d`, `month`. Cost data is read from `~/.claude/projects/` — no API calls, fully offline.
177
192
 
193
+ ### `node9 sessions` — session history
194
+
195
+ See what your AI agent did across sessions — prompt, tool calls, cost, files modified, and whether a snapshot was taken. Useful when you hand off a task and come back to review what happened:
196
+
197
+ ```
198
+ $ node9 sessions --all
199
+
200
+ 📋 node9 sessions — what your AI agent did
201
+
202
+ 7 sessions $178.93 total 2379 tool calls 122 files modified
203
+ avg $25.56 /session 7 of 7 sessions had snapshots
204
+
205
+ Tool breakdown:
206
+ Bash ████████████████████ 1165 (49%)
207
+ Read ███████████░░░░░░░░░ 613 (26%)
208
+ Edit ██████░░░░░░░░░░░░░░ 367 (15%)
209
+ Other ███░░░░░░░░░░░░░░░░░ 203 (9%)
210
+ Write █░░░░░░░░░░░░░░░░░░░ 31 (1%)
211
+
212
+ ─── Apr 15 ~/node9
213
+ 14:47 implement delegated sessions feature 919 tools $74.45 📸 00ac39e2
214
+ 12:47 ok, it seems you crash and we have a bug… 95 tools $6.40 📸 5a4e7fab
215
+ ```
216
+
217
+ Drill into any session for a full tool trace:
218
+
219
+ ```
220
+ $ node9 sessions --detail 4812594b
221
+
222
+ Session 4812594b-c93f-4a26-91f0-44aa2e324918
223
+ Prompt can you push node9-proxy to git dev?
224
+ Project ~/node9
225
+ When Apr 9, 2026, 20:49
226
+ Cost ~$2.06
227
+ Snapshot ✓ taken
228
+
229
+ Tool calls (54):
230
+ 20:49 Bash git status && git branch -a
231
+ 20:52 Write /home/nadav/node9/node9-proxy/.git/hooks/pre-commit
232
+ 20:56 Edit /home/nadav/node9/node9-proxy/src/cli/commands/check.ts
233
+ ...
234
+
235
+ Files modified (3):
236
+ /home/nadav/node9/node9-proxy/.git/hooks/pre-commit
237
+ /home/nadav/node9/node9-proxy/src/cli/commands/check.ts
238
+ /home/nadav/node9/node9-proxy/src/cli/hud.ts
239
+ ```
240
+
241
+ ```bash
242
+ node9 sessions # last 7 days
243
+ node9 sessions --all # all time
244
+ node9 sessions --days 30 # last 30 days
245
+ node9 sessions --detail <session-id> # full tool trace (prefix match on session ID)
246
+ ```
247
+
248
+ Currently works with Claude Code. Support for other agents coming as they expose session history.
249
+
250
+ ### `node9 scan` — day-0 forecast
251
+
252
+ Not installed yet? Run `node9 scan` against your existing Claude Code history to see what Node9 **would have caught** if it had been running:
253
+
254
+ ```
255
+ $ node9 scan
256
+
257
+ 🔍 node9 scan — what would node9 catch?
258
+
259
+ 42 sessions 3,891 tool calls 1,165 bash commands last 90 days
260
+
261
+ If node9 had been installed: 23 commands flagged for review
262
+
263
+ bash-safe · 12 findings → node9 shield enable bash-safe
264
+ block-pipe-to-shell ×8 — Pipe-to-shell is a common supply-chain attack vector
265
+ review-eval ×4 — eval of dynamic content requires human approval
266
+
267
+ Secrets / DLP · 2 potential secret leaks
268
+ aws-access-key AKIA**************** Bash Apr 12
269
+ ```
270
+
271
+ `scan` reads raw JSONL history and runs the real policy engine — same shields and rules that would fire in production. No audit log needed.
272
+
273
+ ```bash
274
+ node9 scan # last 90 days
275
+ node9 scan --all # all time
276
+ node9 scan --days 30 # custom window
277
+ ```
278
+
178
279
  ---
179
280
 
180
281
  ## 📖 Full docs