ego-lite
The fastest browser for AI agents to run browser automation, built for sharing your logged-in browser state with your AI agents, like Codex or Claude Code, without disturbing you. Zero cost, zero config.
Runs with mockssource: GitHubhomepageJavaScriptMITcommit dca7003349c5
JavaScript, MIT licensed. The project labels itself: agent skills, ai agent, automation, browser, browser automation, claude code, codex and hermes agent.
ego-lite runs, with stand-ins for the services it depends on. An Argusic agent installed it in 4.3 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 ego-browser package installs, builds, and passes 494 unit tests on Node 22; the CLI reads JS from stdin and executes it.
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 92 of 100 (the mean of this project's run scores).
At a glance
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js v18 installed, project requires >=221.5 minutes
- Install time
- 4 minutes
- Cold machine to finish
- 2 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm test exited 0, 494 tests passed, 0 failed; CLI echo test 'hello from ego-browser' printed correctly; -h flag printed usage
- Model tokens used
- 81,831
- Exact commit tested
- dca7003349c5
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Typical usage:
ego-browser <<'JS'
const task = await taskSpace('demo')
const page = task.page('p1')
await page.goto('https://example.com')
console.log(await page.snapshot())
JS
Helpers are pre-imported and the browser connection is prepared automatically.
All done. Here's the summary:
tokens used
81,831
All done. Here's the summary: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
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 4.3 minutes to install, slower than the median of the 13 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 14 agent-skills projects Argusic has installed and timed, ego-lite was the 10th fastest to reach a running state, and 11 of 14 reached one at all.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.01 |
Topics (from GitHub)
agent-skillsai-agentautomationbrowserbrowser-automationclaude-codecodexhermes-agentskillsskills-sh
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ego-lite)Questions
- Does ego-lite run?
- ego-lite runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 4 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test ego-lite?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit dca7003349c5. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test ego-lite?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ego-lite take to install?
- 4.3 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 ego-lite need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ego-lite?
- 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 ego-lite compare with the alternatives?
- Of the 14 agent-skills projects Argusic has installed and timed, ego-lite was the 10th fastest to reach a running state, and 11 of 14 reached one at all.
- Where is the evidence for ego-lite?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.