Agentic integrity · Open source · Apache 2.0

An AI coding agent with a quorum behind every call.

QuorX is an AI coding agent whose work is checked. It builds on your own computer with a real shell and a real browser, while decider models answer its questions, a separate reviewer scores every build, and a safety layer guards every command. Any model, from OpenRouter, the makers' own APIs, your subscriptions or your PC, priced before you pick.

v0.2.16 · Installer or build from source · Windows · Free and open source

The QuorX app building a neon snake game: the chat with the agent's steps on the left, the game running in the built-in browser on the right.

Agentic integrity

An agent whose work is checked.

What the agent does is tested by something other than the agent. And you can see how each model holds up before you trust it with a project.

  1. 1

    Deciders answer its questions

    When it's unsure, the agent writes down its own guess, then fast decider models vote. You see whether asking changed the answer.

    The quorum ↓
  2. 2

    A reviewer scores every build

    A separate model opens what was built, plays it and scores it before the reply. Problems go back to the agent.

    The checks ↓
  3. 3

    A safety layer guards commands

    Every command is parsed and classed before it runs. Risky ones wait for you, code QuorX can't read goes to the deciders, and system changes are refused.

    Safety ↓
  4. 4

    Benchmarks measure it

    A built-in build benchmark with hidden checks scores models on real tasks, and your own pass rate sits next to each model's price.

    Models and prices ↓

Across every model you can pick. Per-model results, the price before you pick, and model cards with each model's limits, quirks and QuorX results, so you can see which models build well and improve how you use them.

Watch the walkthrough · 1:36

See it build, test and review a game in 96 seconds.

The video loads from YouTube's no-cookie player only after you press play.

Chapters

Watch on YouTube ↗

Describe it. It builds, tests and shows you.

  1. 1

    Describe it

    A game, a site, a desktop app, a fix. A prompt enhancer spells out what the request implies and shows it under your message, so you can correct it.

  2. 2

    It builds in your folder

    A real terminal, a real browser and the toolchains already on your computer.

  3. 3

    It tests before it replies

    Every file is checked as it is written. Then it opens what it built, plays it like a person would, and a separate reviewer model scores it.

  4. 4

    You review and undo

    Every change, commands included, with one-click Undo.

The quorum

Small, fast models check its guesses.

When the agent is unsure, it writes down its own guess first, then asks a quorum of fast decider models yes/no or multiple-choice questions. You see whether asking changed anything.

Decider question CHANGED ANSWER

When the snake reaches the edge of the board, what should happen in this game?

Agent guessed Wrap around55% sure
Deciders said Walls are deadly 82% confident 3/3 agree Settled
Spread
Walls are deadly0.88
Wrap around0.06
None of these0.06
Two decider questions in the QuorX trace. Each shows what the agent guessed, what the deciders said and the spread of their votes. One is tagged Changed answer, the other Already knew.
The real trace from a build. Each question is tagged Changed answer or Already knew, so you can tell when asking was worth it.

Guess first, then vote

The agent writes down its own answer and how sure it is before the deciders vote, so you can see whether asking changed it.

In ⚡ YOLO the deciders answer for you

When the agent would normally stop to ask you something, the deciders answer its question instead.

A question from the agent answered by the deciders while QuorX is in YOLO mode.

Fixed checks, every build

A standing set of questions goes to the deciders about every build too, not only when the agent is unsure.

Safe by default

It asks before it does anything risky.

Guarded commands

Every command line is parsed and each part is classed. Your rules decide what runs; the rest comes to your approval card. Starting a server gets the same check.

readbuildinstallpushdeletecan't be checked
An approval card for the command Remove-Item -Recurse -Force ../old-builds, tagged deletes and outside the project.

🔒 Strictor⚡ YOLO

Strict is the default and asks you about anything that isn't read-only. YOLO runs most commands on its own, after a snapshot; pushes, deploys and writes outside the project pause for you, and commands QuorX can't read go to the deciders.

