@fibteq/altair-runner 0.2.1 → 0.2.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 +3 -2
- package/dist/cli.js +27 -26
- package/dist/index.js +29 -29
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -20,6 +20,7 @@ Requires Node 22+ and at least one of `claude`, `codex` or `gemini` on your `PAT
|
|
|
20
20
|
```sh
|
|
21
21
|
npx altair-runner pair ABCD-1234 --server https://altair.example.com # code from Altair > Devices
|
|
22
22
|
npx altair-runner service install # runs now and at every login
|
|
23
|
+
npx altair-runner@latest update # later: update and restart it
|
|
23
24
|
```
|
|
24
25
|
|
|
25
26
|
Then add folders in Altair > Devices with **Add folder**: it browses this computer's folders through the runner
|
|
@@ -42,8 +43,8 @@ cache) and registers it to start at login:
|
|
|
42
43
|
|
|
43
44
|
It keeps the `PATH` of the terminal you install it from, which is where it finds `claude`, `codex` and `gemini`.
|
|
44
45
|
On macOS and Linux it restarts after a crash, but not after a clean stop (the computer was removed in Altair, or
|
|
45
|
-
`altair-runner start` was run somewhere else with the same pairing).
|
|
46
|
-
|
|
46
|
+
`altair-runner start` was run somewhere else with the same pairing). `altair-runner update` installs the newest version
|
|
47
|
+
from npm and restarts the background runner on it (`service install` again also restarts it); `service status` shows its state and
|
|
47
48
|
`service uninstall` removes it. On Linux it starts when you log in; to start at boot without logging in, run
|
|
48
49
|
`loginctl enable-linger`.
|
|
49
50
|
|