eve

The Open Framework for Building Agents

Runssource: GitHubhomepageTypeScriptApache-2.0commit a7b0fb2bf24d

TypeScript, Apache-2.0 licensed. The project labels itself: agent, framework, harness, javascript, markdown, sandbox, typescript and vercel.

eve runs. An Argusic agent installed it in 2 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 eve framework monorepo is fully installed, built, and tested: 8726 unit tests and all integration tests pass, the eve CLI binary responds to --help and --version, and the core package typechecks correctly.

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.06 (measured)
recorded runs
2
last tested
stars
5,919
forks
659
open issues
932
watchers
19
size
152 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.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • pnpm typecheck workspace-wide exited 137 (OOM) — container ran out of memory with 51 concurrent tsc processes
Install time
2 minutes
Cold machine to finish
9 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
pnpm test:unit passed (807 files, 8726 passed, 1 skipped); pnpm test:integration passed (all 4 packages); eve --version printed 0.68.0
Model tokens used
49,408
Exact commit tested
a7b0fb2bf24d
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.

**CLI** — `eve --help` prints usage, `eve --version` prints `0.68.0`
**Typecheck** — core `eve` package passes standalone (`tsc --noEmit`); workspace-wide run exited 13…
tokens used
49,408
Typecheck of the core `eve` package passes when run alone. The earlier workspace-wide failure was e…
Let me construct the final report.
**Install** — `pnpm install` (2383 packages, no errors)
**Build** — `pnpm build` (4 packages, all successful)
**Unit tests** — 807 files, 8726 passed, 1 skipped (0 failures)
**Integration tests** — all passed across eve, @eve/code, @eve/catalog, @eve/buzz-acp-adapter
**CLI** — `eve --help` prints usage, `eve --version` prints `0.68.0`
**Typecheck** — core `eve` package passes standalone (`tsc --noEmit`); workspace-wide run exited 13…

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 minutes, faster than the median of the 137 comparable projects Argusic has measured.
  • 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.

Of the 138 agent projects Argusic has installed and timed, eve was the 29th fastest to reach a running state, and 92 of 138 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 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.06
Argusic Runner1/3Runs100.000.07

Topics (from GitHub)

agentframeworkharnessjavascriptmarkdownsandboxtypescriptvercelworkflows

Embed the badge

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

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

Questions

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