openclacky

The Most Token-Efficient Lightweight AI Agent

Could not verifysource: GitHubhomepageRubyMITcommit 261aabd59d76

Ruby, MIT licensed. The project labels itself: agent, agent framework and skills.

Argusic could not get openclacky running. An Argusic agent installed it in 1.5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Ruby 3.2.4 installed via mise; 70 gem dependencies installed; openclacky-1.5.16 built; CLI help and server start both work; test suite runs 4632 examples with 2 env-specific 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 80 of 100 (the mean of this project's run scores).

At a glance

verdict
Could not verify
Argusic Score
80 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
2
last tested
stars
1,209
forks
114
open issues
26
watchers
6
size
14 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.

Time lost to each failure while testing openclacky, 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.

  • Ruby not installed — had to install via mise0.5 minutes
  • 2 test failures: IPv6 loopback unavailable (container), scripts path check (running from repo source)
Install time
2 minutes
Cold machine to finish
4 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
bundle exec rspec -- 4632 examples, 2 failures, 1 pending; bundle exec ruby bin/openclacky --help returned command list; bundle exec ruby bin/openclacky server --port 7071 printed banner and Web UI URL http://127.0.0.1:7071
Model tokens used
40,399
Exact commit tested
261aabd59d76
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
Whether it works at all
this run verified nothing, so this page makes no claim either way

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

Everything works. Let me compile the final report.
**Install**: Ruby not pre-installed — installed via `mise` (Ruby 3.2.4), then `bundle install` comp…
**Launch**: CLI help (`openclacky --help`) lists all commands. Server starts on port 7071 with bann…
**Tests**: 4632 examples, 2 failures (both container-specific: IPv6 unavailable, and scripts path c…
**Verification**: `bundle exec ruby bin/openclacky --help` returned all commands; `bundle exec ruby…
tokens used
40,399
Everything works. Let me compile the final report.
**Install**: Ruby not pre-installed — installed via `mise` (Ruby 3.2.4), then `bundle install` comp…
**Launch**: CLI help (`openclacky --help`) lists all commands. Server starts on port 7071 with bann…
**Tests**: 4632 examples, 2 failures (both container-specific: IPv6 unavailable, and scripts path c…
**Verification**: `bundle exec ruby bin/openclacky --help` returned all commands; `bundle exec ruby…

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

  • Installed in 1.5 minutes, faster than the median of the 140 comparable projects Argusic has measured.
  • Recovered from all 2 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

  • An agent with no time limit did not get it running.

Of the 141 agent projects Argusic has installed and timed, openclacky was the 28th fastest to reach a running state, and 94 of 141 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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Ran out of time0.000.22
Argusic Runner1/3Unverified80.000.02

Topics (from GitHub)

agentagent-frameworkskills

Embed the badge

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

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

Questions

Does openclacky run?
Argusic could not verify that openclacky runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test openclacky?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 261aabd59d76. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test openclacky?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does openclacky take to install?
1.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 openclacky need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing openclacky?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does openclacky compare with the alternatives?
Of the 141 agent projects Argusic has installed and timed, openclacky was the 28th fastest to reach a running state, and 94 of 141 reached one at all.
Where is the evidence for openclacky?
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