PH

@particle-academy/prism-harness

@particle-academy/prism-harness

Node/TS port of prism-harness -- Durable agent sessions -- threads, modes, tool permissions and subagents.

Backend · renders no UITS
Part of Prism — 22 packages, one productSee the family
Backend · renders no UI
Nothing to preview — install it and call the typed API, or hand it to an agent.
$npm install @particle-academy/prism-harness
Why
The contract is the same in every runtime; only the host differs. A team on Node or Python should not have to reimplement durable agent sessions -- threads, modes, tool permissions and subagents, 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-harness -- durable agent sessions -- threads, modes, tool permissions and subagents.
How
npm install @particle-academy/prism-harness. 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.
What next
Install it, then call the API from your code or over MCP.