Reactor

Settings

Everything below is stored in this browser only. Reactor has no accounts and no backend of its own — the console is a static page and the engine is your own process.

Appearance

Applies immediately, and is remembered on this device.

Theme

System follows your OS; Reactor opens dark by default.

Engine

Reactor's control plane runs on your machine, not ours — it spawns sandboxes and holds multi-minute event streams.

Blank restores the default

Start it with:

make build && ./bin/reactor serve
API keys

Sent to your engine on detonate and upload — never to the host that serves this page.

One disposable sandbox per detonationGet a key
Leave blank for the default cloud API
Victim agent + analyst modelGet a key

With no Fireworks key the engine falls back to its sim victim and deterministic analyst; with no Daytona key it uses whatever chamber driver it can reach locally.

Detonation defaults

What the console asks the engine for when you hit Detonate.

Sessions per detonation

Each one gets a fresh chamber. The demo run is five.

Allow network egress

Off means the chamber is cut off and exfil attempts die at the sink.

Open the sample rack

Expand the artifact zoo on load instead of starting folded.

Local data

Reactor stores five keys in this browser and nothing anywhere else.

  • reactor-credentialsDaytona + Fireworks keys
  • reactor-engine-urlengine origin override
  • reactor-prefsdetonation defaults
  • reactor-themetheme choice
  • reactor-onboarding-donefirst-run flag
About

Where the rest of Reactor lives.

Source, engine and docs on GitHubOffline scorecard — 25 real servers, static-blind column