ARGUS

Your product's spec, alive.

I see · I guard · I protect

An autonomous QA agent that tests your web app in a real browser, remembers how your product behaves, and tells you the moment something silently breaks.

npm install -g https://github.com/im-anp/argus-releases/releases/latest/download/argusqa-latest.tgz
runs 100% on your machine bring your own AI key — Claude · GPT · Gemini macOS · Linux · Windows

The problem

Three questions every team fails to answer

How does this feature behave today?

In most teams the answer lives in one senior QA's head. When they leave, it leaves with them.

It worked last week.

The worst bugs don't crash. The page renders fine while the API behind it returns 500s. Nobody notices until a customer does.

Can you re-check all flows before release?

Someone re-clicks the same fifty flows. Every release. Again.

How it works

Point it at a URL. That's the setup.

EXPLOREwalks your app itself
→
LIVING SPEChow it really behaves
→
VERIFYpass · drift · broken
→
FINDINGSscreenshot · repro · API
→
SHAREreports · Jira · Slack
↻ every night, on its own

What you get

A QA teammate with a hundred eyes

🔭 EXPLORES BY ITSELF

Paste a URL, watch it walk your product live and draft a behavioral spec — pages, flows, invariants.

🕵️ CATCHES DRIFT

Every flow classified pass / drift / broken. Drift — "works, but different than recorded" — is the category everyone else misses.

🌐 TESTS THE API LAYER

Watches every network call and console error while clicking. UI fine but the backend 500'd? A finding — endpoint, status, and response body quoted.

🐛 REAL BUG REPORTS

Exact URL, expected vs observed, numbered repro, API evidence, screenshot. Retest any bug: pass = resolved, later failure = reopened. Automatically.

📋 SHAREABLE REPORTS

Every run becomes an execution report — pass rate, per-case results, evidence. Save as PDF or copy as Markdown.

🔐 LOGINS, PASSWORDS UNSEEN

Form logins stored encrypted, replayed by name. SSO/2FA: log in once in a real window, Argus reuses the session. The AI model never sees a credential.

🛡️ GUARDRAILS

Deleting data, payments, sending messages — Argus asks first and never does them unattended. Every permission visible and revocable.

📎 READS YOUR DOCUMENTS

Drop in a PRD, a mockup, a user's bug screenshot. It drafts test flows, compares design vs reality, reproduces the report.

Product memory

You forget. Argus doesn't.

Six months later, nobody remembers why the delete button shows no toast. Argus does — with the evidence still attached.
"How does checkout behave for guest users?" — answered from verified memory, not guesswork. "Did we ever test this? What happened?" — full history in Runs and Reports. New teammate? Point them at the living spec instead of a week of shoulder-tapping.

Integrations

Connects to where your team lives

JIRA — ONE CLICK

Connect with a browser approval, no tokens to copy. Findings become complete tickets with the screenshot attached — straight from the bug card, always with your say-so.

SLACK — ONE WEBHOOK

Nightly watchdog digests land in your channel: what passed, what drifted, what broke — before your standup does.

Trust

Private by design

LOCAL ONLY

100% on your machine. Your app, your data, your history — nothing is sent to us. There is no "us" server at all.

YOUR AI KEY

Bring your own key — Anthropic, OpenAI, or Google. Usage bills to your account. Switch anytime with argus provider.

YOUR SPEC

Plain markdown on your disk, built on Google's open OKF knowledge standard. Read it, version it, take it anywhere.

Get started

Five minutes to your first report

# Node 24+ required — make sure it's active when installing
nvm use 24
npm install -g https://github.com/im-anp/argus-releases/releases/latest/download/argusqa-latest.tgz
argus   # picks your AI provider, opens http://localhost:3123
argusstart Argus — agent + dashboard at localhost:3123
argus providerswitch AI provider or key (Claude / GPT / Gemini)
argus updateupdate to the latest version
  1. Explore — paste your app's URL. The draft spec appears in the Spec tab.
  2. Behind a login? Add a profile in Settings, or capture an SSO session once.
  3. Verify — say "verify the spec". Findings land in Bugs with screenshot, repro, API evidence.
  4. Retest — one click after a fix. Green means resolved.
  5. Share — Reports → Save as PDF, or File to Jira from the bug card.
  6. Ask — "How does checkout behave?" — answered from the living spec.
Download the latest release →

FAQ

Fair questions

Is my product data used to train anything?

No. Argus runs locally and talks only to the AI provider you chose, under your key and their terms.

Does it need repo or CI access?

No. Argus tests your product the way a user experiences it — through the browser. Production, staging, localhost, or behind your VPN.

How is this different from test-automation tools?

Test tools run scripts you write and maintain. Argus builds and maintains its own understanding of your product, verifies it against reality, and answers questions about it. The living spec is the product — tests are a byproduct.

What does it cost?

Argus itself is free to install. You pay your AI provider directly for usage, on your own key.