Acode

Acode - powerful text/code editor for android/ios

Runssource: GitHubhomepageJavaScriptMITcommit b7dbe3d69dcf

JavaScript, MIT licensed. The project labels itself: acode, ai editor, android application, code editor and coding.

Acode runs. An Argusic agent installed it in 20 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

npm install succeeds with warnings (EBADENGINE on Node 18 for packages requiring Node 20+, and deprecation notices). The vitest test suite passes: 723 tests across 87 files passing, 0 failures, 1 intentional skip.

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.11 (measured)
recorded runs
2
last tested
stars
7,818
forks
1,747
open issues
97
watchers
218
size
67 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 Acode, 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.

  • vitest 1.x missing `toHaveBeenCalledExactlyOnceWith` matcher3 minutes
  • Submodule codemirror-lsp-client not checked out (empty directory)2 minutes
  • @babel/core v8 is ESM-only and uses Node 20+ syntax (`with`), failing on Node 18.19.12 minutes
  • vitest v4.1.11 requires Node >=20; `node:util` export `styleText` missing on Node 182 minutes
  • Node 18 lacks global `crypto` in happy-dom environment, causing ReferenceError in adRewards tests2 minutes
  • vitest 1.x actionStack async timer test timing was fragile1 minute
Install time
20 minutes
Cold machine to finish
19 minutes
Errors hit and fixed
6 hit, 6 fixed with no human help
How the result was proved
npx vitest run exited 0, 87 test files passed, 723 tests passed, 1 skipped
Model tokens used
514,726
Exact commit tested
b7dbe3d69dcf
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.

 ✓ tests/unit/lspTailwindServer.test.js (1 test) 5ms
 ✓ tests/unit/installSource.test.js (3 tests) 3ms
 ✓ tests/unit/dev.test.js (2 tests) 3ms
 ✓ tests/unit/shell.test.js (3 tests) 5ms
 Test Files  87 passed | 1 skipped (88)
      Tests  723 passed | 1 skipped (724)
   Start at  16:37:07
   Duration  21.85s (transform 2.26s, setup 1.53s, collect 6.93s, tests 16.85s, environment 10.67s,…
All 87 test files pass (723 tests, 1 skipped). Let me now produce the final report.
tokens used
514,726
All 87 test files pass (723 tests, 1 skipped). Let me now produce the 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 20 minutes.
  • Recovered from all 6 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.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

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.11
Argusic Runner1/3Runs100.000.07

Topics (from GitHub)

acodeai-editorandroid-applicationcode-editorcoding

Embed the badge

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

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

Questions

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