terragrunt
Terragrunt is a flexible orchestration tool that allows Infrastructure as Code written in OpenTofu/Terraform to scale.
Runssource: GitHubhomepageGoMITcommit 65dc2de2690c
Go, MIT licensed. The project labels itself: aws, cli, developer tools, devops, opentofu and terraform.
terragrunt 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.
Terragrunt v1.1.4 builds from source, the `terragrunt --version` and `--help` commands work, all 49 internal/ and pkg/ unit test packages pass, and catalog/scaffold integration tests pass.
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 96 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
- 13 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- Model tokens used
- 161,211
- Exact commit tested
- 65dc2de2690c
- Container image
- sha256:4c3d41857be3
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.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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
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 2, 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.
Let me now also see if we can run the `go vet` on the project to check for any issues: exec /bin/sh -lc 'export GOROOT=/home/runner/go export GOPATH=/home/runner/gopath export PATH=/home/runner/go/bin:$GOPATH/bin:$PATH cd /work/repo go vet ./... 2>&1 | tail -30' in /work/repo succeeded in 45378ms: `go vet ./...` passes cleanly too. Let me record the final state and output. tokens used 161,211 `go vet ./...` passes cleanly too. Let me record the final state and output.
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 12 minutes.
- 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.
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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.06 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.05 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/terragrunt)Questions
- Does terragrunt run?
- Yes. terragrunt 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 terragrunt?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 65dc2de2690c. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test terragrunt?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does terragrunt 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 terragrunt need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing terragrunt?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for terragrunt?
- 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.