Files and Reader
Use the file browser when you want to move through the workspace tree, then open files in Reader for a safer preview flow.- browse the workspace without loading the whole repo at once
- search by path when you already know part of the file or folder name
- inspect markdown, code, text files, and raw assets without leaving the workspace shell
Terminal
Use the built-in Terminal when you want logs and commands next to the rest of the workspace context.- run project commands without leaving fabriqa
- keep build or test output close to the chat that triggered it
- line up terminal output with the same workspace or worktree session you are actively using
Git Changes
Use Git Changes to confirm what actually changed while the chat was working.- review staged, unstaged, and untracked files
- inspect diffs before you accept the work at face value
- stay aligned with a worktree-specific branch workflow when you are in isolated work
Usage and context
Use the usage and context indicators when you want to understand what the current chat is consuming.- watch token and cost details
- notice when a long-running chat is approaching context pressure
- compare the visible usage state after you switch providers in the same chat
Recommended review loop
Move through the tools in this order when you want the fastest confidence check:- Read the chat output.
- Open the referenced file in Reader.
- Inspect the diff in Git Changes.
- Open Terminal if you need supporting commands or logs.
- Check Usage when the conversation is getting large or expensive.