How Argus works

Argus is not one program pretending to be private. It is two, with a deliberate wall between them — and this page is the reference for what each one does.

On this page

Two processes, one boundary

Most multi-profile browser tools make the same mistake: they keep management state — your account, your proxy pool, your saved cookies — in the same process as the browsing session. That is a liability, not a feature. Argus keeps them apart on purpose.

The control plane

Argus Launcher

The desktop app you sign in to. It owns your account, your proxies, your cookie sets and your extensions, and it decides what a browser session is allowed to see.

The data plane

Argus Browser

A purpose-built Chromium. It receives one launch payload, opens a session, and knows nothing else — it never signs in, and it never sees your account or your other profiles.

Everything the browser knows arrives as command-line arguments at launch, and nothing else is ever handed across:

--argus-profile-launch
--argus-profile-id
--argus-profile-name
--argus-fingerprint-json
--argus-proxy-type / --argus-proxy-host / --argus-proxy-port
--argus-proxy-user / --argus-proxy-pass
--user-data-dir
--load-extension

The browser has no credentials to sign in with, no list of your other profiles, and no way to reach your organization's data. If a site compromised a session tomorrow, there is nothing on the other side of that wall for it to find.

The edit-folder dialog with a name field, icon and colour pickers, and the note that folders organize launcher profiles only while browser sessions stay separate.
Folders are a launcher concern: they organize the profiles list, and the browser sessions those profiles point at stay separate.

The launcher

The desktop app you sign in to. It owns your account, your proxies, your cookie sets and your extensions, and it decides what a browser session is allowed to see.

Profiles

Hundreds of fully isolated profiles, each with its own storage, cookies and identity.

  • Create, clone, tag, and sort into folders
  • Bulk launch, bulk edit, and bulk delete across the whole list
  • Search, filter, and paginate — built for lists that outgrow one screen
  • Custom status labels and per-profile notes
  • CSV import and export
  • Delete is soft: profiles go to Trash and can be restored
The profiles table in the Argus launcher: fifteen profiles grouped into folders, each row with a status, proxy-check latency, tag marks, and its own Launch button. Ten more columns are hidden behind a Columns control.
Every profile is a row you can launch. Folders, statuses, proxy-check latency and tags live in the table; ten more columns are one click away.

Proxies

A shared, searchable proxy library with live health checks — not a text field per profile.

  • HTTP and SOCKS5, including SOCKS5 that requires a username and password
  • Health checks report egress IP, country, and latency
  • Checks run automatically for new or failing proxies, concurrently rather than one at a time
  • Any proxy can also be re-checked on demand
  • A proxy that fails its check blocks the launch instead of leaking your real IP
  • CSV bulk import

Cookie sets

Upload a cookie set once, then assign it to any profile that needs it.

  • A shared library — swap a set between profiles without re-uploading it
  • Import from a file or a whole folder at once
  • Cookies are seeded into the session at launch, so the profile opens already signed in

Fingerprints

An auto-generated hardware identity per profile, coordinated so that nothing contradicts anything else.

  • Windows, macOS, and Linux presets, with the user-agent and UA-CH metadata generated to match
  • Platform, CPU cores, memory, screen, timezone, and languages generated together as one coherent set
  • Per-profile editor for the parts you want to pin yourself
  • One-click re-roll produces a new identity while preserving your configuration
The create-profile dialog: proxy mode set to Assigned proxy with Direct and Free Proxy alongside, a fingerprint summarised as Windows 11 with WebRTC proxy-only and canvas noise, and a live preview of the stored profile on the right.
One dialog sets the proxy mode — assigned, direct, or free — and the fingerprint. The right rail shows exactly what will be stored before you save.

Extensions

Install an extension once for the team; every machine that needs it materializes it.

  • Add by Chrome Web Store ID or from a local unpacked folder
  • Give a shared extension a display name your team will recognize
  • Assign across selected profiles rather than one at a time
  • Ships with four built-ins: a cookie manager, FoxyWall Proxy, SMS Activate, and an optional captcha plugin

Four built-ins ship with every install. Their toggles live on the organization, not on you — switching one off switches it off for the whole team's profiles.

Argus Helper

The side panel in every profile window: proxy status, cookies and this launch's automations.

Switching this off removes the whole panel — the session's exit, timezone and device checks, cookie sync, and the automation runner. It also seeds a profile with the cookie set assigned to it, once, on its first launch.

SMS Activate

Buy a phone number for a verification code, so a profile never signs up with yours.

Needs your own API key from onlinesim.io. Numbers are single-use: one number, one verification. Buy another for the next account.

FoxyWall Proxy

The free-proxy backend, bundled into every profile.

Only auto-connects for profiles set to Free Proxy mode. This switch stops it being bundled at all.

Captcha Plugin

Solves reCAPTCHA in the browser itself, on CPU. No account, no per-solve fee.

