Frequently asked questions

Argus is an anti-detect browser for running many separate online identities at once. It comes as two programs: a launcher, which is the app you sign in to and where you manage profiles, proxies, cookies and extensions; and the browser itself, a purpose-built Chromium that actually opens the sessions.

No. You install the launcher, and it downloads and installs the browser engine for you on first run. There is no second installer to find and no separate update to keep track of.

macOS 13 Ventura and newer on Apple Silicon, and Windows 10 and 11 on x64. There is no Intel Mac build — an Apple Silicon machine is required on macOS.

Yes. The macOS build is signed by SIMNETIQ LTD with the hardened runtime, and it is notarized by Apple and stapled, so it opens normally with no Gatekeeper warning and no right-click workaround. The Windows build is distributed as a standard installer.

No, and this is deliberate. The launcher hands the browser one launch payload — a profile id, a fingerprint, proxy settings, a data directory, extension paths — and nothing else. The browser has no credentials, cannot sign in, and has no knowledge of your other profiles or your organization's data.

Your profile definitions, proxies, cookie sets, folders, status labels and shared extensions sync to your organization so they follow you between machines. The actual browsing session — cache, local storage, and the live cookie jar — stays in that profile's own directory on the machine that ran it.

Yes. Argus takes HTTP and SOCKS5 proxies, including SOCKS5 proxies that require a username and password — which ordinary Chromium cannot use at all. Proxies live in a shared library rather than being retyped per profile, and health checks report the egress IP, country and latency.

Health checks run automatically for new and previously failing proxies, and any proxy can be re-checked on demand. If the proxy assigned to a profile fails its check, the launch is blocked rather than allowed to proceed and expose your real address. A separate background sweep loads real sites through each proxy, so a row can name the site that refused it rather than only saying the connection worked — and if you record the date a proxy's term ends, Argus warns you a week out and asks you to confirm before launching behind an expired one.

Two ways, both with the email address your account is on. Ask for a code and Argus emails you a six-digit one to type in, or use Continue with Google — that opens your normal browser to finish, then hands the session back to the app. The desktop app has no password of its own to remember; the code is requested fresh each time you need one.

Yes. Members of an organization share one pool of profiles, proxies, cookie sets, folders and extensions. Writes are made one row at a time, so two people working simultaneously cannot overwrite each other's changes.

Extensions you add — from a Chrome Web Store link or a local folder — are shared with your organization and assigned to the profiles you choose. The four bundled built-ins are toggled at the organization level, so switching one off switches it off for everyone's profiles, not just yours.

There is a local automation API built into the desktop app: a HTTP bridge on your own machine with scoped keys you can create and revoke, covering profile and proxy CRUD, fingerprint updates, launching sessions and authoring automations. It can also be set up as an MCP integration so an agent can drive it. Every endpoint is documented on the API reference page. It is a local desktop API — there is no hosted web API today. It is on every plan, including Free: what a plan sets is how many profiles, seats and automations the workspace gets, not whether the API answers.

In the launcher, under the API tab. The raw key is shown once, at creation — only a hash is stored, so a lost key is replaced rather than recovered. A key can be scoped to specific folders so it only reaches the profiles inside them, and the first request from any new client raises an approve-or-deny prompt in the app before anything is served. Keys are never created on this website, because the API lives on your machine.

Set Argus up as an MCP server from the launcher's Integrations tab. For most clients — Claude Code, Codex, Cursor, Gemini CLI and others — the launcher writes the config file for you and shows you the path first. Once connected, the agent sees Argus as a set of tools: listing profiles, launching sessions, reading pages. The integrations page documents every supported client and the snippet for doing it by hand, and there is no plan to buy first — MCP works on Free.

An automation is a tree of steps run against one browser profile, through that profile's proxy, cookies and fingerprint: navigate, click, type, extract, run scripts, ask a model, branch, loop and send a notification when it finishes. It runs in the desktop app on your own machine — there is no hosted runner, so nothing executes while the launcher is closed. The automation page documents every step type and its fields.

Both, and which you want depends on the site. Argus ships 29 prebuilt collectors for named services — Google Maps listings, Instagram, TikTok, X and LinkedIn profiles and posts, Shopify catalogues and four job boards — and each one is a form: fill it in and one typed table comes back. They open no browser window at all, they cost none of your plan's automation slots on any tier, and all but 2 of them collect signed out. For a site no card covers, or for anything operating an account of your own, build an automation instead: that drives a real profile with a real browser and can do anything. The scrapers page lists every collector, what it asks for and every column of the table it writes.

