Use the engine and client core directly when your application owns the JavaScript runtime and rendering loop.
import { createEngine } from "@blastlauncher/engine"Blast runs extensions compatible with Raycast in your own product. Keep your UI, your host, and your boundaries.
$ blast serve→ extension ready→ scene published→ your UI decidesChoose the boundary that fits your host. Both expose the same engine and client semantics.
Use the engine and client core directly when your application owns the JavaScript runtime and rendering loop.
import { createEngine } from "@blastlauncher/engine"Run the headless engine over stdio and let any language draw scenes, route events, and broker capabilities.
npx -p @blastlauncher/serve@next blast-serveNo launcher assumptions. Blast is a portable host you can place behind your own product surface.
The compatibility surface is measured against the current API declarations and a broad extension sweep. It is work in progress, published plainly.
npm install @blastlauncher/engine@next
npm install @blastlauncher/client-core@next