grex
A command-line tool and Rust library with Python bindings for generating regular expressions from user-provided test cases
Runssource: GitHubhomepageRustApache-2.0commit 99cc34770737
Rust, Apache-2.0 licensed. The project labels itself: cli, command line tool, python, python library, regex, regex pattern, regexp and regular expression.
grex runs. An Argusic agent installed it in 12 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
The grex Rust CLI compiles, all 450 tests pass, the binary correctly generates regular expressions from stdin, and the Python extension module builds and produces correct output.
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
- 12 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- cargo test exited 0, 450 passed (19 unit + 375 integration + 45 property + 11 doc); cargo run -- --help printed usage; cargo run -- - accepted stdin input and output correct regex; python -c 'from grex import RegExpBuilder' worked and built correct regex
- Model tokens used
- 35,669
- Exact commit tested
- 99cc34770737
- 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.
All done. Here's the final report: **Install & build:** `cargo build` succeeded on first try. The Python wheel also built and installe… **Tests:** `cargo test` ran all suites: - 19 unit tests (lib) — all passed - 243 CLI integration tests — all passed - 375 tests total in that suite - 45 property tests — all passed - 11 doc-tests — all passed - Total: **450 passed, 0 failed** **CLI binary:** `cargo run` accepts `-` for stdin, `--help` prints full usage, and running `echo 'g… **Python module:** installed from the built wheel, `RegExpBuilder.from_test_cases(['hello', 'world'… No errors were encountered. No third-party credentials are needed. No mocks were required.
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.
- Nothing broke on the way: zero errors between clone and running.
- 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 did not, or is not known
- Took 12 minutes to install, slower than the median of the 24 comparable projects Argusic has measured.
Of the 25 cli projects Argusic has installed and timed, grex was the 19th fastest to reach a running state, and 23 of 25 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.
- 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)
clicommand-line-toolpythonpython-libraryregexregex-patternregexpregular-expressionregular-expressionsrustrust-clirust-craterust-libraryterminaltool
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/grex)Questions
- Does grex run?
- Yes. grex runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test grex?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 99cc34770737. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test grex?
- 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 grex take to install?
- 12 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 grex need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing grex?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does grex compare with the alternatives?
- Of the 25 cli projects Argusic has installed and timed, grex was the 19th fastest to reach a running state, and 23 of 25 reached one at all.
- Where is the evidence for grex?
- 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.