Project Explorer

Browse and edit the files behind a thread in the side panel, with git status colouring every name the way VS Code does. Modified files read amber, new files green, deleted red, and a collapsed folder inherits the colour of whatever changed inside it. Saving sends back the hash the file had when you opened it, so a change an agent made underneath you reports a conflict instead of being overwritten. Dotfiles such as .claude and .env appear, and directories load one level at a time, so a repository with node_modules opens as quickly as an empty one. Needs a thread whose environment has a workspace; git colours need that workspace to be a git repository.

Overview

View source

What you get

A Project Explorer entry in the thread side panel's New tab list. It opens a two-pane tab: the workspace file tree on the left, the file you picked on the right.

The tree colours files the way VS Code does, from the working tree of the thread's own environment:

amber for modified, renamed, or copied
green for added or untracked
red and struck through for deleted
purple for an unmerged conflict

A collapsed folder inherits amber when anything beneath it changed, so you can see where an agent has been working without expanding the tree.

How it works

Directories load one level at a time, when you expand them. Nothing walks the repository, so a project with node_modules opens as quickly as an empty one, and a folder you never open costs nothing. Listings are cached for the life of the tab, and a collapsed folder unmounts its contents entirely.

Files open with BB's own syntax highlighting and code theme. The Edit button swaps the viewer for a text editor: Cmd+S or Ctrl+S saves, Tab inserts two spaces, and a dot beside the path marks unsaved work. Closing a file with unsaved changes asks first.

Saving is compare-and-swap. The plugin sends back the SHA-256 the file had when you opened it, so if the agent edited that file while you were typing, the save stops and tells you instead of overwriting the agent's work.

Dotfiles such as .claude, .env, and .github appear in the tree. BB's own directory listing hides them, so the plugin reads the directory itself through a host entry that runs on the machine holding the files — which also means a workspace on a remote host behaves the same way. .git stays hidden.

Also included

A bb project-explorer ls <path> command lists any directory exactly as the tree sees it, with --json for scripting. Agents can use it to inspect the same workspace from a shell.

Requirements

The thread needs an environment with a workspace path. Git colours need that workspace to be a git repository; in a plain folder the tree still lists and edits files, without colours.

Files over 2 MB and files containing NUL bytes are listed but not opened.

More from NinjasWeb

Project ColorsOrganize busy sidebars by giving every project its own color. Choose from seven colors; project headings, nested threads, and conversation titles carry the project's visual identity. Choices stay local to each BB client, and the plugin uses no external service or account.19

More in File Viewers & Editors 12

Browse, open, preview, or edit files and document vaults.

View all

File ManagerManage the files on the machine bb runs on without a terminal: browse, upload, move, rename, extract and hand them to the agent. Opens as a sidebar page, as a tab beside a thread that can start in that thread's folder, and from a file link in a message. Double-click shows images, PDF, video, Markdown and code; Space looks inside zip, tar, 7z and rar archives without extracting them. Multi-gigabyte uploads resume after a dropped connection. On a phone, selected rows get an Actions bar with the whole row menu. Access stays inside the home folder of the user bb runs as; tar, 7z and rar archives need tar and 7z on that machine.

Foma353

FilesA VS Code-style file explorer and editor for the workspace behind a thread. Search in files finds a word across every file in the project: results are grouped by file with each hit highlighted, and clicking one opens the file on that line. It is smart case, with match-case, whole-word and regex toggles, and built for typing — file contents stay in memory between searches, so refining a query re-runs in tens of milliseconds, and a regex runs in its own worker so a runaway pattern cannot freeze BB. Around it: a file tree that shows dotfiles, editor tabs, a go-to-file palette (Cmd+P), find in the open file (Cmd+F), syntax highlighting in your BB code theme, and edit and save guarded so a change an agent made underneath you is never clobbered. Two pickers choose the project and then its checkout or one of its worktrees; beside a thread it is pinned to that thread's worktree. Adds a `bb files` command so agents can browse and read the same workspace from the CLI, on whichever machine it lives.

AbdElrahman Telb242

File TreeFind the file an agent mentions and keep the workspace tree beside the conversation. Search by name or path, open previews, add relative paths to drafts, create a blank markdown file, delete a file after confirmation, and reveal or copy files from the machine that owns them. Files show Seti-style type icons for markdown, JSON, gitignore, env, and other common names. Project threads stay rooted in their checkout; personal threads can browse a configured folder. Requires local file access on the BB machine; Finder reveal is macOS-only.

Yuriy Egorov43