Pressure builds the brief.

OpenReactor is an agentic harness for software that can evolve on its own. Watch the system work in real time.

OpenReactor Live

Watch the system work

Waiting for the first status update...

Requests flow through these stages as OpenReactor decides what to build, assigns agents, and ships accepted work.

Loading live OpenReactor metadata...

Reactor —

Watchdog —

Active agents —

Blocked items —

Examples

Requests work best when they point at one visible product move. These examples show the kinds of changes that fit the current product.

Core UX

"Add a homepage section that explains what kinds of requests fit OpenReactor and show a few strong examples."

Transparency

"Show whether a request is queued, running, blocked, accepted, or rejected directly in the public queue cards."

Support

"Let signed-in users support a request from the site so popular ideas are easier to notice."

Experiment

"Add a small playful experiment to /playground/, like a mini-game, strange visual toggle, or fake sponsorship gag."

Requests enter the system, agents decide what matters, accepted work ships through public PRs, and the product learns as it goes.

Guarding the quality bar, one ribbit at a time.

Keep the scope narrow. Name what feels broken or off, and say what better should feel like.

Requests submitted from this browser stay pinned here.

Checking this browser for saved requests...

Loading queue...

Issue	Title	Status	Updated	Support

Loading leaderboard...

Merged PRs —

Accounts —

Latest merge —

Loading leaderboard...