bevy
A refreshingly simple data-driven game engine built in Rust
Runssource: GitHubhomepageRustApache-2.0commit cfeaeda7bff1
Rust, Apache-2.0 licensed. The project labels itself: bevy, game development, game engine, gamedev, open source and rust.
bevy runs. An Argusic agent installed it in 5 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Bevy 0.20.0-dev builds from source on Linux x86_64, the headless example runs (prints 'hello world' and frame counter), and all core library unit tests pass (2053 tests, 0 failures).
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 60 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.
- wayland-sys build failed: pkg-config could not find wayland-client.pc (missing libwayland-dev)2 minutes
- 16 bevy_ecs should_panic tests failed when debug feature was not enabled (expected parameter names but got error codes)2 minutes
- Linker failed: unable to find -lwayland-client (no .so symlinks for the dev libraries)1 minute
- winit compilation error: 'The platform you are compiling for is not supported by winit' (neither x11 nor wayland features enabled)1 minute
- headless example panicked: 'ScheduleRunnerPlugin does not exist in this PluginGroup'1 minute
- Install time
- 5 minutes
- Cold machine to finish
- 39 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- cargo run --example headless --no-default-features -F bevy_log printed 'hello world' and frame counter output; cargo test with -F debug on bevy_ecs (978 passed), bevy_app (489 passed), bevy_reflect (265 passed), bevy_math (54 passed), bevy_utils (54 passed), bevy_state (82 passed), bevy_color (37 passed), bevy_time (47 passed), bevy_ptr (25 passed), bevy_log (22 passed), all 0 failed
- Model tokens used
- 468,164
- Exact commit tested
- cfeaeda7bff1
- 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.
bevy_log: 22 passed bevy_ptr: 25 passed All core tests pass (978 + 489 + 265 + 54 + 54 + 82 + 37 + 47 + 22 + 25 = 2053 tests) and the headl… ```json ``` 2026-09-25T12:15:06.559677Z ERROR codex_core::session: failed to record rollout items: thread 01a0d… 2026-09-25T12:15:06.559928Z ERROR codex_core::session: failed to record rollout items: thread 01a0d… tokens used 468,164 All core tests pass (978 + 489 + 265 + 54 + 54 + 82 + 37 + 47 + 22 + 25 = 2053 tests) and the headl… ```json ```
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 5 minutes.
- 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 Apache-2.0, 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.
- A quick evaluation: it was running 5 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 | 2/3 | Runs | 100.00 | 0.12 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.22 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/bevy)Questions
- Does bevy run?
- Yes. bevy runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test bevy?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit cfeaeda7bff1. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test bevy?
- The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does bevy take to install?
- 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 bevy need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing bevy?
- 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 bevy?
- 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.