A QuorX chat running in YOLO mode, with the deciders approving a step.

Undo covers commands

The project is snapshotted before each command, so Undo covers what a build script or an rm did, not just the agent's edits, even when commands ran at the same time.

Review changes in QuorX: every file a reply touched, with an Undo button.

Tripwire and spending caps

A command that deletes many files outside the project is stopped. A cap per reply, an optional daily cap, project budgets and a media cap. Stopped and failed calls count too, so caps match what OpenRouter bills.

Per reply
$1.00
Paid media per reply
$0.50
Daily
optional
Project budget
stops and asks

Example values from one chat's settings. You set your own.

Stop ends everything

Each command runs in a Windows job, so Stop ends every process it started and confirms 0 processes left. Pressed before a command starts, Stop means it never runs.

Servers and terminals running in a QuorX project, each with a Stop button.

Refused outright

Deny

System changes (services, the registry, disks, admin rights), deleting your profile, a drive root or anything above the project. No rule or mode can approve these.

  • rm -rf ~your profile
  • Remove-Item -Recurse C:\a drive root
  • rm -rf ../..above the project
  • Stop-Service WinDefenda system change

It checks before it says done.

  • Checks the changed files again and runs compiler checks on them.
  • Opens what it built and runs browser checks against it.
  • Catches weakened tests, so a pass means a pass.
  • A separate reviewer model plays the result and scores it. Problems go back to the agent.
Browser checks run by QuorX against a build, with 5 passed.
Reviewer card: Function 5 of 5, Design 5 of 5, Craft 4 of 5, Originality 4 of 5, Accessibility 4 of 5. Passed, cost $0.0057.

Any model, wherever you pay. Price first.

Hundreds of models through one OpenRouter key, the makers' own APIs with your key, the plans you already have, or Ollama and the AI apps on your PC. The picker starts with where a model runs, then searches, sorts by price, filters by what a model can do, and shows your own pass rate next to each price.

Every step and every cent is on the record.

A reply cost breakdown in QuorX: $0.01095 for 16 model calls.

$0.01095for one reply, 16 model calls, itemised.

The QuorX model picker, listing OpenRouter models with prices, capabilities and your pass rate.

Twelve providers, four ways to pay.

What each one brings →

One key, every makerpay per call

  • OpenRouterHundreds of models, prices side by side. Runs the deciders and paid media.

The makers' own APIsyour key, their prices

  • OpenAIGPT models, cached tokens billed as OpenAI does.
  • AnthropicClaude with thinking and prompt caching, natively.
  • Google GeminiGemini on your key; free-tier keys work too.
  • Moonshot KimiKimi, with its reasoning kept between steps.
  • MetaMeta's models on its developer API.

Subscriptionsa key with plan limits

  • OpenCode GoIts models at no cost per call, up to the plan's limits.
  • Command CodeGPT, DeepSeek, Kimi, GLM, Qwen and Claude on your credits.

Apps on this PCyour sign-ins there, no key here

  • OllamaThe models you pulled, for nothing, and its cloud models.
  • OpenCodeEvery provider you connected there.
  • Claude CodeThe plan or key it's signed in with.
  • Grok BuildGrok's models, for writing and building.

Same tools, approvals, Undo and Stop on every one. Mix them: one model for the chat, another for the reviewer, a third for the helpers.

More in the box.

16 platform packs

Each one finds its toolchain, compiles what a reply changed, runs and drives the app, and debugs with breakpoints.

  • Rust
  • Node & TypeScript
  • Python
  • .NET
  • Go
  • C & C++
  • Java & Kotlin
  • Android
  • Flutter
  • Electron
  • Tauri
  • Godot
  • Unity
  • Windows installers
  • Apple apps
  • + one for every project

The Terminal tab

Your terminals, what's running and your servers in one place, with panes you can stack and resize, and Stop for everything.

Servers and terminals running in a QuorX project, each with a Stop button.

Several chats at once