No. The calendar fires only while the launcher is running, and a slot it was closed for is marked missed and skipped rather than caught up hours late. That is the same boundary automations have, and it is deliberate: there is no hosted runner, because running your session on our machines would mean handing over the cookies, proxy credentials and fingerprint that make the profile yours. For an overnight calendar, Keep awake asks the operating system not to idle-sleep while the launcher runs — a closed lid still sleeps, and nothing in the app can override that.

In a dataset in your workspace by default: a table with columns you name, shared with your organization, that the save rows step writes into and the load rows step reads back out of on the next run. Point the same step at a data connector instead and it lands wherever you send it — a spreadsheet, an Airtable base, or whatever else the workflow feeds. Datasets can also be built by importing a CSV, JSON, TXT or XLSX file, edited in the grid, and exported whole.

No. Every AI feature — the assistant, the AI automation steps, and the skills they load — runs on API keys you bring yourself, so you pay your model provider directly and nothing routes through anyone else's account. A model running locally on your own machine is reached through a connector and needs no key at all. There is no AI line on an Argus bill because there is no AI usage we can see.

In your workspace, as a connector, so a key is entered once and every automation on every machine you sign in from uses the same one. Two consequences are worth knowing before you paste one in: anyone in the workspace who can open the connectors list can read it, and the local API returns a connector's full configuration to any Argus key allowed to read connectors — so such a key is worth as much as the credentials behind it. Argus masks credentials in its own interface, but that is a convenience rather than a security boundary, so give a connector the narrowest key the provider will issue.

Yes. A skill is the brief the assistant loads for a job plus the pack of tools that job needs, and skills can be listed, read, saved and deleted over the local API — so an agent connected as an MCP integration can author one, as can the assistant itself. What neither can do is grant itself new abilities: a skill picks from tool packs the app already defines, and which tools a skill may touch stays fixed in code. Your edits to the built-ins and any skills you create are stored on the machine you made them on and are never uploaded.

Paid plans are priced in USD and can be paid by card through Revolut or in crypto through OxaPay, for 30 days or 12 months. Create an account, sign in, then choose a plan from the pricing page and pick how you want to pay. If you pay by card you also choose whether it renews: leave auto-renewal on and the card is charged each period until you turn it off, or turn it off and you have bought a single term that simply ends. Crypto cannot recur, so a crypto purchase is always a single term.

If you have an auto-renewing card subscription, turn off auto-renewal from your dashboard at any time. That stops the next charge and you keep the plan and its limits until the end of the term you have already paid for — it never cuts your access short. A single term, bought by card or in crypto, has no next charge to stop; it simply ends on the date shown, and you can drop to the Free plan sooner from your dashboard if you want to. Fees already paid are non-refundable except where required by law; see the refund policy.

Yes — a yearly plan costs ten months' money for twelve months of service, so two months are free. Base is $890 a year instead of $1,068, Team is $1,590 instead of $1,908, and Enterprise is $2,990 instead of $3,588. Switch the toggle on the pricing page to see the yearly prices.

Choose Crypto on the confirmation page and you are sent to an OxaPay invoice, payable in Bitcoin, Ethereum, USDT and a number of others. The invoice is priced in USD and stays open for three hours; the plan is applied as soon as the payment confirms on-chain. Because crypto cannot recur — there is no stored instrument and nothing that could charge you again — a crypto purchase buys one term and then ends. We email you and notify you in the app seven, three and one day before that, and if you buy the same plan again before the date, the days you have left are added on top of the new term, so paying early costs you nothing.

The workspace moves to the Free plan and its limits. Nothing is deleted — every profile, proxy, cookie set and automation stays exactly where it is. The Free limits only restrict how many new ones you can create, so anything above the limit stays put and becomes available again the moment you are on a paid plan.

Each plan sets how many browser profiles the workspace can keep, how many people can share it, and how many automations it can store. Those limits are enforced in the database rather than only in the interface, so they behave the same on every machine you sign in from. See the pricing page for the current tiers.

Sign in and use the support page to open a request, or email us directly. We reply to the address on your account.