particle-academy/prism-browser
particle-academy/prism-browser
Guarded browser automation for Prism agents -- bounded observations, policy-first navigation, and durable sessions. First-party, so driving a browser from an agent does not start with a third-party approval conversation.
Part of Prism — 9 packages, one productSee the familyBackend · renders no UI
Nothing to preview — install it and call the typed API, or hand it to an agent.
$
composer require particle-academy/prism-browserWhy
Driving a browser is one of the most useful things an agent can do and one of the easiest to do badly: an unbounded observation floods the context window, and navigation with no policy is an agent going wherever a page tells it to. Reaching for a third-party driver also starts a dependency conversation for something the estate already ships.
What
Guarded browser automation for Prism agents: bounded observations, policy-first navigation, and durable sessions. Bounded and policy-first are both about the same thing — what the agent is allowed to see and where it is allowed to go are declared rather than emergent.
How
composer require particle-academy/prism-browser. For asserting a Fancy surface from an agent rather than driving a page, the MCP bridges in @particle-academy/agent-integrations are the closer fit — the component is the affordance, not a DOM target.API surface
Headless package — drive it from code or an agent. No component grid.
This package renders no UI surface. It exposes a typed PHP 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.