@particle-academy/prism-browser
@particle-academy/prism-browser
Node/TS port of prism-browser -- Guarded browser automation -- bounded observations and policy-first navigation.
Part of Prism — 22 packages, one productSee the familyBackend · renders no UI
Nothing to preview — install it and call the typed API, or hand it to an agent.
$
npm install @particle-academy/prism-browserWhy
The contract is the same in every runtime; only the host differs. A team on Node or Python should not have to reimplement guarded browser automation: bounded observations and policy-first navigation, so an agent's reach is declared rather than discovered, or route through a PHP service to reach it, because the capability happens to have been written in Laravel first. This is that port -- the same behaviour, held to the same shared fixtures rather than to a README that claims parity.
What
Node / TypeScript port of prism-browser -- guarded browser automation: bounded observations and policy-first navigation, so an agent's reach is declared rather than discovered.
How
npm install @particle-academy/prism-browser. Same shapes in and out as the PHP twin; the reasoning behind the capability is on that page.API surface
Headless package — drive it from code or an agent. No component grid.
This package renders no UI surface. It exposes a typed code API; issues are tracked on GitHub.
No API table yet. A supporting package with no rendered components, so there are no live demos — reach for the README + Changelog for the full reference, and the Issues link to file feedback.