lobstah 0.8.8 → 0.8.10

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 CHANGED
@@ -25,16 +25,21 @@ and recovers each; status and evidence land on disk. Supervision costs
25
25
  nothing — no tokens, no attention — so the whole fleet fits in one
26
26
  conversation, and **your agents just bring home the lobstahs**.
27
27
 
28
- ## Which one? 🧭
29
-
30
- As a **background router**, lobstah takes work you (or a tracker) lob in,
31
- runs supervised workers in their own worktrees, pings you when something
32
- needs you, and brings PRs home with no session open. As the **lobstah man**,
33
- one interactive Claude Code or Codex session takes the helm and runs that
34
- same fleet from a conversation, woken by the plugin's hooks instead of by
35
- you. Both sit on the same daemon, so start with the router and add a helm
28
+ ## Choose your approach 🧭
29
+
30
+ Both run on the same daemon, so you can start with the router and add a helm
36
31
  whenever you like.
37
32
 
33
+ | | Background router | Lobstah man |
34
+ |---|---|---|
35
+ | What it is | lobstah takes work you (or a tracker) lob in, runs supervised workers in their own worktrees, and brings PRs home | One interactive Claude Code or Codex session takes the helm and runs that same fleet from a conversation |
36
+ | Who it's for | You, with no session open: it pings you when something needs you | You, talking to one session that dispatches, answers workers and hands you the catch |
37
+ | How it runs | The daemon, as a service; `[hooks.notify]` reaches you | The daemon, plus the plugin's hooks, which wake the helm instead of you |
38
+ | Setup | `npm i -g lobstah`, `lobstah init --scan ~/src`, `lobstah daemon install` | The same, then the lobstah plugin for your harness |
39
+ | Start with | `lobstah dispatch --repo myapp --brief ./brief.md` | `/lobstah:man` (Claude Code) or `$lobstah:man` (Codex) |
40
+
41
+ See [the router's quickstart](#quickstart-the-background-router-) or [the lobstah man's](#quickstart-the-lobstah-man-).
42
+
38
43
  ![Pixel lobster carrying a star across the page](https://github.com/aequitas-labs/lobstah/blob/main/docs/assets/lob-crawl.svg)
39
44
 
40
45
  ## Requirements 📋
@@ -227,6 +232,26 @@ means the brief is fulfilled. Merging is never the dispatch's job.
227
232
  Everything lives under `$LOBSTAH_HOME` (default `~/.lobstah`). To run more
228
233
  instances, use more homes. One daemon per home, enforced.
229
234
 
235
+ ## Glass 🔭
236
+
237
+ The glass is lobstah's web view of your fleet: what's on deck, cards waiting
238
+ for an answer, PRs and their stacks, reviews, runs and traps.
239
+ `lobstah glass --detach` starts it in the background at
240
+ `http://127.0.0.1:4949` (`lobstah glass` runs it in the foreground).
241
+
242
+ <img src="docs/assets/glass-mobile.png" width="320" alt="The glass on a phone, On deck: three decisions waiting, three dispatches in flight (one needs a decision, two working), and two that landed today">
243
+
244
+ From the glass you can answer decision and permission cards, run a run card,
245
+ mark a PR to merge when its checks are green, and review a PR. Everything you
246
+ do there goes through the same paths as the CLI.
247
+
248
+ The same glass is hosted at [glass.lobstah.dev](https://glass.lobstah.dev),
249
+ through a wharf. Enroll this machine with `lobstah wharf login --wharf <name>
250
+ --mirror`, set `[glass] mirror` to that wharf, and run `lobstah daemon restart`.
251
+ The hosted glass then shows this machine's glass, and what you do there is
252
+ carried out on this machine. The fleet stays on its local grounds.
253
+ [docs/configuration.md](https://github.com/aequitas-labs/lobstah/blob/main/docs/configuration.md) has the details.
254
+
230
255
  ## When something needs you 🛎️
231
256
 
232
257
  Set one config table — `[hooks.notify]` with `command = "ntfy pub my-topic ..."` — and the
@@ -296,44 +321,12 @@ with a nudge.
296
321
 
297
322
  ## Telemetry 📊
298
323
 
299
- lobstah shares anonymous daily usage statistics, **on by default**. Once
300
- per UTC day the daemon sends schema 2, with `catches.today` and `catches.total` for the UTC day and
301
- all-time, plus up to 100 `traps: [{name, today, harness, model, config}]` entries with automatically
302
- generated names and recorded provenance. Custom names (`--name`) and older
303
- names with unknown provenance stay local; their catches remain in the totals.
304
- Names are not hashed. A `helm` snapshot and up to 100 headless `byWorker`
305
- count buckets include harness, catalog-only model id, and nullable reasoning
306
- effort/permission-mode enums. Unknown observations stay null; custom or
307
- unrecognised model ids become `other`. No arbitrary config is sent.
308
- The payload also includes the lobstah
309
- version, OS family, CPU architecture, the UTC date, and a random install id
310
- made on your machine. It never sends repository names or paths, code, briefs,
311
- session ids, PR URLs, hostnames, or usernames. It also sends small count ranges
312
- for boats and local/wharf grounds, fixed choices for hosted/self-hosted use
313
- and boat access, and daily catches with/without a live helm and on local/wharf
314
- grounds. Older unobserved catches stay unknown. Helm presence distinguishes
315
- none, one and several; an unreadable wharf stays unknown. Boat count is at
316
- least one locally, or the largest visible account roster; it is unknown when
317
- the boat cannot read a configured wharf. Telemetry reads cached observations
318
- only, on its own clock and a fresh connection without wharf credentials or
319
- cookies. Signing in never links the install id to an account. No account or
320
- boat identifiers, wharf addresses, grounds names, tokens or times finer than
321
- the UTC date are sent. Self-hosted wharves receive no telemetry. Hooks never send
322
- anything, and nothing is sent until a one-time notice has been shown in your
323
- terminal. The counts feed a project-wide `🦞 N` badge. Per-install rows are
324
- deleted after 90 days, as are per-trap and worker/config rows; retained daily
325
- totals have only counts, including harness/model aggregates and usage-bucket
326
- histograms, no names or config.
327
-
328
- - `lobstah telemetry show` prints the exact JSON that would be sent.
329
- - `lobstah telemetry status` shows whether it is on and why.
330
- - Turn it off with any one of: `lobstah telemetry disable`,
331
- `[telemetry] share = false` in `~/.lobstah/config.toml`,
332
- `LOBSTAH_TELEMETRY=0`, `DO_NOT_TRACK=1`, or `CI` set.
333
-
334
- No release sends anything yet: the endpoint is not set. Everything about it,
335
- including who receives it and how long it is kept, is in
336
- [PRIVACY.md](PRIVACY.md).
324
+ lobstah sends anonymous daily usage counts, on by default: how many catches,
325
+ which harness and model, the lobstah version and OS, and a random install id.
326
+ It never sends code, briefs, repository names, paths or hostnames. Turn it off
327
+ with `lobstah telemetry disable` (or `DO_NOT_TRACK=1`); `lobstah telemetry show`
328
+ prints exactly what would be sent. Everything it collects:
329
+ [docs/telemetry.md](https://github.com/aequitas-labs/lobstah/blob/main/docs/telemetry.md).
337
330
 
338
331
  ## What a wharf holds
339
332