The agent in your Chrome
Atlarix has no browser of its own for the agent to drive. It works in your Chrome — or Edge, or Brave — through the free Atlarix extension, and that is how it tests the app you are building.
What it is
When the agent needs a real browser — to open your dev server, click through a flow, or check what a page actually shows — it works in the browser you already use: Chrome, Edge or Brave, through the Atlarix extension.
The tabs it opens are gathered in an Atlarix tab group, so its work stays apart from yours and you can watch it happen.
Installing the extension
Install Atlarix for Chrome from the Chrome Web Store — it is free. The desktop app connects to it directly on your machine.
The desktop app driving your Chrome works on every plan, including Free. Only the extension's own side-panel agent, which you chat with inside Chrome, needs Pro or Atlarix Core credit. More on the extension page.
How the agent reads and acts
The agent can open a URL, read the page, and — in every mode except Plan — click, type and hover, then read the page again to see what changed.
It can take a screenshot when a literal picture is genuinely needed: a design comp to reproduce, an image's actual content, a canvas.
Console and network
The agent reads the page's console messages and its network requests, including failed ones — either everything it has seen, or only what happened since the last navigation, so the output from one step does not bury the next.
That is how it fixes what actually broke at runtime rather than guessing from the source.
Checking how a page looks
To judge the layout, the agent asks for a visual report of the rendered page — blank or broken areas, invisible and low-contrast text, overlapping elements. It is cheaper and more precise for layout facts than reading a screenshot, and it points at the element that is wrong.
Testing your dev server
Start your dev server from chat, and the agent opens the printed localhost URL in the Atlarix tab group. From there it can exercise the change it just made, read the console and network for errors, and check the layout — the same loop you would run by hand.
Because these are your own browser's tabs, a site you are signed into stays signed in.
If the extension is not connected
The agent says so plainly and links you to the Chrome Web Store to install it, rather than failing quietly. Nothing else about the task changes — it just cannot open a page until the extension is connected.
Web search is separate and needs no extension: web_search and read_url run inside Atlarix itself.