Abbreviatory turns a test run, a log or a JSON response into a short report. Failures, errors and warnings first, repeats folded into one line, all within a byte budget. Everything it leaves out stays one command away. No language model, no network.
0.05%
A 5.6 MB log of 63,369 lines reduced to a 3,075-byte report
1,500 of 1,500
Simulated CI runs where the reported new, fixed, still failing and flaky tests matched the known ones exactly
10.9 MB
Peak memory while a 1,107 MB log of 12.5 million lines streamed through
105 tests
Go tests passing, with the race detector finding nothing
From the test suite of v0.6.0, recorded on a Linux machine with an Intel Xeon at 2.30GHz and 2 CPUs. The result files are in the code repository under test/results.
release
After tests, the thing a coding agent reads most is a build failing. cargo build, tsc, npm install, mvn test. Until now Abbreviatory read those as logs. It found the …
release
Warnings pile up. A build has forty of them, everyone stopped reading them months ago, and the one that matters, the deprecation that turns into an error next quarter, …
release
Coding agents run tests all day. Every run prints thousands of lines, and the agent reads all of them, pays for all of them, and then often reads them again after a …
release
Test runs and logs aren’t the only big outputs a coding agent reads. It reads diffs all day, to review what it changed. It calls APIs with curl and gets back a wall …
case studies
Something went wrong overnight and the service log is 5.6 MB: 63,369 lines. Most of them are cache hits and request logs. Somewhere in there are the errors, each one …
case studies
A coding agent fixing a bug runs the tests again and again. Change a line, run go test ./..., read the output, change another line. Each run of our sample suite prints …
case studies
The first thing anyone does in a new repository is look around. A person runs tree and gives up after a few screens. A coding agent runs find . -type f and gets every …
case studies
Reviewing a big change starts with a question the diff doesn’t answer up front: what’s in here? git diff prints the first file’s first hunk and makes …
case studies
A red build on GitHub Actions usually means scrolling. The job log holds thousands of lines, the failures are somewhere in the middle, and the first question is always …
Download the binary and pipe a test run or a log through abbreviatory reduce. Questions, bug reports and formats it should read are welcome.