ruby-openai
OpenAI API + Ruby! 🤖❤️ GPT-5 & Realtime WebRTC compatible!
Runs with mockssource: GitHubhomepageRubyMITcommit 62938e02bb83
Ruby, MIT licensed. The project labels itself: ai, api client, chatgpt, dall e, gpt 4, gpt 4o, o1 and openai.
ruby-openai runs, with stand-ins for the services it depends on. An Argusic agent installed it in 24 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
ruby-openai gem v8.3.0 builds, loads, passes all 155 RSpec specs and RuboCop linting with zero failures in a container with no pre-installed Ruby.
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 92 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 not installed in container8 minutes
- libyaml not found; psych (YAML) extension failed to build4 minutes
- zlib library missing headers; gem install failed3 minutes
- logger.rb and time.rb stdlib files corrupted by ext/common copy2 minutes
- set.rb overwritten by JSON add-on; Set#add? missing1 minute
- Bundler 4.0.24 incompatible with Gemfile.lock (needs 2.4.5)1 minute
- Install time
- 24 minutes
- Cold machine to finish
- 25 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- bundle exec rspec exited 0: 155 examples, 0 failures; bundle exec rubocop: 57 files inspected, 0 offenses
- Model tokens used
- 269,613
- Exact commit tested
- 62938e02bb83
- 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
- Behaviour against real services
- this run was verified against stand-in services only
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.
**Environment:** Container had no Ruby installed at all. I compiled Ruby 3.2.2 from source (the onl… ### Errors Found and Fixed 1. **No Ruby in container** — Compiled Ruby 3.2.2 from ruby-lang.org source with `./configure --pre… 2. **libyaml missing** — `psych` (YAML extension) failed to build. Built libyaml 0.2.5 from source,… 3. **zlib headers missing** — `gem install` failed because zlib extension couldn't compile. Downloa… 4. **set.rb corrupted** — The initial bulk copy of `.ext/common/*` overwrote `set.rb` with a 29-lin… 5. **logger.rb and time.rb corrupted** — Same root cause. Re-copied all stdlib `.rb` files from the… 6. **Bundler version mismatch** — Gemfile.lock required bundler 2.4.5, but the default was 4.0.24 (… ### Final Verification - **`bundle exec rspec`** — **155 examples, 0 failures** (tests use VCR cassettes + WebMock stubs) - **`bundle exec rubocop`** — **57 files inspected, no offenses** - **Library loads and client instantiates** correctly (returns HTTP 401 as expected without real AP…
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
- Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 24 minutes to install, slower than the median of the 234 comparable projects Argusic has measured.
Of the 235 ai projects Argusic has installed and timed, ruby-openai was the 208th fastest to reach a running state, and 166 of 235 reached one at all.
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 with mocks | 92.00 | 0.15 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.08 |
Topics (from GitHub)
aiapi-clientchatgptdall-egpt-4gpt-4oo1openairailsrubywhisper
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ruby-openai)Questions
- Does ruby-openai run?
- ruby-openai runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 24 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test ruby-openai?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 62938e02bb83. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test ruby-openai?
- The run that produced this verdict cost $0.15: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ruby-openai take to install?
- 24 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 ruby-openai need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ruby-openai?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does ruby-openai compare with the alternatives?
- Of the 235 ai projects Argusic has installed and timed, ruby-openai was the 208th fastest to reach a running state, and 166 of 235 reached one at all.
- Where is the evidence for ruby-openai?
- 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.