conductor-remote 1.42.0 → 1.42.2
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 +25 -0
- package/bin/cli.js +8 -0
- package/dist/assets/{index-BNMm_aez.js → index-DFdIcbun.js} +3 -3
- package/dist/index.html +1 -1
- package/dist/sw.js +1 -1
- package/dist-node/scripts/service.js +156 -1
- package/dist-node/src/mcp-tools.js +22 -20
- package/dist-node/src/reads.js +1 -14
- package/dist-node/src/search.js +8 -9
- package/dist-node/src/shared.js +59 -0
- package/dist-node/src/wire.js +23 -0
- package/package.json +3 -2
package/README.md
CHANGED
|
@@ -39,6 +39,12 @@ on your machine, so `npm i -g` finishes in about a second. `service install`
|
|
|
39
39
|
prints a phone URL with an embedded token; open it and **Add to Home Screen**.
|
|
40
40
|
Manage the service with `conductor-remote service status|restart|uninstall`.
|
|
41
41
|
|
|
42
|
+
`conductor-remote config` prints what the daemon is **actually** configured with and
|
|
43
|
+
where each value came from, then cross-checks the configured reachability against what
|
|
44
|
+
Tailscale is really doing. Read-only. Reach for it first when the relay is behaving like
|
|
45
|
+
a setting you thought you changed never took, because the values it reports come from the
|
|
46
|
+
daemon's own environment rather than your shell's.
|
|
47
|
+
|
|
42
48
|
**Install flags.** `service install` takes flags for the install-time knobs (each
|
|
43
49
|
also settable via the env var in brackets — the flag wins when both are given).
|
|
44
50
|
Run `conductor-remote --help` for the full list. The common ones:
|
|
@@ -157,6 +163,25 @@ Each knob is an env var (honored by `yarn start` and `service install`) and, for
|
|
|
157
163
|
`service install`, the CLI flag in the second column. A flag wins over the ambient
|
|
158
164
|
env. `EXPOSE`/`--expose` is documented under Install above.
|
|
159
165
|
|
|
166
|
+
`service install` bakes these into the LaunchAgent plist, so that plist is the daemon's
|
|
167
|
+
environment and re-running `service install --<flag> <value>` is how you change one.
|
|
168
|
+
`conductor-remote config` reads them back:
|
|
169
|
+
|
|
170
|
+
```
|
|
171
|
+
$ conductor-remote config
|
|
172
|
+
plist: ~/Library/LaunchAgents/no.adluna.conductor-remote.plist
|
|
173
|
+
state: ~/Library/Application Support/conductor-remote
|
|
174
|
+
daemon: running (pid 85882)
|
|
175
|
+
|
|
176
|
+
expose tailnet plist
|
|
177
|
+
port 8787 default
|
|
178
|
+
write-strategy applescript default
|
|
179
|
+
…
|
|
180
|
+
token 99f6…6b38 token file
|
|
181
|
+
|
|
182
|
+
✓ tailscale agrees: serve only (tailnet)
|
|
183
|
+
```
|
|
184
|
+
|
|
160
185
|
| Var | Flag | Default | Purpose |
|
|
161
186
|
| --- | --- | --- | --- |
|
|
162
187
|
| `RELAY_PORT` | `--port` | `8787` | Listen port |
|
package/bin/cli.js
CHANGED
|
@@ -62,6 +62,8 @@ function usage() {
|
|
|
62
62
|
' read transcripts and drive workspaces via the relay',
|
|
63
63
|
' conductor-remote service <subcommand> manage the login LaunchAgent',
|
|
64
64
|
' install | uninstall | restart | status',
|
|
65
|
+
' conductor-remote config what the daemon is actually configured with, and',
|
|
66
|
+
' where each value came from (read-only)',
|
|
65
67
|
' conductor-remote logs [-n N] [--no-follow] tail the running relay’s logs (follows by default)',
|
|
66
68
|
' conductor-remote nosleep [duration] keep this Mac awake (incl. lid-closed) until',
|
|
67
69
|
' Ctrl-C or the duration (e.g. 1h, 90m)',
|
|
@@ -106,6 +108,12 @@ switch (cmd) {
|
|
|
106
108
|
process.argv = [process.argv[0], process.argv[1], ...rest]
|
|
107
109
|
await import(resolveEntry('../dist-node/scripts/nosleep.js', '../scripts/nosleep.ts'))
|
|
108
110
|
break
|
|
111
|
+
case 'config':
|
|
112
|
+
// Read-only view of the daemon's effective configuration. A service.ts subcommand, re-shaped the
|
|
113
|
+
// same way `logs` is, because the answer lives in the plist that script writes.
|
|
114
|
+
process.argv = [process.argv[0], process.argv[1], 'config']
|
|
115
|
+
await import(resolveEntry('../dist-node/scripts/service.js', '../scripts/service.ts'))
|
|
116
|
+
break
|
|
109
117
|
case 'logs':
|
|
110
118
|
// `logs` is a service.ts subcommand; re-shape argv so its argv[2] is `logs` (mirrors the `service` case).
|
|
111
119
|
process.argv = [process.argv[0], process.argv[1], 'logs', ...rest]
|