mongo-ruby-driver
The Official MongoDB Ruby Driver
Runssource: GitHubhomepageRubyApache-2.0commit 6375dc607da5
Ruby, Apache-2.0 licensed. The project labels itself: mongodb, mongodb driver, nosql, ruby and ruby on rails.
mongo-ruby-driver runs. An Argusic agent installed it in 18 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Ruby 3.2.6 compiled from source with psych and zlib support, all 41 gem dependencies installed via bundler, MongoDB 8.0.0 server running on localhost:27017, test users created, and 6535 unit tests execute with only 11 pre-existing failures (all timeout-sensitive or container-detection tests)
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.
- Ruby 3.2.6 not installed in container8 minutes
- libyaml missing - psych gem (required by RubyGems) couldn't load3 minutes
- Ruby compiled with --with-static-linked-ext caused segfault in bigdecimal3 minutes
- zlib missing - bundler install failed without zlib2 minutes
- git submodules not initialized (spec/shared)1 minute
- MongoDB not running - test suite requires a running deployment1 minute
- Install time
- 18 minutes
- Cold machine to finish
- 28 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- bundle exec rspec spec/mongo/collection_spec.rb: 55 examples, 0 failures, 9 pending. Full unit suite (spec/mongo/ --tag ~integration): 6535 examples, 11 failures (8 timing-sensitive timeout tests, 2 container/FaaS detection tests, 1 write concern error test), 1396 pending. All failures are environment-expected (container detection, timing sensitivity on standalone mongod).
- Model tokens used
- 96,477
- Exact commit tested
- 6375dc607da5
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
index_spec.rb: 0 examples, 0 failures, 1 error occurred outside of examples query_spec.rb: 0 examples, 0 failures, 1 error occurred outside of examples The only real failures are in `client_spec.rb` (the 8 timeout-related tests we saw earlier). Let me… 2026-11-15T10:47:15.223517Z ERROR codex_core::tools::router: error=exec_command failed: CreateProce… exec /bin/sh -lc 'kill $(pgrep mongod) 2>/dev/null; sleep 1; echo "done"' in /work/repo succeeded in 860ms: done Here is the complete report. tokens used 96,477 Here is the complete 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 18 minutes.
- Recovered from all 7 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.
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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mongo-ruby-driver)Questions
- Does mongo-ruby-driver run?
- Yes. mongo-ruby-driver runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test mongo-ruby-driver?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6375dc607da5. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test mongo-ruby-driver?
- The run that produced this verdict cost $0.23: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mongo-ruby-driver take to install?
- 18 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 mongo-ruby-driver need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mongo-ruby-driver?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for mongo-ruby-driver?
- 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.