Eric D. Schabell: Terry: A Live File Tree and Review Gate for Claude Code

Wednesday, November 18, 2026

Terry: A Live File Tree and Review Gate for Claude Code

Terry: see every file Claude changes, right beside the chat

[ Today I’m handing the keyboard to a friend. Henry is an enthusiastic newcomer to the open source ecosystem and jumped right in with his first project. He's built a small open source tool called Terry that sits beside Claude Code and shows you every file the agent touches. If you let an AI agent edit your repo, you know how easy it is to lose the thread by turn nine. Terry’s answer is a live file tree and one firm rule: nothing gets committed until you’ve read the diff. It’s a single Rust binary and a thin plugin, which I appreciate in a tool that does this much. Over to Henry and welcome to our community! -- Eric D. Schabell]

A live file tree for Claude Code, with diff review before anything ships.

Why I built it

I kept a full IDE open for one job: to look at code changes. I did not use its editor or its refactoring tools. The agent did that work. So I paid for a whole cockpit and used one dial.

I wanted that dial beside the chat, and nothing else. I also wanted the agent to drive git, with one rule: no change reaches a branch or a PR before I read it. I will be honest with you: this one is non-negotiable for me.

Terry is the result. 

Note that the file tree comes first and the review gate comes second. All screenshots in this article come from a small demo repo in a Linux terminal.

The file tree

An AI agent edits many files, fast. The chat scrolls, and by turn nine you forget what happened in turn three. Let's take a look at terry, which offers a simple, lightweight solution: a pane that stays open beside the chat and lists every file in the repo.

Here is the pane in the demo repo. Every status is on screen at once.

The terry file tree beside Claude Code, showing added, modified, deleted and untracked files and the branch chain
  • Color and letter show the status. Green A is added, yellow M is modified, red D is deleted, and cyan ? is untracked.
  • A ✎ shows who. It marks a file that the agent edited. A · marks a file that you changed.
  • Orange shows where the agent is now. The top bar names the file it edits.
  • Bold or dim shows the commit state. Bold is not committed. Dim is in a commit.
  • A click opens the diff of a changed file.

Now the agent edits src/utils.py. Notice how the top bar names the file, and the tree marks it with a ✎, while the edit waits for permission.

Claude Code asking permission to edit src/utils.py, with the terry top bar reading Claude is editing utils.py

The tree also shows the branch chain, such as main -> dev -> feature/login.

The review gate

Now the second piece. When the agent tries to commit or open a PR, terry stops the command. A pane opens with the full diff. You press Approve or Reject, and the agent waits. An approval works once, for one exact diff.

The terry Diff review pane with Approve and Reject buttons, the git commit command and the diff

terry also lints the lines that the change adds. If lint fails, the agent fixes the problems before you see the diff. You review only code that passes.

Here the commit holds a file with lint problems. terry denies the commit and lists each problem.

terry denying a commit because lint found problems, with the list of ruff findings

Then Claude starts a fix. Notice how the fix is an edit that waits for your approval.

terry denying a commit because lint found problems, and Claude Code proposing a fix to src/report.py

Three design choices

The tree reads git, not the chat. It marks every change since the branch last met what is published. A commit that landed stays marked until you push, so nothing falls out of view.

Review in a pane, then the prompt. While Claude Code shows a prompt, a pane gets no keys and no mouse wheel. You cannot scroll a long diff there. So you read the diff in the pane first, and the permission prompt stays as the last check.

One Rust binary and a thin plugin. The binary holds all the logic, with one dependency (serde_json). The pane plugin only draws the panes and asks the binary for every fact.

Try it

# Clone the repo and run the installer.
#
$ git clone https://github.com/hbbaker/terry.git ~/Projects/terry
$ cd ~/Projects/terry
$ ./install.sh

Start a new Claude Code session and run /terry. Ask the agent to edit a file, and watch the tree. Then ask it to make a commit, and read the diff.

What is next

The problem is not special to one agent. Any AI terminal tool that edits files and runs git has it. Our goal is to make the file tree and the review work with more of them, not only Claude Code.

There are also plans to support file drag and drop into the tree, though it is early in development.

If you use another tool and want it supported, open an issue on GitHub. Tell us what you want to see.

Source and docs: github.com/hbbaker/terry Find me on LinkedIn and GitHub.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.