typebulb 0.62.6 → 0.62.8

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
@@ -69,7 +69,7 @@ typebulb trust [file] Remember a bulb as trusted (no arg: list trusted
69
69
  typebulb untrust <file> Forget a bulb's trust (back to Restricted)
70
70
  typebulb status [agent] A sub-agent's status: what it waits on, its commands and files (no arg: the session's overview)
71
71
  typebulb status --slow <dur> When a call counts as slow for this session (default 3m)
72
- typebulb babysit Watch your sub-agents silently; print and exit when one needs you (run it in the background — the exit is your wake-up)
72
+ typebulb babysit Watch your sub-agents silently; print and exit when one needs you (run it in the background: each exit is one wake-up, so re-arm it after handling)
73
73
  typebulb babysit --slow <dur> When a call counts as slow for this session (default 3m)
74
74
  typebulb --no-watch <file> Disable hot reload
75
75
  typebulb --no-open <file> Open nothing at launch, not even inside VS Code
@@ -326,7 +326,7 @@ The host owns light/dark; you style for both.
326
326
  - **A bulb's working files land beside it automatically** — relative `tb.fs` paths resolve to the bulb's folder, in `code.tsx` and `server.ts` alike: `tb.fs.write('run.json')`, no path prefix, no mkdir.
327
327
  - **Images & media: an `assets/` subfolder of the bulb's folder** (`birds.bulb.md` → `birds/assets/robin.png`) — `<img src="assets/robin.png">` just works (always that relative form, never `/assets/…`), every tier except inline. It holds what the bulb ships in order to run (e.g. images), never results.
328
328
  - **See what's already running** — `typebulb logs` with no argument lists every running bulb and mirror; check it before launching anything.
329
- - **Checking on sub-agents you spawned** — `typebulb status` is your session's overview (what's running, failure streaks, files to check before `git add`), and `typebulb status <id>` one agent's; run it before committing. Arm `typebulb babysit` in the background when you fan out (Claude Code: `run_in_background`; Codex: experimental, may need elevated permissions): it exits with a line when an agent needs you, so handle it and arm it again. Brief their checks unpiped or after `set -o pipefail`: a run piped into `tail` exits with `tail`'s code, so neither can see it fail. Both take `--slow` (when a call counts as slow, default `3m`): set it to your project's pace once, e.g. `--slow 10m` where the test suite takes 8, and the session keeps it.
329
+ - **Checking on sub-agents you spawned** — `typebulb status` is your session's overview (what's running, failure streaks, files to check before `git add`), and `typebulb status <id>` one agent's; run it before committing. Arm `typebulb babysit` in the background when you fan out (Claude Code: `run_in_background`; Codex: experimental, may need elevated permissions): it exits with a line when an agent needs you, because a background command wakes you only by exiting. Handle it and arm it again right away; the re-arm loses nothing, as what came up meanwhile fires at once and what it already reported doesn't repeat. Run babysit unpiped, and brief their checks unpiped or after `set -o pipefail`: a command piped into `tail` exits with `tail`'s code, hiding its own. Both take `--slow` (when a call counts as slow, default `3m`): set it to your project's pace once, e.g. `--slow 10m` where the test suite takes 8, and the session keeps it.
330
330
  - **Self-testing a local bulb** — To confirm a bulb works, run it, instrument with `tb.log(...)`, and read it back with `typebulb logs`. That's the loop to verify behaviour without asking the user to copy-paste console output. `tb.fs.write(...)` is handy for dumping large outputs.
