@node9/proxy 1.0.6 → 1.0.7

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 +45 -3
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -16,7 +16,7 @@ While others try to _guess_ if a prompt is malicious (Semantic Security), Node9
16
16
  **AIs are literal.** When you ask an agent to "Fix my disk space," it might decide to run `docker system prune -af`.
17
17
 
18
18
  <p align="center">
19
- <img src="https://github.com/user-attachments/assets/0e45e843-4cf7-408e-95ce-23fb09525ee4" width="100%">
19
+ <img src="https://github.com/user-attachments/assets/afae9caa-0605-4cac-929a-c14198383169" width="100%">
20
20
  </p>
21
21
 
22
22
  **With Node9, the interaction looks like this:**
@@ -232,7 +232,7 @@ The `field` key supports dot-notation for nested args: `"params.query.sql"`.
232
232
 
233
233
  Use `node9 explain <tool> <args>` to dry-run any tool call and see exactly which smart rule (or other policy tier) would trigger.
234
234
 
235
- ---
235
+ ## <<<<<<< Updated upstream
236
236
 
237
237
  ## 🖥️ CLI Reference
238
238
 
@@ -332,7 +332,49 @@ All checks passed ✅
332
332
 
333
333
  ### `node9 explain`
334
334
 
335
- Dry-runs the policy engine and prints exactly which rule (or waterfall tier) would block or allow a given tool call — useful for debugging your config:
335
+ ## =======
336
+
337
+ ## 🖥️ CLI Reference
338
+
339
+ | Command | Description |
340
+ | :---------------------------- | :------------------------------------------------------------------------------------ |
341
+ | `node9 setup` | Interactive menu — detects installed agents and wires hooks for you |
342
+ | `node9 addto <agent>` | Wire hooks for a specific agent (`claude`, `gemini`, `cursor`) |
343
+ | `node9 init` | Create default `~/.node9/config.json` |
344
+ | `node9 status` | Show current protection status and active rules |
345
+ | `node9 doctor` | Health check — verifies binaries, config, credentials, and all agent hooks |
346
+ | `node9 explain <tool> [args]` | Trace the policy waterfall for a given tool call (dry-run, no approval prompt) |
347
+ | `node9 undo [--steps N]` | Revert the last N AI file edits using shadow Git snapshots |
348
+ | `node9 check` | Called by agent hooks; evaluates a pending tool call and exits 0 (allow) or 1 (block) |
349
+
350
+ ### `node9 doctor`
351
+
352
+ Runs a full self-test and exits 1 if any required check fails:
353
+
354
+ ```
355
+ Node9 Doctor v1.2.0
356
+ ────────────────────────────────────────
357
+ Binaries
358
+ ✅ Node.js v20.11.0
359
+ ✅ git version 2.43.0
360
+
361
+ Configuration
362
+ ✅ ~/.node9/config.json found and valid
363
+ ✅ ~/.node9/credentials.json — cloud credentials found
364
+
365
+ Agent Hooks
366
+ ✅ Claude Code — PreToolUse hook active
367
+ ⚠️ Gemini CLI — not configured (optional)
368
+ ⚠️ Cursor — not configured (optional)
369
+
370
+ ────────────────────────────────────────
371
+ All checks passed ✅
372
+ ```
373
+
374
+ ### `node9 explain`
375
+
376
+ > > > > > > > Stashed changes
377
+ > > > > > > > Dry-runs the policy engine and prints exactly which rule (or waterfall tier) would block or allow a given tool call — useful for debugging your config:
336
378
 
337
379
  ```bash
338
380
  node9 explain bash '{"command":"rm -rf /tmp/build"}'
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@node9/proxy",
3
- "version": "1.0.6",
3
+ "version": "1.0.7",
4
4
  "description": "The Sudo Command for AI Agents. Execution Security for Claude Code & MCP.",
5
5
  "main": "./dist/index.js",
6
6
  "module": "./dist/index.mjs",