What's new

QuorX is in the Microsoft Store: Microsoft signs that copy and keeps it up to date, so Windows shows no warning.

The agent's browser tells it whether a page started any sound, so it can check a game or a player it can't hear.

The Windows app is about 55 MB smaller: it carries only the terminal parts it uses.

The Models report in News points to OpenRouter's rankings for choosing a model.

With another copy of QuorX already running, the desktop app starts its own instead of opening the other one.

News has seven new articles on what 0.2.7 measured and learned, from the cache-friendly prompt to a lock-down post-mortem.

The Models, Tests and Platforms reports in News are rebuilt with 0.2.7's benchmark and test results.

The agent's browser can wait for a timer, a round or an animation, instead of sleeping in the shell.

The agent's browser presses key combinations like Shift+R and Control+S, and a capital letter holds Shift.

The Tests report in News shows each pack's results only, not details of the computer that ran the tests.

/review lists bugs in what changed (the last reply, uncommitted changes or the branch) with file:line; send the ones you agree with to the agent.

Hooks run your own commands around the agent's work, like npm run lint after every file write, set in each project's settings.

Schedules start a chat on their own, like every weekday at 9 in a project, with the prompt, model and mode you saved.

Memory: a short list of facts and preferences you approve, like "I use pnpm", that every chat gets; edit it in Settings.

Export my QuorX saves your chats, projects, settings and rules to one file, and Import restores it on any computer.

Paid media work with several parts is priced up front as one production plan and approved once.

A video clip can start from a picture, and edit_video joins clips, stills, voice and music into one .mp4 with ffmpeg.

Recommended models have a model card with their limits, quirks and tips, and the agent reads the ones it uses.

A short first-run tour shows projects, Strict and YOLO, the deciders, costs and the terminal.

Research notes for 0.2.7 in docs/research: how QuorX checks its agent across models, a cheaper prompt, and a 0.2.5 post-mortem.

Each step's prompt is smaller and puts what doesn't change first, so more of it is read from the cache.

Usage shows how much of each model's input came from the prompt cache.

Closing the desktop window explains that QuorX keeps running in the tray, and Quit QuorX is easy to find.

The desktop app ships its full terminal again, plus the terminal view and math files the installer had left out.

A reply resumed after a restart stays in one bubble and keeps its result.

Two copies of QuorX on one computer no longer sign each other out.

A project inside another project's folder no longer fills that project's file list and prompts.

A file check that runs out of time no longer reports a syntax error in a file that is fine.

QuorX answers only the computer it runs on: phone and other-device access is gone, and so is everything it opened up.

Hook commands go through your command rules and approvals like the agent's own, and /review never sends secrets files.

An imported backup never changes your approval settings, and its schedules arrive paused.

Every pull request is tested on Windows and Linux, and new versions reach installed apps only once promoted.

0.2.5 locked QuorX out of its own data files, so projects, chats and the Terminal seemed gone; nothing was lost.

QuorX repairs those files by itself when it starts, before it reads anything, with no administrator rights needed.

The desktop window no longer says its app link is not valid after a restart.

The data folder stays private to your account: only the folder is locked, and its files inherit that.

If the project list can't be read, QuorX says so instead of showing an empty list.

QuorX answers only its own windows: open the link it prints at start once per browser (the desktop app does this for you).

Other devices are off for new installs, and QuorX listens only on this computer until you turn them on.

Commands can't read QuorX's keys or browser profiles, and reading files outside the project asks first.

Web fetches check every redirect, and a page from one chat can't read another chat's files.

Releases are built by a read-only job and published by a separate step, with checksums checked in between.

Command rules move from each project's folder into QuorX's own data folder; add any you saved before again.

A video direction skill for trailers, explainers and social cuts, with the research behind it.

Code and styles for features that are gone were removed, about 1,100 lines lighter.

QuorX is open source under the Apache License 2.0: use it, change it and fork it, for personal or commercial work.

Each release lists the installer's SHA-256 checksum and a signed proof that GitHub built it from this repository.

A shorter README with the trailer, plus pages on getting started, features, privacy and security.

A project's spend in the sidebar no longer goes below zero while a reply is running.

The agent's own page in the Browser tab shows its picture after the reply, instead of a broken image.

Prompt enhancer: a small model spells out what your request implies, shown under your message for you to correct.

The agent and the deciders read that reading, so a movie trailer's voice-over counts as asked for.

In YOLO, a question or an unsettled approval waits 15 seconds for you before the deciders answer or it carries on.

Wait for me, or typing in the card, stops that clock; set the time in Settings under Budget & approvals.

A helper script the agent writes in its own scratch folder is judged on harm only, so the deciders no longer turn it down for not being asked for.

PowerShell lines that only work with text, such as $_.FullName.Replace(...), .IndexOf(...) and .Substring(...), count as reads and no longer wait for approval.

