The review
What it does
Burrow lives in your terminal and works through coding tasks step by step: reading files, proposing edits, running tests. Commands are sorted into safe, cautious and destructive, and anything in the last group (deleting files, force-pushing, dropping tables) requires you to type yes. It writes a short receipt of what it changed at the end of every session.
Why we like it
It's open-source, runs with whichever model provider you configure and has the most sensible default permissions we've seen in a terminal agent. The receipt at the end of each run makes code review much easier, and the plan file it keeps in the repo means you can stop on Tuesday and resume on Thursday without re-explaining everything.
Watch out for
- Setup assumes you're comfortable with config files and API keys.
- On large monorepos it can spend a lot of tokens just reading. Point it at a folder.
- Community plugins vary wildly in quality; stick to the maintained ones.
