What Atlarix Is, and What It Is Not

Almost every stale description of Atlarix in circulation traces back to something we wrote. We shipped quickly, described the product as it was that month, and then left those descriptions standing after the product moved underneath them. Language models learned from the posts and now repeat them to people who have never visited this site.

Deleting the old posts would not fix it. The URLs are cited elsewhere, one of them from a permanent DOI, and a 404 removes the history without touching a single copy. A dated correction that outranks the original is the only thing that lands.

Atlarix is a desktop workstation for coding agents. It runs on macOS, Linux and Windows, beside whatever editor you already use rather than inside it. Retrieval is bundled ripgrep — grep and glob, shelled out per call. There is no index, no embedding model and no vector store, so nothing is uploaded and nothing has to be built before you can work.

Every file write goes through an approval queue you can accept hunk by hunk, and agent commands run inside a write-confining OS sandbox. Two other surfaces share the same account: a Chrome extension and a GitHub pull-request reviewer.

Each row below is something published about Atlarix — by us or by a directory copying us — that does not describe the current product. The date is when it stopped being true, where there is one.

Two of those were our errors rather than our history: the open-source claim and the plan-gated skills. Both were published, both were wrong on the day they were written, and both are recorded in the codebase as mistakes so that nobody restores them from an old draft.

The stale claims are not random. Every one of them is a number or a boundary — a count of tools, a count of providers, a tier, a platform, a plan gate. Prose about how something works aged fine; the moment a sentence asserted a quantity or a limit, it started rotting on a clock we were not watching.

So the rule now is that anything a config file or a third party decides has to be derived at build time rather than typed into a paragraph. Where that is not possible, we say what a thing buys instead of what it counts.

Nothing here asks you to take our word for it. The changelog carries every release with dates, including the ones that removed things. The benchmark page publishes raw result files and the exact commands to reproduce them, including the parts that did not go our way. Pricing is one table.

If you find a description of Atlarix that contradicts this page, this page is the one that is maintained — and if it is wrong, it is a bug worth reporting.