Each chat works in its own project with its own budget. When a budget runs out, the reply stops and asks.

Point and comment

Point at part of a page to say what should change. Export as PDF, PNG or a ZIP.

Real apps, driven like a person

A real browser tab, or your own Chrome, Brave or Edge through the QuorX extension; the desktop apps you allow, at View, Click or Full; Android emulators and interactive terminal programs.

News inside the app

What's new in each version, plus reports and research articles. New pieces arrive between versions.

The QuorX News view with release notes and research articles.

MCP both ways, and your skills

The agent uses any MCP server's tools, and any MCP client can hand work to QuorX. Write or import your own skills, for every project or just one.

What's new, release by release

Four releases, 109 changes.

0.2.16 is out now as the installer and from source; the Microsoft Store copy updates itself with a later Store release. Pick a release to see what it added, with a guide for each big feature. All articles →

0.2.16A chat that reads in time order, one budget per chat, and a smarter agent loop

All 32 changes →
QuorX 0.2.16: your message in a teal row, the agent's reply with a violet edge, its work folded into How it got here, then the answer with a poster frame and a video.
A chat that reads in order. No bubbles: full-width rows with a glowing edge, a time on every message, and the answer first.
An approval card for an ffmpeg command with the main button Allow every ffmpeg command, then Just this once, Allow always and Deny.
One yes per program. Allow ffmpeg once and every ffmpeg command in the chat runs.
The side pane's Artifact tab showing Review changes for a reply: two new files, each with Undo file.
Files beside the chat. Review changes, the plan and long answers open in the side pane.
Settings, Agent loop: the six stages of a reply, Plan, Work, Check, Review, Helpers and Long chats.
A smarter agent loop. Edit guard, job notices, hooks, helper roles and typed memory.

🕘 A chat that reads in order

Top to bottom, in the order things happened, with a time on every message. No bubbles: full-width rows with a glowing edge, yours teal, the agent's violet, turning green, amber or red with its state. A finished reply folds its work into How it got here.

Guide →

🧠 A smarter agent loop

It reads a file again if you changed it, hears when background jobs end, reads other tools' notes, loads rare tools only when needed, and runs your hooks around any tool. Helper roles and typed memory, all in Settings.

Guide →

✅ One yes per program

Allow one ffmpeg command and every ffmpeg command in that chat runs without a card. Always allow is on every command card.

Guide →

💰 One budget per chat

The reply, media and daily caps and project budgets become one budget per chat. /goal is the one way to ask for a plan.

🗂 Files beside the chat

Files, Review changes, the live plan and long answers open in the side pane's Artifact tab; Compare splits it.

🎬 Motion design skills

Two built-in skills for films with exact easing and timing, including HyperFrames. Videos in your projects can be scrubbed.

0.2.15MCP servers, your own API keys, and a calmer, faster app

All 35 changes →
QuorX 0.2.15: a chat that previewed a coffee landing page, with the side pane split into the Terminal above and the Browser below.
The side pane, split. The Terminal over the Browser: the test run, the page's server and the page itself, side by side with the chat.
Settings, MCP servers: four servers with their state and tool counts, and the tracker server's details with its command and an Auto or Ask every time choice.
MCP servers. Programs on this PC and servers on the web, with their state, tools and a Sign in button.
An approval card in a chat: use create_issue on the MCP server tracker, marked Changes things, with Allow once, Allow always for this chat, and Deny.
MCP tools ask first. A tool that changes things waits for you in Strict; read-only ones run.
Settings, Providers: defaults for new chats, then every provider by kind with its status, models and spend this month.
One Providers page. OpenRouter, subscriptions, the makers' own APIs and apps on this PC.
The Permissions window: a command rule allowed in a project from a card, and four MCP servers set everywhere, with filters by kind, effect, state and source.
One Permissions window. Every rule and tool you allowed, where it applies and how often it ran.
A command approval card for npm test, with Allow always open: this exact command, commands starting with npm test, or any npm command, in this chat, this project or everywhere.
"Allow always", spelled out. What it covers and where, before you save it.
A settings card in a chat: Project settings, Budget, from $10.00 to $20.00, with Change it and Keep it as it is.
Settings from a chat. The agent finds the setting; only your click changes it.

