Skip to content

Examples

Every example is a small Effect application in the repository, typechecked against the packages on every change. Most run offline on ReactorTest with no API key. All but the rundown are written to run on hosted H3 with REACTOR_API_KEY set, where only the layer changes; no example has run there yet, though paid checks ran most of the SDK they use (hosted evidence). Clone the repository and install once:

Terminal window
git clone https://github.com/mannyc2/reactor-effect-client && cd reactor-effect-client
bun install && bun run build

Quickstart offline or live

Section titled “Quickstart ”

One H3 clip from prompt to its end, with its frames decoded in your process, in one file. The quickstart page walks through it.

Terminal window
node examples/quickstart/src/main.ts

Terminal viewer offline or live

Section titled “Terminal viewer ”

H3 drawn in your terminal. Each frame is decoded in the process and drawn as 24-bit colour text about twelve times a second, while every clip of a playlist is followed from acceptance to its end. No browser is involved anywhere: this is what reactor-effect-native adds to Node and Bun.

Terminal window
cd examples/terminal
node src/main.ts "A lighthouse on a sea cliff at dusk" "A neon-lit alley in the rain"

Live channel offline or live

Section titled “Live channel ”

Your own 24/7 AI channel. Viewers send prompts from a page, a house rotation fills the gaps, and Playout renews sessions before their cap so a renewal never takes the channel off air. The server decodes one paid session and broadcasts it to many viewers, and can restream it to Twitch, YouTube or X over RTMP (so far run against a local RTMP listener only; the channel’s live mode has not run on hosted Reactor yet). The channel guide explains each piece.

Terminal window
cd examples/livestream
node src/main.ts # then open http://127.0.0.1:3000

H3 Studio in the browser

Section titled “H3 Studio ”

A page that runs its own session: H3’s queue live with its play, move, pop and stop controls, reference images validated once and reused, each clip’s lifecycle, and failures shown with their dispatch outcome. Rehearse a failed build, a lost reply or a moderation verdict with one click.

Open the playground: Studio on ReactorTest, running in your tab, with no key and nothing billed. With an API key on its server, the same page is built to run on hosted H3 over BrowserPeer, which has not yet run on a paid session.

Terminal window
cd packages/browser/examples
bun run start # offline without REACTOR_API_KEY; open http://127.0.0.1:3000

A command line that generates one clip and writes its decoded frames and audio to an MP4 through ffmpeg, filling any dropped frame explicitly. It prints the most the run can cost before it allocates anything.

Terminal window
cd packages/native/examples
REACTOR_API_KEY=rk_... node src/capture.ts --prompt "A red kite over a green hill" --out kite.mp4

An application service written against Playout: it plays an ordered list of prompts and reports what became of each. Its tests run it on ReactorTest under TestClock, with faults standing in for a failed build and a lost reply, in a fraction of a second of real time. Test offline with ReactorTest builds on it.

Terminal window
cd packages/client/examples
bun run start && bun run test