Enabling File Tracking
File tracking is off by default. To turn it on:- Go to your environment’s settings page (
Environments > [your environment] > Settings). - Toggle File Tracking to Enabled.
Configuration
After enabling, you can optionally configure what gets tracked.| Setting | Default | Description |
|---|---|---|
| Tracked Paths | /home, /root, /workspace, /app | Directories monitored for changes (can vary by environment) |
| Exclude Patterns | node_modules/, .venv/, __pycache__/, *.pyc, .cache/, .npm/, .git/objects/, .git/logs/, *.so, *.o, *.a | Glob patterns for files and folders to skip |
Using the Code Tab
Once file tracking is enabled and a trace has completed:- Open a trace
- In the environment pane, click the Code tab (next to Environment, Logs, and Debug)
What You’ll See
The Code tab has two panels:- File tree (left) — A collapsible directory tree of all files the agent touched. Each file shows a badge indicating its change type: M (modified), A (added), or D (deleted). Folders containing changes show a colored dot.
- Code viewer (right) — A syntax-highlighted view of the selected file. Modified files show a side-by-side diff (before on the left, after on the right). Added and deleted files show a single pane.
Notes
- Larger files may be lazy-loaded when you click them (the tree loads instantly regardless of project size).
- Binary files are detected and skipped.
- File tracking adds minimal overhead — a sidecar uploads a compressed file snapshot at the end of the session, and diffs are rendered in the viewer from trace steps.
See Also
Environments
Deploy and manage environments
Debugging Traces
DEBUG and LOGS tabs for trace investigation