🧲 MCP servers

The agent uses any MCP server's tools, a program on your PC or a server on the web. Add one in Settings, paste its setup into a chat, or bring in the ones your other tools already have. Notion, Linear and Sentry sign in from your own browser.

Guide →

🔌 Twelve providers, four ways to pay

OpenRouter; the makers' own APIs with your key (OpenAI, Anthropic, Google Gemini, Moonshot Kimi, Meta); OpenCode Go and Command Code plans; and Ollama, OpenCode, Claude Code and Grok Build on your PC. Each with its own page, spend and a free test.

Guide →

🛡 One Permissions window

Every rule, app, folder, site and tool you allowed, by chat, project or everywhere, with how often each ran. Switch any off, or remove it.

Guide →

Clearer approval cards

They say what will run and why it asks, and "Allow always" asks what it covers and where. Type instead of clicking to answer in words.

Guide →

⚙ Settings from a chat

Ask the agent to read or change QuorX's and the project's settings. Every change waits for your click, and keys stay out of reach.

Guide →

Sub value

What your subscription calls would have cost at list price, per call, reply, chat and in total, so you can see what your plan is worth.

Guide →

▶ Running in the sidebar

Every server, command, terminal, browser tab, Chrome and desktop session QuorX has going, in every project, each with Stop.

Tour →

⊟ A split side pane

Two or three tabs at once, stacked and resizable: the Browser over the Terminal, Steps over Files. Remembered per chat.

Tour →

Files inline, a compact message box

Pictures, videos, PDFs and Markdown show in the chat. The message box gives your text the full width, with one row of controls.

Tour →

🖥 Computer use on one screen

QuorX shrinks beside the app it's using, with a Stop banner on top. Computer use and Chrome start only after your click.

Guide →

🔊 Browser tab sound and links

Volume and mute for every tab, the agent's alone, or one tab. A click on a link opens it in the Browser tab; Ctrl+click in your own browser.

0.2.14Your own AI apps as the chat model

All 19 changes →

Apps on this PC as the model

Run a chat's main model through OpenCode, Claude Code or Grok Build on your PC. Your own plan pays, QuorX holds no key, and its files, browser, terminal, checks and approvals work the same.

Guide →

No OpenRouter key needed

Chats, the helper, the reviewer, the prompt enhancer and fresh eyes can all run on an app on this PC. What needs OpenRouter is switched off, and says so.

Guide →

Pick where a model runs

The model picker starts with the source, each with its logo, then that source's own filters, so a long list stays short.

Replies that finish the job

A reply that says what it will do but makes no call is sent back to make it. One that loops or runs far too long is stopped, keeping its calls.

Guide →

Calls only the model can make

Calls written as text run only with this step's key, on a line of their own, outside code, quotes and plans, so a page or a file can't make one.

Guide →

🖥 Computer use draws freehand

One held stroke through many points, smooth held moves, and up to 40 steps in one go.

Guide →

🧭 Follow the steps

Next to 👁, 🧭 follows the running reply's steps in the side pane, for that chat only.

A ⋯ menu on every chat

Rename, Duplicate and Delete from one menu on each chat row, also on right-click.

0.2.13Schedules that run themselves, and your desktop apps

All 23 changes →
The Schedules window: four schedules for a landing-page project with their timing, model, notify rule, next run countdown, and Run now, Pause and Edit.
Schedules. Each with its next run, its notify rule, and Run now, Pause and Edit.

⏰ Schedules that run themselves

A chat that runs every weekday at 9, every hour, or once tomorrow. Press ⏰ Repeat this under a good reply, pick when it tells you, and three failed runs in a row pause it.

Guide →