A plan that nobody has started after 10 steps gets a nudge to begin.

An approval the deciders couldn't settle showed up as two identical cards.

The placeholder left when old text is trimmed from the conversation could be written into a file. Such writes are refused now.

Bugs the reviewer finds that a user would notice send the build back even when its scores pass.

After the checks send a build back, the final reply keeps its answer to your message and adds what was fixed.

The cost card at the end of the steps is more compact.

The reports, articles and What's new use neutral wording, written for anyone who reads them.

Numbers worked out from the computer's own logs are labelled On this computer, and still never leave it.

QuorX has its own logo, a Q whose tail is an X, in the top bar, on Home, in Settings, by the version and as the tab icon.

The desktop app uses the logo for its window, taskbar, tray, notifications and installer.

News in the sidebar: what's new in each version, reports and articles, with a dot when something is new.

Design systems: pick one of six starters or measure one from a site or screenshot, and every chat in the project builds to it.

Comment on part of a page in the Browser tab: point at an element, say what should change, and the agent changes only that.

Export a page as a PDF or a full-length PNG, or the project's files as a ZIP.

Any MCP client can hand work to QuorX: list projects, start a reply, follow it and stop it; approvals stay with the person at QuorX.

Replay a finished reply step by step with its real timing, a scrubber and speeds up to 16×.

Home's start box picks a project, a recent folder or a template before typing.

Projects show their GitHub repo, can be pinned or archived, and the chat header shows what the project has spent.

Costs update live while a reply runs, and a reply that ended early still counts what its calls spent.

A simpler message box: the model, then This chat's settings with the caps, reasoning and every tool as one icon.

Home lists the projects, pinned ones first, each with its latest chats.

When the reviewer can't open any page, it says so instead of scoring a browser that failed.

The side panel can be hidden for a chat-only view, text size and page zoom are set separately, and notifications carry QuorX's name.

The agent works through a real shell, so it can build command-line programs and desktop apps, not only web pages.

Rules read every command before it runs; deleting the user profile, a drive or a system folder is blocked however it is written.

Stop ends everything a command started and confirms nothing is left, and Undo now covers what commands change.

A tripwire stops a command part-way when many files outside the project disappear.

In YOLO the deciders vote on risky commands; they see only the facts, need a quorum, and never include the chat's own model.

Spending caps per reply and per day, and installs for the whole computer always ask first.

QuorX checks that a toolchain can really build here before the agent starts, and says what is missing.

The agent can answer prompts in terminal programs, click through Windows desktop apps and Android emulators, and use a debugger.

A Running tab shows everything running in a project and who started it, with Stop on each and Stop all.

Long builds and installs move to the background instead of being cut off at a time limit.

Platform packs: one file per kind of app tells QuorX how to detect, check, run, debug and explain it.

Anyone can test the packs their computer supports with npm run test:packs, without an OpenRouter key.

.NET: WinForms and WPF apps are built and driven, dotnet test failures are summed up, and netcoredbg debugs them.

Scripts that run other programs are read first and always ask, so a wrapper script can't hide what really runs.

Tauri apps are built, and their window is read and clicked through WebView2.

Go, C, C++ and Rust programs can be debugged with breakpoints, and C and C++ projects get a build check before the reply.

Electron apps are driven through their DevTools port, and the debugger attaches to the main process.

Godot and Unity projects are checked and their tests summed up; MSIX and WiX installers are built with test certificates only.

Android emulators are started and driven, crashes point to the first line of the project's own code, and Flutter apps are checked and debugged.

Java and Kotlin: Gradle and Maven compile checks, JUnit summaries, and a debugger built on the JDK's own.

QuorX runs safely on macOS and Linux: Stop ends whole process groups, rules read bash and zsh, and key folders are off limits.

On a Mac, iPhone and Mac apps are built with Xcode, driven in the Simulator and debugged; crash reports are summed up.

Python desktop apps use the project's own virtual environment, and tkinter and PyQt windows are driven and debugged.

The update button in the sidebar is short and fills up like a progress bar while the update downloads.

With the sidebar folded, a waiting update shows as an icon above restart, theme and settings.

A reply no longer fails its final check when the hidden browser won't start; it uses the agent's own tab or checks the files.

QuorX finds Chrome installed for one user, 32-bit Chrome, Brave and Chromium, and says why a browser didn't start.

Pages the agent makes load from their own local address, so storage works in artifacts and project pages.

The side pane's tabs show only icons when the pane is narrow, and the servers button stays in view.

When the same problem comes back, a second model with a clean context finds the likely cause before the next try.

QuorX runs any model through OpenRouter, with a quorum of decider models behind its choices.

The agent builds web apps, sites and games, and opens each one in a browser to check it before it replies.