typebulb 0.15.1 → 0.15.3

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
@@ -43,7 +43,7 @@ typebulb send <file> [msg] Push a message into a running bulb's page (its tb
43
43
  typebulb check [file.bulb.md] Type-check a bulb without running it
44
44
  typebulb predict [file] Report the capability a bulb probably needs, without running it
45
45
  typebulb models List AI models for tb.ai, filtered by your .env API keys
46
- typebulb logs [file|pid] Print a running bulb's captured console (no arg: list running servers; -f follow, -n N tail, --clear for a clean run)
46
+ typebulb logs [file|pid] Print a running bulb's captured console (no arg: list running servers; -f follow, -n N tail, --run latest|N for one reload's output, --clear to empty it)
47
47
  typebulb wait [file|agent] Block until the target server logs a new line, print it, exit — an agent's wake-up
48
48
  (--match <substr> filters; --timeout <sec>, default 1800, exit 2)
49
49
  typebulb stop [file|pid] Stop a running bulb (no arg: list this project's running servers)
@@ -247,7 +247,7 @@ Run a bulb **once** and let hot reload drive the loop.
247
247
  - **Don't relaunch, and don't wrap it in `timeout`.** A relaunch only replaces the running server (one per bulb file); `timeout` kills it, and the racing relaunch is what spawns a second window on a fresh port.
248
248
  - **What needs a restart:** a `.env` change (read once at boot) and in-memory `server.ts` state (reset on each reload).
249
249
  - **Each reload re-runs the bulb.** A save re-executes `code.tsx` from scratch, so work you start on mount repeats every edit — re-spending GPU/network, re-firing side effects, flooding the log. Put expensive or side-effecting work behind a trigger: `tb.onMessage(() => start())`, then `typebulb send <file>` when ready (also a general terminal→page channel — pass params, drive a loop).
250
- - **Reading the log:** `typebulb logs --clear <file>` empties it first, so you see only the next run.
250
+ - **Reading the log:** it appends across every reload, so `typebulb logs --run latest <file>` shows just the current run (no need to clear).
251
251
  - **When done:** Ctrl-C, or `typebulb stop <file>` — closing the terminal leaves the server running detached.
252
252
 
253
253
  ## Tips for Agents