Gemini-Nexus

Gemini Nexus 是一款面向浏览器场景的 AI 助手扩展,集成 Gemini Web、Gemini API 与 OpenAI 兼容接口,支持网页上下文、图像处理、工具调用和 MCP 浏览器控制。

Runssource: GitHubJavaScriptMITcommit aeaa06cce02d

JavaScript, MIT licensed. The project labels itself: browser automation, chrome extension, gemini, google gemini, llm, manifest v3 and side panel.

Gemini-Nexus 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.

Dependencies installed, Vite build compiles 1790 modules without error, all 1437 tests in 201 test files pass, and the Chrome extension packages successfully to artifacts/chrome-extension/

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 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.03 (measured)
recorded runs
2
last tested
stars
1,131
forks
152
open issues
11
watchers
4
size
6 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 Gemini-Nexus, 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.

  • [email protected] depends on webidl-conversions@8 which uses ArrayBuffer.prototype.resize (Node 20+ API), crashes on Node 180.5 minutes
Install time
2 minutes
Cold machine to finish
7 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
npm test exited 0, 201 test files passed, 1437 tests passed; npm run package:extension produced artifacts/chrome-extension/
Model tokens used
117,623
Exact commit tested
aeaa06cce02d
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

The end of the recording

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

**One caveat worth surfacing:** the `knip` lint runner and `marked` library also require Node 20+, …
tokens used
117,623
Here's the complete report:
**Error fixed:** `[email protected]` requires Node ≥20 (via `webidl-conversions` referencing `ArrayBuffe…
**Verification:**
- `npm install` → dependencies installed successfully (with known Node 18 engine warnings)
- `npm run build` → Vite build completed, 1790 modules transformed
- `npm test` → **201 test files, 1437 tests passed** (exit 0)
- `npm run package:extension` → extension packaged to `artifacts/chrome-extension/`
- The only remaining artifact is a harmless jsdom teardown error (`window[i].close is not a functio…
**One caveat worth surfacing:** the `knip` lint runner and `marked` library also require Node 20+, …

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, faster than the median of the 14 comparable projects Argusic has measured.
  • 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.

Of the 15 browser-automation projects Argusic has installed and timed, Gemini-Nexus was the 5th fastest to reach a running state, and 13 of 15 reached one at all.

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.03
Argusic Runner1/3Runs with mocks92.000.08

Topics (from GitHub)

browser-automationchrome-extensiongeminigoogle-geminillmmanifest-v3side-panel

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/Gemini-Nexus.svg)](https://argusic.com/subject/gemini-nexus)

Questions

Does Gemini-Nexus run?
Yes. Gemini-Nexus 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 Gemini-Nexus?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit aeaa06cce02d. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test Gemini-Nexus?
The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does Gemini-Nexus 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 Gemini-Nexus need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing Gemini-Nexus?
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.
How does Gemini-Nexus compare with the alternatives?
Of the 15 browser-automation projects Argusic has installed and timed, Gemini-Nexus was the 5th fastest to reach a running state, and 13 of 15 reached one at all.
Where is the evidence for Gemini-Nexus?
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