amber
A code search / replace tool
Runssource: GitHubRustMITcommit a6d54a5957f6
Rust, MIT licensed. The project labels itself: command line tool, grep, replace text, rust and search.
amber runs. An Argusic agent installed it in 2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
The amber code search and replace tool compiles, passes all 9 unit tests, and both ambs (search) and ambr (replace) binaries work correctly including regex captures in replacements.
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.
- Install time
- 2 minutes
- Cold machine to finish
- 2 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- cargo test exited 0, 9 passed; ambs --help printed usage and version 0.6.1; ambr --help printed usage; ambs searched 'hello' in a test file and returned matching line; ambr --no-interactive replaced 'hello' with 'goodbye' and the file contained 'goodbye world'; ambr with --regex captured groups and expanded ${1}/${pat} correctly matching the README example
- Model tokens used
- 29,693
- Exact commit tested
- a6d54a5957f6
- 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.
--> Cargo.toml:48:1
|
48 | time = "0.3"
| ^^^^^^^^^^^^^^^^^^^^^
|
help: consider removing the dependency on `time`
warning: `amber` (manifest) generated 3 warnings
Finished `release` profile [optimized] target(s) in 25.75s
Everything builds and works perfectly. Let me compile the final report.
tokens used
29,693
Everything builds and works perfectly. Let me compile the final 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 2 minutes, faster than the median of the 12 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
Of the 13 command-line-tool projects Argusic has installed and timed, amber was the 3rd fastest to reach a running state, and 12 of 13 reached one at all.
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 2 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
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/amber)Questions
- Does amber run?
- Yes. amber runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test amber?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a6d54a5957f6. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test amber?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does amber take to install?
- 2 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 amber need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing amber?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does amber compare with the alternatives?
- Of the 13 command-line-tool projects Argusic has installed and timed, amber was the 3rd fastest to reach a running state, and 12 of 13 reached one at all.
- Where is the evidence for amber?
- 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.