https://abbreviatory.com/tags/coding-agents/ Recent content in coding agents on Abbreviatory.com Hugo -- gohugo.io en-us Mon, 19 Oct 2026 00:00:00 +0000 https://abbreviatory.com/abbreviatory-0.3-gives-coding-agents-an-mcp-server-and-opens-a-browser-demo/ Mon, 19 Oct 2026 00:00:00 +0000 https://abbreviatory.com/abbreviatory-0.3-gives-coding-agents-an-mcp-server-and-opens-a-browser-demo/ 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 one-line change. Abbreviatory v0.3.0 lets the agent skip that. It’s now an MCP server, so an agent can ask it to run the tests and get back the short report instead: the failures with their messages, what changed since the last run, and one line when nothing did. https://abbreviatory.com/how-to-give-a-coding-agent-short-test-reports-through-the-abbreviatory-mcp-server/ Mon, 19 Oct 2026 00:00:00 +0000 https://abbreviatory.com/how-to-give-a-coding-agent-short-test-reports-through-the-abbreviatory-mcp-server/ 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 4,882 lines of go test -json events, 808 kB, and almost all of it says a test passed. The agent reads every line, every time, and pays for every line in its context window. By the tenth run most of its context is old test output. https://abbreviatory.com/how-to-map-an-unfamiliar-repository-with-find-and-abbreviatory/ Mon, 19 Oct 2026 00:00:00 +0000 https://abbreviatory.com/how-to-map-an-unfamiliar-repository-with-find-and-abbreviatory/ 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 path, and on a large project that’s thousands of lines spent before it has read a single file. Most of them say the same thing: another test fixture, another Go file in the same package. The listing in this example is find src -type f over Go’s own source tree, which is big enough to make the point: 10,703 paths in 1,097 directories, 454. https://abbreviatory.com/what-context-reduction-is-and-why-abbreviatory-does-it-without-a-language-model/ Sun, 18 Oct 2026 00:00:00 +0000 https://abbreviatory.com/what-context-reduction-is-and-why-abbreviatory-does-it-without-a-language-model/ Context is whatever a reader has in front of them when they decide what to do next. For a person, it’s the terminal. For a coding agent, it’s the text that goes into the model on its next turn. Either way it’s limited, and most of what tools print is filler. Context reduction is cutting that down before it reaches the reader, without losing anything they need. A test run of 5,000 lines, of which 4,950 say “ok”, becomes the 50 that don’t, plus a count of the rest.