Off until you enable it: the model is a ~56 MB download, fetched once per machine and shared by every profile.

The extensions tab: six installed, four bundled extensions marked Included with per-card toggles, two Chrome Web Store entries, an Add from link or folder button, and a note that bundled extensions apply to the whole team.
Bundled extensions are org-wide — switching one off switches it off for the whole team. Your own come from a link or a folder.

The Discover view carries twelve more from the Chrome Web Store, curated into four groups. Anything not listed is still reachable: paste any Web Store link, or add an unpacked folder of your own.

Captcha & automation

Captcha Solver: Auto Recognition and BypassHands captchas to the 2Captcha service and fills in the answer.
Buster: Captcha Solver for HumansSolves reCAPTCHA audio challenges in one click.
TampermonkeyRuns your own userscripts on any page.
Selenium IDERecord and replay a browser flow without writing code.

Cookies & identity

Cookie-EditorRead, edit and delete a site's cookies from the toolbar.
Session BuddySaves and restores a window's open tabs as a named session.
User-Agent Switcher for ChromeOverrides the UA string per site. Profile fingerprints override it back.

Proxy & network

Proxy SwitchyOmegaPer-site proxy rules, on top of the profile's own proxy.
ClearURLsStrips tracking parameters out of every link you follow.

Privacy & blocking

uBlock Origin LiteContent blocker. The MV3 build, since MV2 uBlock is delisted.
Privacy BadgerLearns and blocks trackers as you browse.
Dark ReaderGenerates a dark theme for any site.
Chrome's own extensions popover inside a launched profile, listing Argus Cookie Manager, Cookie-Editor, FoxyWall Proxy and SMS Activate.
Inside a launched profile they are ordinary Chrome extensions — the browser's own popover lists them like any other.

Cloud sync & teams

Sign in once and your workspace follows you; a team shares one pool instead of trading files.

  • One account, signed in with an email and password, on every machine you use
  • Profiles, proxies, cookie sets, folders, statuses, and bookmarks sync to your organization
  • Members of an organization share one pool of everything above
  • Every write touches a single row, so two people working at once cannot overwrite each other
  • Plan entitlements are enforced in the database, not just in the interface

Local automation API

A local HTTP bridge that lets your own tooling drive the app — on your machine, not ours.

  • Scoped API keys you can create, list, and revoke
  • List, read, update, and delete profiles; create, update, and delete proxies
  • Assign a proxy to a profile, update a fingerprint, and launch a session
  • Bulk cookie matching, local cookie push, and proxy re-import
  • Set up as an MCP integration so an agent can drive it directly
  • Every request from a new client raises an approve-or-deny prompt in the app first

Updates

The launcher keeps itself and the browser current without you chasing a download page.

  • Update checks run in the background and download automatically
  • You choose when to restart and apply
  • The browser engine is fetched and installed on demand — there is no second installer to run

The browser

A purpose-built Chromium. It receives one launch payload, opens a session, and knows nothing else — it never signs in, and it never sees your account or your other profiles.

Authenticated SOCKS5 that actually works

The clearest reason Argus ships its own browser instead of automating someone else's.

  • Chromium's own SOCKS5 client only speaks the no-auth variant, so a proxy that needs a username and password simply cannot be used
  • Argus runs a local relay that performs the RFC 1929 handshake on the upstream leg
  • The profile is pointed at a loopback address, so no proxy authentication dialog ever appears
  • This is not a workaround layered on top — it lives inside the browser process

Fingerprint spoofing in the renderer

The identity is applied below the page, where a script cannot read around it.

  • Canvas, WebGL (including reported vendor and renderer), and audio
  • Platform, languages, timezone, screen, device memory, and CPU core count
  • Each surface runs in one of four modes: real, noise, off, or manual
  • A script sees the spoofed value because that is the only value present, not because a wrapper hid the real one

WebRTC leak protection

Your real address does not escape through WebRTC, and a page cannot switch that off.

  • Enforced as browser policy on the profile, beneath the JavaScript layer
  • Applied to every profile — it is not a toggle you can forget to set
  • Assigning a proxy to a profile that was still reporting its real address upgrades it automatically

Real profile isolation

Each session starts from its own directory with nothing carried over from any other.

  • A dedicated user-data directory per profile — separate storage, cache, and cookie jar
  • Session restore is disabled, so a previous run cannot resurface in a new one
  • The proxy is applied at the network layer, not through an extension that a page can detect
  • A default block list covers remote-access ports that sites probe to detect automation

Signed and notarized

The macOS build is signed by SIMNETIQ LTD, notarized by Apple, and stapled.

  • Opens with no Gatekeeper warning and no right-click-to-open workaround
  • Hardened runtime enabled
  • macOS builds are Apple Silicon; Windows builds are x64

Try it

Download the launcher; it fetches the browser on first run.

macOS (Apple Silicon, signed & notarized) · Windows 10/11 (x64) · v1.0.72