bandicot

Sharper, smaller tool results

Command output keeps the error buried in the middle, searches skip what your project ignores, and long files are read in one clean stretch.

Engine

When a command prints a long log, the agent used to see only its first and last fifty lines, so an error in the middle could be missed. It now also sees the lines that look like errors or failures, each kind once. Colour codes, progress bars that redraw themselves and lines repeated over and over are tidied away before the agent reads the output, which saves a large share of what a noisy build prints. A command that never stops printing now stops on time and when you press Stop.

Searching and reading

Searches across a project leave out what the project's ignore files exclude, such as build folders and old copies, so the matches that come back are the ones that matter. If nothing matches exactly and the agent wrote a search pattern, such as a word followed by any digits, the search runs it as a pattern, then tries again ignoring upper and lower case, and says which one found the results. Finding files understands a choice of endings and any folder depth, so a request for every TypeScript file finds the ones at the top of the project too. A very long line no longer fills a whole result. Reading a long file now gives one continuous stretch and says exactly where to carry on, and an edit still works when the agent copies text along with the line numbers it was shown.