codejar

An embeddable code editor for the browser 🍯

Runssource: GitHubhomepageTypeScriptMITcommit 32f7a803cccb

TypeScript, MIT licensed. The project labels itself: code editor.

codejar runs. An Argusic agent installed it in 1.5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Build succeeds (tsc exits 0, produces dist/codejar.js + dist/cursor.js + .d.ts). The CodeJar editor works in a headless Chromium browser: initializes with contenteditable='plaintext-only', updateCode and toString function correctly, cursor module exports cursorPosition, selectedText, textAfterCursor, textBeforeCursor.

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.07 (measured)
recorded runs
2
last tested
stars
1,989
forks
126
open issues
18
watchers
17
size
0 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.

Install time
2 minutes
Cold machine to finish
6 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
node test-verify.cjs (puppeteer + Chromium): CodeJar init PASS, updateCode('const x = 42;') PASS, toString()='const x = 42;' PASS, contenteditable='plaintext-only' PASS, cursor module exports [cursorPosition,selectedText,textAfterCursor,textBeforeCursor] PASS
Model tokens used
75,216
Exact commit tested
32f7a803cccb
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.

Here's the full journey:
1. **Install** (`npm install`): 556 packages, completed with only minor deprecation warnings (no er…
2. **Build** (`npm run build` / `tsc`): completed with zero errors, produces `dist/codejar.js`, `di…
3. **Runtime verification**: Launched a headless Chromium 112 via puppeteer with a custom HTTP serv…
4. **No issues found**: The tsconfig.json has a trailing comma (invalid strict JSON) but tsc handle…
tokens used
75,216
Here's the full journey:
1. **Install** (`npm install`): 556 packages, completed with only minor deprecation warnings (no er…
2. **Build** (`npm run build` / `tsc`): completed with zero errors, produces `dist/codejar.js`, `di…
3. **Runtime verification**: Launched a headless Chromium 112 via puppeteer with a custom HTTP serv…
4. **No issues found**: The tsconfig.json has a trailing comma (invalid strict JSON) but tsc handle…

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 11 comparable projects Argusic has measured.
  • Nothing broke on the way: zero errors between clone and running.
  • 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 12 code-editor projects Argusic has installed and timed, codejar was the 4th fastest to reach a running state, and 11 of 12 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.
  • Following its own README: the documented path worked with nothing to fix.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks92.000.04
Argusic Runner1/3Runs100.000.07

Topics (from GitHub)

code-editor

Embed the badge

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

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

Questions

Does codejar run?
Yes. codejar runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test codejar?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 32f7a803cccb. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test codejar?
The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does codejar 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 codejar need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing codejar?
Nothing did, in the recorded run: zero errors between clone and running.
How does codejar compare with the alternatives?
Of the 12 code-editor projects Argusic has installed and timed, codejar was the 4th fastest to reach a running state, and 11 of 12 reached one at all.
Where is the evidence for codejar?
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