tesla
The flexible HTTP client library for Elixir, with support for middleware and multiple adapters.
Runssource: GitHubElixirMITcommit f1d040b237cf
Elixir, MIT licensed. The project labels itself: elixir, hackney, http, http client, ibrowse, json and middleware.
tesla runs. An Argusic agent installed it in 13 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Elixir 1.19.6 with Erlang/OTP 28.5.0.7 installed via asdf, tesla deps fetched, project compiled, and full test suite (1235 tests + 24 doctests) passes with 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 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.
- Elixir/Erlang not installed in container5 minutes
- Erlang build requires ncurses-dev (curses functions not found)3 minutes
- unzip command not found for Elixir precompiled zip1 minute
- .tool-versions had imprecise versions (1.19-otp-28, 28.5) vs installed (1.19.6-otp-28, 28.5.0.7)1 minute
- Install time
- 13 minutes
- Cold machine to finish
- 15 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- mix test --no-compile exited 0, 1235 tests + 24 doctests passed, 0 failures, in ~55s
- Model tokens used
- 67,654
- Exact commit tested
- f1d040b237cf
- 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.
3. `unzip` binary not found → extracted Elixir zip using Python instead 4. `.tool-versions` used imprecise version strings → updated to exact installed versions tokens used 67,654 Here's the final report for the Tesla HTTP client library: **Install:** Elixir and Erlang were not present in the container. Installed via asdf: Erlang 28.5.0… **Test suite:** 1235 tests + 24 doctests, 0 failures. Tests exercise real HTTP interactions against… **Errors encountered and fixed:** 1. No Elixir/Erlang runtime in container → installed via asdf 2. Erlang build failed on missing ncurses headers → added `--without-termcap` and other feature fla… 3. `unzip` binary not found → extracted Elixir zip using Python instead 4. `.tool-versions` used imprecise version strings → updated to exact installed versions
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 13 minutes.
- Recovered from all 4 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 MIT, 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.
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/tesla)Questions
- Does tesla run?
- Yes. tesla runs. Argusic installed and launched it on a clean machine in 13 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test tesla?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f1d040b237cf. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test tesla?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does tesla take to install?
- 13 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 tesla need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing tesla?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for tesla?
- 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.