Async
IDE, A native-feeling AI coding workspace that blends chat, planning, agent execution, and project navigation into a unified desktop experience.
Runssource: GitHubTypeScriptApache-2.0commit 2c18a43c0711
TypeScript, Apache-2.0 licensed. The project labels itself: ai coding assistant, ai development tools, code editor, cursor alternative, electron, llm, reactjs and typescript.
Async runs. An Argusic agent installed it in 8.7 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install completes, full build (typecheck + esbuild + vite) succeeds, all 117 test files (709 tests) pass, and the Electron app starts with the dist bundle rendering the agent window via did-finish-load.
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
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.
- scripts/sync-builtin-team-repo.mjs exits with code 1 when external 'agency-agents' repo is missing (blocking `npm run build`)1 minute
- Install time
- 9 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm test exited 0 (117 files, 709 passed); ASYNC_SHELL_LOAD_DIST=1 electron . --no-sandbox started and showed 'showing main window via did-finish-load'
- Model tokens used
- 61,881
- Exact commit tested
- 2c18a43c0711
- 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.
- `npm run build` — typecheck + esbuild + vite build succeeded (with `ASYNC_BUILTIN_TEAM_SOURCE` en… - `ASYNC_SHELL_LOAD_DIST=1 electron . --no-sandbox` — Main process started, window loaded via `did-… One fixable error encountered: the `sync:builtin-team` script `process.exit(1)` when the optional `… tokens used 61,881 Now let me compile the final result. **Timeline (elapsed ~8.7 min from start to verification):** - `npm install` — 848 packages installed, no errors - `npm test` — 117 test files, 709 tests, all passed - `npm run build` — typecheck + esbuild + vite build succeeded (with `ASYNC_BUILTIN_TEAM_SOURCE` en… - `ASYNC_SHELL_LOAD_DIST=1 electron . --no-sandbox` — Main process started, window loaded via `did-… One fixable error encountered: the `sync:builtin-team` script `process.exit(1)` when the optional `…
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.
- 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 Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 8.7 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
Of the 4 ai-coding-assistant projects Argusic has installed and timed, Async was the 3rd fastest to reach a running state, and 4 of 4 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 8.7 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
Topics (from GitHub)
ai-coding-assistantai-development-toolscode-editorcursor-alternativeelectronllmreactjstypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/async)Questions
- Does Async run?
- Yes. Async runs. Argusic installed and launched it on a clean machine in 9 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test Async?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2c18a43c0711. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Async?
- 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 Async take to install?
- 8.7 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 Async need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Async?
- 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 Async compare with the alternatives?
- Of the 4 ai-coding-assistant projects Argusic has installed and timed, Async was the 3rd fastest to reach a running state, and 4 of 4 reached one at all.
- Where is the evidence for Async?
- 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.