AIPex

AIPex: AI browser automation assistant, no migration and privacy first. Alternative to Manus Browser Operator、 Claude Chrome and Agent Browser

Runssource: GitHubhomepageTypeScriptMITcommit 4173fa865fed

TypeScript, MIT licensed. The project labels itself: accessbility testing, agent browser, agent skills, browser automation, browser use, chatgpt atlas alternative, chrome extension and claude chrome.

AIPex runs. An Argusic agent installed it in 1.5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The project builds, typechecks, and all 639 tests pass across 5 packages using Node 22.15.0.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.04 (measured)
recorded runs
2
last tested
stars
1,285
forks
139
open issues
18
watchers
14
size
4 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing AIPex, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Node 18.19.1 too old — vitest 4.x, vite 7.x, jsdom 29, @vitejs/plugin-react require Node >= 20. Errors: (1) @exodus/bytes ESM/CJS mismatch in jsdom caused ERR_REQUIRE_ESM crash in dom-snapshot, aipex-react, browser-ext tests. (2) @vitejs/plugin-react ESM module couldn't be loaded by vitest config on Node 18. (3) File global undefined in Node 18, causing instanceof File to throw ReferenceError in core tests.3.5 minutes
Install time
2 minutes
Cold machine to finish
4 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
npm run preflight (format + lint + typecheck + test) on Node 22.15.0, exited 0, all 5 workspace packages pass typecheck, 639 tests pass, 10 skipped (aipex-react), 0 failures.
Model tokens used
74,128
Exact commit tested
4173fa865fed
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

packages/browser-ext test:    Start at  13:20:07
packages/browser-ext test:    Duration  1.37s (transform 223ms, setup 274ms, import 224ms, tests 26…
packages/browser-ext test:
packages/browser-ext test: Done
All **5 packages** pass typecheck and all **639 tests pass** (10 skipped). The project was on Node …
Here's the final report:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 1.5, "…
tokens used
74,128
All **5 packages** pass typecheck and all **639 tests pass** (10 skipped). The project was on Node …
Here's the final report:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 1.5, "…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 1.5 minutes.
  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 1.5 minutes after the clone.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.04
Argusic Runner1/3Runs100.000.04

Topics (from GitHub)

accessbility-testingagent-browseragent-skillsbrowser-automationbrowser-usechatgpt-atlas-alternativechrome-extensionclaude-chromegemini-chromemcpopenclaw-alternativetab-management

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/AIPex.svg)](https://argusic.com/subject/aipex)

Questions

Does AIPex run?
Yes. AIPex runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test AIPex?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4173fa865fed. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test AIPex?
The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does AIPex take to install?
1.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does AIPex need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing AIPex?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for AIPex?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion