chat-on-steroids

Cross-platform local MCP capabilities for ChatGPT with Chrome integration, Goal, Compact & Resume, and durable multi-agent workflows.

Runssource: GitHubTypeScriptMITcommit 3c0578fb02c0

TypeScript, MIT licensed. The project labels itself: automation, chatgpt, chrome extension, electron, linux, local first, macos and mcp.

chat-on-steroids runs. An Argusic agent installed it in 2.5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Dependencies installed, TypeScript typecheck passes, electron-vite build succeeds, Electron v44.3.0 binary launcher works, and the test suite passes 255 of 270 attempted files (5348 tests passing) with zero failures; 3 JSDOM-heavy tests time out in the container but show no failures.

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.26 (measured)
recorded runs
2
last tested
stars
5,194
forks
679
open issues
31
watchers
14
size
117 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 chat-on-steroids, 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.js 18.19.1 too old — project requires >=201 minute
  • GPU not available in container — Electron crashes without --no-sandbox0.3 minutes
  • 3 JSDOM test files hang/timeout in container (content-script.test.ts 21k lines, input-delivery-integration.test.ts, renderer-timeline.test.ts 4k lines)
Install time
3 minutes
Cold machine to finish
48 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
npx vitest run --exclude 3 timeout files: 255 files passed, 5348 tests passed, 0 failures. npx electron-vite build: succeeded in 5.85s. npx tsc --noEmit: exit 0. electron --no-sandbox --version: returned v44.3.0
Model tokens used
480,075
Exact commit tested
3c0578fb02c0
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.

=== TypeScript typecheck ===
pass (exit 0)
=== Electron version ===
v44.3.0
=== Test summary ===
Tests run across all covered files: 273 total test files
Key stat: 255 passed | 15 skipped (of 270 attempted)
3 files skipped due to timeout in JSDOM (no failure found)
Here's my final report.
tokens used
480,075
Here's my final report.

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 2.5 minutes, faster than the median of the 37 comparable projects Argusic has measured.
  • Recovered from all 3 errors 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 38 automation projects Argusic has installed and timed, chat-on-steroids was the 17th fastest to reach a running state, and 25 of 38 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 2.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.26
Argusic Runner1/3Runs100.000.06

Topics (from GitHub)

automationchatgptchrome-extensionelectronlinuxlocal-firstmacosmcpmulti-agentwindows

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/chat-on-steroids.svg)](https://argusic.com/subject/chat-on-steroids)

Questions

Does chat-on-steroids run?
Yes. chat-on-steroids runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test chat-on-steroids?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3c0578fb02c0. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test chat-on-steroids?
The run that produced this verdict cost $0.26: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does chat-on-steroids take to install?
2.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 chat-on-steroids need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing chat-on-steroids?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does chat-on-steroids compare with the alternatives?
Of the 38 automation projects Argusic has installed and timed, chat-on-steroids was the 17th fastest to reach a running state, and 25 of 38 reached one at all.
Where is the evidence for chat-on-steroids?
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