331
331
  - **Self-testing client code** — gate checks behind `tb.onMessage(m => { if (m === 'selftest') return run() })`, trigger with `typebulb send <file> selftest --wait`, and assert on the JSON reply — see [Interrogating the live page](#interrogating-the-live-page).
332
332
  - **Probe handlers go in the first draft** — the selftest, readback, and set handlers you'll want later: adding one is an edit, and that hot reload destroys the very state you meant to inspect.
package/SKILL.md CHANGED
@@ -1,10 +1,10 @@
1
1
  ---
2
2
  name: typebulb
3
3
  description: "Author and run Typebulb bulbs — single-file markdown apps (TypeScript/TSX) that run locally via `npx typebulb` (full power: filesystem, database, `server.ts`, `tb.ai`) or render live inline in your coding agent's session through Typebulb's agent mirror (sandboxed, client-only). A bulb can be a visual widget (chart, simulation, diagram, calculator, UI), a full-stack tool with a Node backend, or an AI app that calls models at runtime. Covers the bulb format, the `tb.*` API, trust, and the local run/inline workflow. Use when the user wants a bulb, a quick local tool (visual, backend-backed, or AI-powered), or something visual rendered inline in the conversation."
4
- version: 0.62.6
4
+ version: 0.62.8
5
5
  ---
6
6
 
7
- > Generated from typebulb v0.62.6. `npx typebulb agent` prints the running version alongside the path to its packaged SKILL.md: if that version is newer than this one, replace this file with that one.
7
+ > Generated from typebulb v0.62.8. `npx typebulb agent` prints the running version alongside the path to its packaged SKILL.md: if that version is newer than this one, replace this file with that one.
8
8
 
9
9
  # typebulb
10
10
 
@@ -77,7 +77,7 @@ typebulb trust [file] Remember a bulb as trusted (no arg: list trusted
77
77
  typebulb untrust <file> Forget a bulb's trust (back to Restricted)
78
78
  typebulb status [agent] A sub-agent's status: what it waits on, its commands and files (no arg: the session's overview)
79
79
  typebulb status --slow <dur> When a call counts as slow for this session (default 3m)
80
- typebulb babysit Watch your sub-agents silently; print and exit when one needs you (run it in the background — the exit is your wake-up)
80
+ typebulb babysit Watch your sub-agents silently; print and exit when one needs you (run it in the background: each exit is one wake-up, so re-arm it after handling)
81
81
  typebulb babysit --slow <dur> When a call counts as slow for this session (default 3m)
82
82
  typebulb --no-watch <file> Disable hot reload
83
83
  typebulb --no-open <file> Open nothing at launch, not even inside VS Code
@@ -334,7 +334,7 @@ The host owns light/dark; you style for both.
334
334
  - **A bulb's working files land beside it automatically** — relative `tb.fs` paths resolve to the bulb's folder, in `code.tsx` and `server.ts` alike: `tb.fs.write('run.json')`, no path prefix, no mkdir.
335
335
  - **Images & media: an `assets/` subfolder of the bulb's folder** (`birds.bulb.md` → `birds/assets/robin.png`) — `<img src="assets/robin.png">` just works (always that relative form, never `/assets/…`), every tier except inline. It holds what the bulb ships in order to run (e.g. images), never results.
336
336
  - **See what's already running** — `typebulb logs` with no argument lists every running bulb and mirror; check it before launching anything.
337
- - **Checking on sub-agents you spawned** — `typebulb status` is your session's overview (what's running, failure streaks, files to check before `git add`), and `typebulb status <id>` one agent's; run it before committing. Arm `typebulb babysit` in the background when you fan out (Claude Code: `run_in_background`; Codex: experimental, may need elevated permissions): it exits with a line when an agent needs you, so handle it and arm it again. Brief their checks unpiped or after `set -o pipefail`: a run piped into `tail` exits with `tail`'s code, so neither can see it fail. Both take `--slow` (when a call counts as slow, default `3m`): set it to your project's pace once, e.g. `--slow 10m` where the test suite takes 8, and the session keeps it.
337
+ - **Checking on sub-agents you spawned** — `typebulb status` is your session's overview (what's running, failure streaks, files to check before `git add`), and `typebulb status <id>` one agent's; run it before committing. Arm `typebulb babysit` in the background when you fan out (Claude Code: `run_in_background`; Codex: experimental, may need elevated permissions): it exits with a line when an agent needs you, because a background command wakes you only by exiting. Handle it and arm it again right away; the re-arm loses nothing, as what came up meanwhile fires at once and what it already reported doesn't repeat. Run babysit unpiped, and brief their checks unpiped or after `set -o pipefail`: a command piped into `tail` exits with `tail`'s code, hiding its own. Both take `--slow` (when a call counts as slow, default `3m`): set it to your project's pace once, e.g. `--slow 10m` where the test suite takes 8, and the session keeps it.
338
338
  - **Self-testing a local bulb** — To confirm a bulb works, run it, instrument with `tb.log(...)`, and read it back with `typebulb logs`. That's the loop to verify behaviour without asking the user to copy-paste console output. `tb.fs.write(...)` is handy for dumping large outputs.
339
339
  - **Self-testing client code** — gate checks behind `tb.onMessage(m => { if (m === 'selftest') return run() })`, trigger with `typebulb send <file> selftest --wait`, and assert on the JSON reply — see [Interrogating the live page](#interrogating-the-live-page).
340
340
  - **Probe handlers go in the first draft** — the selftest, readback, and set handlers you'll want later: adding one is an edit, and that hot reload destroys the very state you meant to inspect.