🖥 Computer use, app by app

Allow each app at View, Click or Full, and the agent works in apps already open or opens installed ones by name. A glowing edge and a Stop button show while it works.

Guide →

Live schedules

A countdown to each next run, a run going on now glows in the list and pulses in the sidebar, and each schedule has one chat.

Guide →

Block a provider

Stop OpenRouter sending calls to a provider that breaks tool calls, for every model or only some (deepseek/*).

Guide →

Each chat's own notes

Every chat keeps its own agent notes, and a chat can stay off its project's notes until you bring it in.

Guide →

Folders outside the project

One card adds a folder to the chat, and the file tools work there. Paths in replies open in File Explorer.

Guide →

Rules you can switch off

Always allowed rules turn on and off and count their uses, in the chat, project settings and Settings.

Approvals that do what they say

Rules match exactly what they name, and dialogs such as "Replace it?" ask you first.

0.2.12Steadier, safer and faster

All 32 changes →
Black Hole Lab, a page with a lensed black hole and physics controls, built by QuorX 0.2.12. Opens the live demo.
Built from one request, in 26 minutes. Black Hole Lab: WebGL lensing and real orbital physics, with 19 passing tests and the reviewer's pass. Try the live demo →
Video Mode in QuorX: the brief card with prices, the story pick, the storyboard approval and frames of the finished film.
Video Mode. The brief, the story pick and the storyboard, then the film.
Settings, Storage in QuorX: what QuorX takes on this computer, with Clear safe caches.
Storage in Settings. What QuorX takes on this computer, and a safe way to clear it.
QuorX at quorx.localhost, a red approval card for reading AWS credentials, and the key-export confirmation naming its folder.
Safer by default. Its own address, a red card before any key is read, and one more ask before keys are exported.
A 4.9 GB backup saved in the background, a search over 12,486 files that says where it stopped, and a long reply streaming.
Fast with big work. A 4.9 GB backup in the background, and a search that says where it stopped.
The same pairing code in QuorX and in the QuorX extension, and the agent carrying on in the same Chrome tab.
Your own Chrome. A matching pairing code, and the next reply carries on in the same tab.

🎬 Video Mode

A film starts with a brief, a story pick and a storyboard, then music first and moving pictures, before anything is spent.

Settings, redesigned

Each category laid out for what it controls. Storage shows what QuorX takes and clears it, Skills you write work in every project or just one, and News arrives between versions.

Its own address

QuorX opens at quorx.localhost, so your sign-in stays away from the apps you build and run on localhost.

Fast with big work

Big projects, long replies and large backups no longer slow QuorX down. A streaming reply keeps its text in place, so you can select it as it arrives.

Stronger checks

Starting a server is checked like any command, reading your keys asks first, and the agent's keys and clicks go only to apps it started.

Your Chrome tabs

The agent's tabs stay open and the next reply carries on in them. ⚡ YOLO can act in your own tabs without asking, if you turn it on. Pairing shows a code to match.

Good to know when you update from 0.2.11 or earlier

  • The first start replaces the app's key, so restart any MCP server that's running.
  • Spend reads higher: stopped and failed calls now count, so it matches what OpenRouter bills.
  • Search skips what .gitignore ignores and build folders.
  • A chat runs one reply at a time.
  • Backups over 4 GB use ZIP64, which older versions can't import.

0.2.7 – 0.2.11Your own browser, the Store, and checked harder

Every version →
  • 0.2.11 The agent works in your own Chrome, Brave or Edge; one Terminal tab; ✨ Enhance; drag anything into a chat.
  • 0.2.10 In the Microsoft Store; the agent's browser tells it whether a page started any sound; the Windows app is about 55 MB smaller.

0.2.7: checked harder, easier to trust

A smaller, cache-friendly prompt

The parts that never change come first, so more of each step is read from the provider's cache. On our benchmark run it passed 2 of 2 tasks vs 1 of 2, at $0.094 vs $0.127 a run. That was one run of each version, so most of the gap is run-to-run variation.

How it was measured ↗

A harder benchmark

Tougher build tasks with hidden checks the agent can't see, and stricter scoring for originality.

Model cards

Recommended models get a card with their limits, quirks, provider tips and QuorX results, and the agent reads the ones it uses.

Cache share per model

Usage shows how much of each model's input came from the prompt cache, so you can see where the money goes.

Review, hooks, schedules, memory

/review lists bugs in what changed with file and line. Hooks run your own commands around the agent's work. Schedules start chats on their own. Memory keeps facts you approve.

A first-run tour, export and import

A short tour of projects, Strict and YOLO, the deciders and costs. Export saves your chats, projects and settings to one file; Import restores them anywhere.

The main changes in 0.2.7 come with write-ups: what was tried, what was measured and what didn't work. Read the research notes ↗

Built with QuorX

Try what it built, live.

Two apps from real QuorX 0.2.12 runs, each from one request: written, tested and reviewed by QuorX, and hosted here as they came out.

Skyline

Live weather and air quality for any city, a sky drawn from the real conditions, and Kite Day: fly a kite in the city's real wind. QuorX found the free weather API by researching it in its own Chrome tabs, then built the app.

  • 29 min
  • tests pass
  • played its own game
  • reviewer 4/5 ×5
Open the live demo →

Uses live data from Open-Meteo once you open it.

Black Hole Lab

A black hole you can play with: gravitational lensing ray-marched on your graphics card, a Doppler-beamed disk, and probes on relativistic orbits that precess into rosettes.

  • 26 min
  • 19 tests pass
  • reviewer passed
Open the live demo →

Heavy on graphics: it checks your GPU before it starts.

Both demos, with how they were made →

Deliberately narrow

What it doesn't do yet.

  • Not code-signed yetWindows may warn before the installer runs. Check its SHA-256, or build it from source.
  • Windows onlyQuorX is built and tested for Windows. macOS and Linux aren't supported.
  • No OS sandbox yetThe guards work at the command level. They are not a container.
  • It runs real commands on your computerKeep YOLO for projects you trust. Strict is the default.

Research · Video direction

The Director's Harness

Ten video skills, one per route: code, images, AI clips, footage, or a mix.

Analysis only Nothing here has been tested on video yet.

Newsletter

Hear when QuorX ships something new.

One email per release or research piece. Kept on our own server, never sold, and you can leave anytime.

What we keep, and how to leave

Get QuorX.

Which one updates first?

  1. 1From sourceEvery change, as soon as it's merged
  2. 2InstallerEach release, once it's out; it updates itself
  3. 3Microsoft StoreEach release, after Microsoft certifies it

Windows

Microsoft Store

Microsoft signs it and keeps it up to date, so Windows shows no warning.

0.2.16 isn't in the Store: get it with the installer below or from source. The Store copy updates itself with a later Store release.

Get QuorX from the Microsoft Store

Direct download (.exe) QuorX-Setup-0.2.16.exe from the 0.2.16 release. It updates itself, but it isn't code-signed yet, so Windows SmartScreen may warn the first time you run it. Every release has SHA256SUMS.txt and a signed build attestation:

PS> Get-FileHash .\QuorX-Setup-0.2.16.exe -Algorithm SHA256

Open source · Apache 2.0

Let's build together

QuorX is built in the open. Run it from source, tell us what breaks, suggest what's next, or send a pull request. Every bit helps.

Run it from source on Windows, with Node.js 20 or newer and an OpenRouter account:

git clone https://github.com/mims1234/QuorX.git
cd QuorX
npm install
npm start

Then open http://localhost:5188 and choose Sign in with OpenRouter.

Prefer the desktop app? From the same folder (the first line installs Electron, about 100 MB, once):

npm run desktop:setup
npm run desktop

Official downloads come only from the Microsoft Store, GitHub releases and this site. Forks are welcome under a name of their own.