Browser engineering · Anti-detect · Live
A hundred identities,one machine.
Argus is an anti-detect browser: a custom Chromium fork that carries a different, coherent device identity in every window, and a desktop control plane that decides what each of those windows is allowed to know.
▸ Specification
§ 01 · About
You cannot fake a browserfrom inside the page.
A browser identity is not one value. It is a few hundred of them — canvas and WebGL output, audio characteristics, installed fonts, screen metrics, timezone, language, hardware concurrency — and they are all expected to agree with one another. Change some and leave the rest, and the disagreement is itself the signal.
The usual approach is to patch those values from inside the page, with an extension or an injected script. That works until something asks the question a different way. A property that has been overwritten in JavaScript does not look like a property that was always that value, and checking for the overwrite is cheaper than checking the value.
So the identity had to move below the page. Argus ships its own Chromium fork, with the spoofing compiled into the engine and driven by launch flags the page never sees. There is nothing in the JavaScript environment to find, because nothing in the JavaScript environment was changed.
That one decision is what makes this a compiler and toolchain project rather than a web project — and it is why it takes a build pipeline across three repositories rather than a bundle.
§ 02 · What's inside
Four decisions that shaped the build
Fingerprint, WebRTC policy and locale are applied in the browser process, below anything a page can reach. A script cannot read around the identity because the identity is not implemented in script.
One profile, one on-disk Chromium directory, one cookie jar, one proxy. Every session starts from its own directory with nothing carried over from any other.
A workspace holds up to a thousand profiles across twenty-five seats, with a shared proxy library under live health checks rather than a text field on every profile.
The app speaks the Model Context Protocol, so an agent that already knows how to use tools can drive profiles without being taught an API. A loopback HTTP bridge covers everything else.
§ 03 · Design system
Achromatic paper,one cyan that means buy.
Every neutral in the interface is a grey with no hue in it, so the only colour on screen carries meaning. Cyan marks the commercial path; green and red are signal-only. Both themes ship together, and nothing hardcodes a colour — a component that needs a value takes a token, and the token resolves per theme.
▸ Palette · light theme
▸ Typography
Hero and section headlines, set tight. The ladder clamps between 34 and 52 pixels so a headline never wraps at an awkward width.
Body, subtitles and table copy. One family across the whole interface keeps the chrome quiet and the product loud.
Launch flags, proxy strings, API routes — anything the user is expected to copy exactly.
§ 04 · Surfaces
Five surfaces,one workspace.
The control plane is organised around what a session needs before it opens and what it leaves behind once it closes. Each surface owns one of those, and an automation can reach across all of them.
- P-01ProfilesLIVE
- P-02ProxiesLIVE
- P-03AutomationsLIVE
- P-04ScheduleLIVE
- P-05DatasetsLIVE
§ 05 · Try it
Run a profile yourself.
Argus is free to start — five profiles, no card. Signed and notarised builds for macOS on Apple Silicon and for Windows 10 and 11.