byollm 0.1.5-beta.2 → 0.1.6
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 +39 -9
- package/dist/bin.js +1 -1
- package/dist/{chunk-GWC3CCIW.js → chunk-D6IRB3FG.js} +4757 -3923
- package/dist/chunk-D6IRB3FG.js.map +1 -0
- package/dist/index.d.ts +1312 -1262
- package/dist/index.js +1 -1
- package/package.json +2 -2
- package/dist/chunk-GWC3CCIW.js.map +0 -1
package/README.md
CHANGED
|
@@ -1,11 +1,18 @@
|
|
|
1
|
-
<!-- release-note 0.1.
|
|
2
|
-
> **`0.1.
|
|
3
|
-
>
|
|
4
|
-
>
|
|
1
|
+
<!-- release-note 0.1.6 -->
|
|
2
|
+
> **`0.1.6`: an automatic update brings this device back up, and every update
|
|
3
|
+
> writes down what it did.** `PROTOCOL_VERSION` is still `2`; update in any
|
|
4
|
+
> order. On macOS an update no longer ends with no service and nothing
|
|
5
|
+
> running (#9572): `byollm start` hands the re-register to a copy that waits
|
|
6
|
+
> for the old daemon to exit. **If an update to 0.1.5 left a Mac on
|
|
7
|
+
> `NOT RUNNING`, run `byollm start` once.** New: `byollm logs`, what this
|
|
8
|
+
> device did with each job, one line per event (#9547). Every update now
|
|
9
|
+
> writes `update:` lines to `~/.byollm/service.log` and `byollm logs`, from
|
|
10
|
+
> the update after this one (#9594). Full note:
|
|
11
|
+
> `docs/release-notes/0.1.6.md`.
|
|
5
12
|
>
|
|
6
13
|
> This README used to open with a stack of release notes instead of with the
|
|
7
14
|
> package. The history moved to `docs/release-notes/` and `CHANGELOG.md`,
|
|
8
|
-
> where none of it was lost.
|
|
15
|
+
> where none of it was lost.
|
|
9
16
|
|
|
10
17
|
# `byollm`
|
|
11
18
|
|
|
@@ -101,6 +108,21 @@ version. Every update is checked against its npm provenance before it runs and
|
|
|
101
108
|
rolled back if it fails; [`docs/security.md` §7a](https://github.com/oftomorrowinc/byollm/blob/main/docs/security.md#7a-updates)
|
|
102
109
|
says exactly what is checked.
|
|
103
110
|
|
|
111
|
+
Every update writes down what it did, one line per step, each beginning
|
|
112
|
+
`update:` and the time in UTC: the offer it took and from where, the drain,
|
|
113
|
+
the install, the provenance check, the re-register, and then the new
|
|
114
|
+
daemon's `now running 0.1.7, was 0.1.6`. A failure says which step failed,
|
|
115
|
+
npm's words, and whether the machine stayed, rolled back, or needs you, with
|
|
116
|
+
the two commands to run. They are in `~/.byollm/service.log` and in
|
|
117
|
+
`byollm logs`:
|
|
118
|
+
|
|
119
|
+
```bash
|
|
120
|
+
grep update: ~/.byollm/service.log
|
|
121
|
+
```
|
|
122
|
+
|
|
123
|
+
Written by the updater already on the device, so the first update with an
|
|
124
|
+
account is the one after 0.1.6.
|
|
125
|
+
|
|
104
126
|
You do not have to write any of this by hand. `byollm services manage` asks
|
|
105
127
|
what this machine has and writes the file for you, and it is safe to re-run:
|
|
106
128
|
it shows what is already there.
|
|
@@ -133,6 +155,8 @@ It installs at the user level on every platform — a launchd `LaunchAgent` on
|
|
|
133
155
|
macOS, a `systemd --user` unit on Linux, a logon task on Windows. No root, no
|
|
134
156
|
system directories: it runs as you, it stops when you say so, and you can read
|
|
135
157
|
every file it wrote. Output goes to `~/.byollm/service.log` on all three.
|
|
158
|
+
`byollm logs` reads the device's own event log rather than this file, so it
|
|
159
|
+
works the same under any supervisor and at a hosted box's `byollm>` console.
|
|
136
160
|
|
|
137
161
|
Two things worth knowing:
|
|
138
162
|
|
|
@@ -157,6 +181,9 @@ byollm status # what's connected, what's running, what you've done for o
|
|
|
157
181
|
byollm sites # which sites this device serves, and which keys it still holds
|
|
158
182
|
byollm log # every prompt that has ever run here
|
|
159
183
|
byollm log --full # the whole text, not the first line
|
|
184
|
+
byollm logs # what happened, one line per event: claimed, started, answered, failed
|
|
185
|
+
byollm logs --job 911c5d84 # one job's lines, and where it stands
|
|
186
|
+
byollm logs --follow # and keep printing as they happen (--tail N for more than 20)
|
|
160
187
|
byollm stop # stop running in the background — the off switch, always yours
|
|
161
188
|
byollm start # and bring it back
|
|
162
189
|
byollm forget <url> # drop a pairing entirely
|
|
@@ -237,12 +264,15 @@ locked to your own work — a protocol rule, not a setting you can change.
|
|
|
237
264
|
Every payload is treated as hostile input. Breakout is structurally
|
|
238
265
|
impossible: process-class backends get a fixed argv with the prompt on stdin,
|
|
239
266
|
a stripped environment, an empty scratch directory and hard timeout/output
|
|
240
|
-
caps; HTTP-class backends spawn nothing at all. The model has no tools
|
|
241
|
-
retrieval and no MCP.
|
|
267
|
+
caps; HTTP-class backends spawn nothing at all. The model has no tools that
|
|
268
|
+
run on your device, no retrieval and no MCP. A site's own tools (`llm.tools`,
|
|
269
|
+
off until you turn it on for a service) run on the site: the daemon seals each
|
|
270
|
+
call to that site, logs it first, and never executes it.
|
|
242
271
|
|
|
243
272
|
Prompt injection — steering what the model _says_ — is not prevented by
|
|
244
|
-
anything and we do not claim otherwise. It is bounded here because
|
|
245
|
-
|
|
273
|
+
anything and we do not claim otherwise. It is bounded here because nothing
|
|
274
|
+
the model says runs on the device: its output is inert, and a call to a site's
|
|
275
|
+
tool is sealed to that site and run there.
|
|
246
276
|
|
|
247
277
|
Full threat model, including what the OS stops us dropping:
|
|
248
278
|
[`docs/security.md`](https://github.com/oftomorrowinc/byollm/blob/main/docs/security.md).
|