Claude Code Filetree plugin
A file tree plugin for Claude Code that highlights the files the agent reads and edits, with git status, diffs and a preview
- 388 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The plugin hooks see which files the agent reads, edits and commits
- The `Open with`, `Edit with` and `Diff with` settings run commands you define
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/claude-code-filetreeDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The plugin hooks see which files the agent reads, edits and commits
- The `Open with`, `Edit with` and `Diff with` settings run commands you define
This is third-party code. Review the repository files before installing.
What it does
Claude Code Filetree adds a file tree panel for the current folder to the Claude Code terminal and Desktop app. When the agent reads, writes or commits a file, its row in the tree shimmers, and auto-collapse closes the folders the agent opened itself. Columns show git status, size, line count and date, with the branch and its ahead and behind counts at the bottom. The tree moves with vim-style keys. `z` jumps to a folder like zoxide, `s` searches by name, `q` searches inside files through `git grep` or `grep -r`, and `d` shows the diff of a file or of every changed file in a folder. The selected file and up to 100 marked entries go to Claude as context, and file references with a line in its replies become links. In the terminal, previews of code, Markdown, images, video frames, PDF and Word pages and a folder size treemap work. A separate feature guards files and folders from Claude's edits and shows writes outside the repository.
Who it is for. Developers working in Claude Code who want to see which files the agent touches and where.
Good fit when
- An agent edits dozens of files and you want to follow the progress without reading the tool call log
- Before a commit you want to review the changed files with diffs right in the panel
- The repository has files such as deploy configs the agent must not touch: guarded paths cover them
- You like jumping between folders with `z` and searching contents without leaving the session
- You need to find the heaviest folders of the project: the size treemap helps
Not a fit when
- You need a built-in editor: the plugin opens files in an external editor set in the `Edit with` setting
- Your Claude Code is older than 2.1.306, and an install on versions before 2.1.287 fails with `Unrecognized key: "options"`
- You want images in the preview in another terminal: they render only in Ghostty and kitty outside tmux and herdr
Example request
Show in the tree which files you are editing now and open the diff for the src directoryLimitations
You need Claude Code 2.1.306 or newer and `git`. Optional tools extend the preview: `magick` or `ffmpeg` for images and video frames, `pdftoppm` or `gs` for PDF, `soffice` for Word, `inotifywait` for live updates on Linux, and `tmux` or `herdr` to open an editor in a new pane.
The Desktop app has no split preview and no size treemap. GIFs and video show a single frame in the preview. On Windows, folder sizes come from file listings and the treemap draws one level.
The project is young, at version 0.7.1: settings and behavior may change.
How to disable. Open `/plugin` in Claude Code and remove `filetree`. Settings live in `/config` under the filetree name and go with the plugin.
FAQ
How do I install Claude Code Filetree?
Run `claude plugin marketplace add data-goblin/claude-code-filetree`, then `claude plugin install filetree@claude-code-filetree`. Inside a session the same steps use `/plugin marketplace add` and `/plugin install`.
Which keys does the tree use?
`z` jumps to a folder, `s` searches by name, `i` searches inside the selected folder, `q` searches file contents and `d` opens a diff. The shortcuts overlay shows the full list and `docs/keys.md` describes it.
Does the panel work in the Desktop app?
Yes, the tree and the highlighting of agent actions work. What is missing compared with the terminal is listed under limitations.
How do I protect files from Claude's edits?
Set guarded files and folders in the guards feature: the plugin keeps Claude from editing them and shows writes outside the repository. Details are in `docs/guards.md`.
Where do I change settings?
In `/config` under filetree. There you set which Claude activity to show, the auto-collapse mode, the `Open with`, `Edit with` and `Diff with` commands, the palette and the glyph set.
Discussion
No questions or reviews yet.
Related
PluginsA debugging tool for Claude Code that reads the session logs already saved on disk and shows exact file paths, diffs, model thinking and a category-by-category
A Claude Code plugin marketplace by Frad LEE: Git and GitFlow, GitHub, refactoring, memory, research, image generation and interface work
Neovim plugin that connects Claude Code to the editor: current file, selection, diagnostics and diff review of proposed edits
A Claude Code plugin that generates and maintains CLAUDE.md: a 0 to 100 quality score, a 150-line cap and stale reference checks
A Claude Code plugin that puts context usage, active tools, running subagents and todo progress into the statusline
A Claude Code status line displays the current model, Git state and context usage directly in the terminal
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Claude Code Filetree (this card) | no | 388 | |
| Claude HUD | no | 29,122 | shows context usage and task progress in the status line, while Filetree shows the files the agent reads and edits |
| ccstatusline | no | 13,542 | a configurable status line with the model, branch and context, while here there is a separate panel with a file tree |
README in short
The text begins with key features and animations, then installation through its own marketplace, a feature list linking to separate docs, settings in YAML, requirements, considerations and contribution rules. Changes go to release branches.