The tree and git status

Browse the tree

• The Files panel is opened from the Inspector and shows the selected workspace’s tree.
• Each folder expands individually and loads on demand.
• The tree is virtualized: even with many files, it draws what is in view.
• The action bar has collapse all and reload the files — reloading is what you use when something changed on disk outside the app.

States you may find

State	What it means
Loading	The folder is being read
Empty	The folder exists and has no visible content
Error	The read failed — an access-denied message appears, instead of an empty list

A read error is not the same as an empty folder: if you see access denied, the problem is permission or connection, not missing files.

Show dotfiles and ignored files

Two independent options in the action bar:

• Show dotfiles — includes files and folders that start with a dot.
• Show git-ignored files — includes what .gitignore hides.

Both are per worktree: turning one on does not turn on the other.

The ignored-files switch only appears when it makes sense for that workspace. Not finding it is not a defect.

Git status markers

The tree rows show each file’s status relative to the active worktree’s git — modified, added, deleted and the other known states.

• The status comes from the project’s git, not from the panel: it is the same information the git area shows.
• The markers are a reading, not a command: clicking the row opens the file, it does not stage or discard the change.
• If the markers look out of date, reload the files from the action bar.

Where this differs from what you expect

• The tree is not the whole project folder when the workspace points at a subfolder. It shows the selected workspace’s folder.
• The tree hides nothing on its own beyond what the two options control: if a file does not appear, check whether it is a dotfile or is in .gitignore.

Related

• Searching files and content
• Opening and viewing files