Yes. encore runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 5 errors on the way, and recorded the session.

How did Argusic test encore?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 13dfbf46f262. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test encore?

The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does encore take to install?

1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.

Does encore need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing encore?

5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for encore?

The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

encore

The infrastructure platform for the intelligence era

Runssource: GitHub homepageGoMPL-2.0commit 13dfbf46f262

Go, MPL-2.0 licensed. The project labels itself: aws, backend, cloud, cloud native, database, devops, devops automation and distributed systems.

encore runs. An Argusic agent installed it in 1 minute and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Encore CLI v1.58.6 installed, a sample Go app runs with the dev server and dashboard; Rust workspace (miniredis, tsparser, supervisor) compiles and tests pass (65 passed); Go CLI builds from source; three preexisting test gaps remain in clientgen golden files, compiler/build requiring Encore's patched Go runtime, and Rust build requiring manual LLVM+protoc setup. Go build and Rust build succeeded
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.17 (measured)
recorded runs: 1
last tested: 2026-09-26
stars: 12,389
forks: 625
open issues: 128
watchers: 67
size: 18 MB
created: 2021-02-17
last push: 2026-09-23

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-26. 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 encore, 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.

Missing libclang for Rust bindgen crate; LLVM 18 requires libtinfo.so.5 which is absent10 minutes
Rust bindgen can't find stddef.h via LLVM 17's clang5 minutes
Missing protoc for Rust prost-build crate3 minutes
Go test pkg/clientgen fails: whitespace (tab vs space) diffs in generated Go client code golden files
Go test v2/compiler/build fails: runtime.exitEncoreG / runtime.startEncoreG relocation targets not defined

Install time: 1 minutes
Cold machine to finish: 45 minutes
Errors hit and fixed: 5 hit, 5 fixed with no human help
How the result was proved: encore run --port=4099 started dev server on 127.0.0.1:4099 with dashboard returning HTTP 200 on 127.0.0.1:9400; go build ./cli/cmd/encore produced binary reporting version v0.0.0-develop+13dfbf46; cargo test --lib passed 65/65; go test ./cli/... ./internal/... all passed (many ok+no test files); Rust cargo check and cargo test passed
Model tokens used: 571,284
Exact commit tested: 13dfbf46f262
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.

encore: Starting Encore application...
encore: Starting Encore application done (50ms)
  Encore development server running!
Let me compile the final results
exec
/bin/sh -lc 'echo "Elapsed seconds: $(( $(date +%s) - $(date -d '"'2026-09-26 22:15:00' +%s) ))\"" …
 succeeded in 0ms:
Elapsed seconds: 2711
Now I have all the data I need. Here's the final report:
tokens used
571,284
Now I have all the data I need. Here's 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 1 minute.
Recovered from all 5 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 MPL-2.0, as reported by its host.

What did not, or is not known

Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 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 by	attempt	outcome	score	cost USD	when
Argusic Runner	1/3	Runs	100.00	0.17	2026-09-26 23:00 UTC

Topics (from GitHub)

aws backend cloud cloud-native database devops devops-automation distributed-systems encore gcp go golang infrastructure-as-code infrastructure-automation microservices serverless typescript

Embed the badge

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

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

Questions

Does encore run?: Yes. encore runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test encore?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 13dfbf46f262. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test encore?: The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does encore take to install?: 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does encore need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing encore?: 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for encore?: The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.