@pathrule/cli 0.0.13 → 0.0.15
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 +58 -5
- package/dist/index.js +3052 -452
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -60,10 +60,18 @@ pathrule setup --workspace <workspace-id-or-name> --target all --yes
|
|
|
60
60
|
|
|
61
61
|
## Install Options
|
|
62
62
|
|
|
63
|
-
|
|
63
|
+
Pathrule CLI requires Node.js `>=20.11.1` on every supported platform.
|
|
64
|
+
After install, the binary lives at whatever path your npm global prefix
|
|
65
|
+
puts it — verify with `command -v pathrule` (macOS/Linux) or
|
|
66
|
+
`where pathrule` (Windows).
|
|
67
|
+
|
|
68
|
+
### macOS
|
|
64
69
|
|
|
65
70
|
```bash
|
|
66
71
|
npm i -g @pathrule/cli
|
|
72
|
+
pathrule login
|
|
73
|
+
pathrule setup
|
|
74
|
+
pathrule doctor
|
|
67
75
|
```
|
|
68
76
|
|
|
69
77
|
Upgrade:
|
|
@@ -72,18 +80,63 @@ Upgrade:
|
|
|
72
80
|
npm i -g @pathrule/cli@latest
|
|
73
81
|
```
|
|
74
82
|
|
|
75
|
-
###
|
|
83
|
+
### Linux
|
|
76
84
|
|
|
77
85
|
```bash
|
|
78
|
-
|
|
86
|
+
npm i -g @pathrule/cli
|
|
87
|
+
pathrule login
|
|
88
|
+
pathrule setup
|
|
89
|
+
pathrule doctor
|
|
79
90
|
```
|
|
80
91
|
|
|
81
|
-
|
|
92
|
+
Optional: the bridge daemon can run under `systemd --user` if your
|
|
93
|
+
distro ships user services. `pathrule daemon start` works without
|
|
94
|
+
systemd; the daemon stays foreground until you stop it.
|
|
95
|
+
|
|
96
|
+
### Windows
|
|
97
|
+
|
|
98
|
+
```powershell
|
|
99
|
+
npm i -g @pathrule/cli
|
|
100
|
+
pathrule login
|
|
101
|
+
pathrule setup
|
|
102
|
+
pathrule doctor
|
|
103
|
+
```
|
|
104
|
+
|
|
105
|
+
Notes:
|
|
106
|
+
|
|
107
|
+
- Windows autostart for the bridge daemon is not yet wired up. Start
|
|
108
|
+
it manually with `pathrule daemon start`. `pathrule daemon status
|
|
109
|
+
--json` reports `supported: false, method: "task-scheduler"` so
|
|
110
|
+
scripts can distinguish a planned no-op from a real failure.
|
|
111
|
+
- The CLI writes a `pathrule-hook.cmd` shim next to `pathrule-hook.js`
|
|
112
|
+
inside `%USERPROFILE%\.pathrule\bin\`. AI clients that spawn hooks
|
|
113
|
+
without a shell (Codex on Windows) execute the `.cmd` directly.
|
|
114
|
+
- If you use a corporate proxy or custom CA, set `HTTPS_PROXY`,
|
|
115
|
+
`HTTP_PROXY`, `NO_PROXY`, or `NODE_EXTRA_CA_CERTS` in the env before
|
|
116
|
+
running `pathrule install <client>` — the CLI propagates those values
|
|
117
|
+
into the managed MCP entry so AI-client-spawned MCP can still reach
|
|
118
|
+
Supabase.
|
|
119
|
+
|
|
120
|
+
### Homebrew (macOS)
|
|
121
|
+
|
|
122
|
+
The Homebrew formula is generated by every release but the tap is not
|
|
123
|
+
yet publishing publicly. Until the `pathrule/homebrew-tap` repository
|
|
124
|
+
goes live, prefer `npm i -g @pathrule/cli@latest`. Once the tap is up,
|
|
125
|
+
`brew upgrade pathrule` will be advertised through `versions.json`.
|
|
126
|
+
|
|
127
|
+
### Local-state override
|
|
128
|
+
|
|
129
|
+
Pathrule keeps per-user state in `~/.pathrule` on every supported OS by
|
|
130
|
+
default. Override with `PATHRULE_HOME` if you need a custom location:
|
|
82
131
|
|
|
83
132
|
```bash
|
|
84
|
-
|
|
133
|
+
PATHRULE_HOME=/srv/pathrule pathrule sync
|
|
85
134
|
```
|
|
86
135
|
|
|
136
|
+
`pathrule install <client>` propagates the active `PATHRULE_HOME` into
|
|
137
|
+
the managed MCP entry so AI-client-spawned MCP reads the same
|
|
138
|
+
credentials.
|
|
139
|
+
|
|
87
140
|
## Authentication
|
|
88
141
|
|
|
89
142
|
Most users do not need to run `pathrule login` manually. `pathrule setup`
|