Who it is forA developer who wants to check what an agent edited in a repository before committing or continuing.
The problemReviewing changes means switching to a terminal or editor and risks changing files by accident.
The outcomeYou open the file browser, pick a working-tree, staged or commit comparison and read each file's diff in read-only mode.
What you need first
- A computer with herdr 0.9.0 or newer, Bun 1.4 or newer and Node 18 or newer (Node is not needed on Windows)
- Git, curl and tar on Linux or macOS, or Git for Windows on Windows x64
- A herdr pane running Claude Code, Codex or another supported agent
- Optional: Tailscale on the computer and your phone for access away from your desk
Steps
- Install Ovis with
herdr plugin install devswha/ovisor the install command for your system. - Open the address [127.0.0.1:7317](http://127.0.0.1:7317) in your browser.
- Select the workspace that contains the repository.
- Open the file browser and choose a working-tree, staged or commit comparison.
- Open each changed file to read its diff.
Prompt for your agent
Using the devswha/ovis repo, open the repository diff view for <target repo path> in Ovis and list each changed file for the working tree. Confirm the repository has no changes after viewing, and report the file count.
Caveat. The README describes read-only diffs for files herdr can reach, so repositories outside a herdr workspace may not appear.
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page