Raycast extensions in any app. Blast is an embeddable engine: it runs the launcher flow for you (command search, preference and argument prompts, dependency installs, each command's UI) and hands your app views to draw and capability requests to answer. You draw the pixels; Blast brings the extension.
Try it in a browser — no install: blast.yukai.dev/demo.
Embed in JS/TS with the in-process engine
(npm install @blastlauncher/engine@next):
import { createEngine } from "@blastlauncher/engine";
const engine = createEngine({ handlers: { "clipboard.copy": (params) => copy(params) } });
engine.openExtension({ extensionDir: "./my-extension" });
const root = engine.root({ views: { platform: "macOS" } });
root.subscribe((view) => draw(view)); // the command list, prompts, then the command
root.input({ type: "search", text: "ap" });Embed in any language by spawning blast serve
(npx -p @blastlauncher/serve@next blast-serve) and speaking versioned NDJSON; the Go and
Python examples are standard-library clients:
hello (with views) → welcome
extension.open, root.open → root.view: draw it; root.input → forward input
root.launched → session.view: draw it; session.input until session.exited
capability.request → answer capability.result
Embed in a web page with @blastlauncher/web@next: one mount() call runs
an extension in a sandbox on a second origin you host.
Use it in tmux with the tmux-blast
plugin: Ctrl+Space opens a Raycast-style palette in a tmux
popup with pane, window and session commands, plus any Raycast extension
directory you add. With TPM, add this to
~/.tmux.conf and press prefix I:
set -g @plugin 'BlastLauncher/tmux-blast'It needs tmux 3.2+ and Bun; the plugin runs @blastlauncher/tui@next
(3.0.0-alpha.3 or later) from npm. See the
tmux palette docs for commands and options.
The quickstart runs each path. The embedding guide has the complete API and transcript.
- Lists every opened extension's commands as a Raycast-style root view.
- Asks for missing preferences and arguments, and installs declared dependencies.
- Runs each command in its own Node.js process, brokering every privileged call.
- Implements Raycast client semantics, including storage and OAuth.
- Draw views (list, grid, form, detail, actions, toasts) in your UI.
- Forward semantic input: search text, movement, primary action, back.
- Answer only the OS capabilities you choose to grant.
Compatibility is measured against the latest @raycast/api, not claimed:
API coverage is 1539/1540 current symbols (@raycast/api 2.11.1) and the
sandboxed sweep renders 91.4% of 5,759 corpus commands.
The curated smoke renders 237/253 commands; dependency
smoke renders 51/52 (details).
Alpha:
3.0.0-alpha.9is published on npm undernext(npm install @blastlauncher/<package>@next);lateststill points at Blast v1. Reference clients: the browser demo, the TUI, the Go and Python embedders, the AppKit and web launchers.
| Package | Role |
|---|---|
host (@blastlauncher/engine) |
Engine, bundling, sessions, dependencies, capabilities |
runtime |
React reconciler and @raycast/api implementation |
protocol |
Message types, capability catalog and schema |
client-core |
Framework-free views, ranking, selection and input |
serve |
blast serve over stdio |
web |
Browser runtime for any web page, via mount() |
native |
Optional macOS, Windows and Linux handlers |
cli |
blast run, a headless debug client |
tui |
OpenTUI terminal client and tmux palette (Bun) |
Requires Bun and Node.js 24.
bun install --frozen-lockfile
bun run verify
bun run release:build # the npm packages as tarballs, for local testingSee architecture, capabilities, CLI, release, PLAN.md and AGENTS.md.
Blast v1 was an Electron launcher published as the @blastlauncher/cli,
runtime, api, renderer and utils packages (1.x); its last app release
was v0.0.14.
V3 is a from-scratch rewrite and an ongoing personal experiment.
MIT