Projects & state
What is portable, device-local, or session-only.
Projects & state
A .busloom.json file is the reviewable source of truth for one device or device family. It should be safe to share after reviewing endpoint names and certificate paths. Credentials, accepted certificate pins, account state, and live history are not embedded.
| Owner | Examples | Lifecycle |
|---|---|---|
| Project file | Profiles and TLS paths · views · tags/groups · saved Trends · import presets · automation · notes · addressing/display | Portable and reviewable |
| This device | Theme · text size · keybindings · recent projects · accepted TLS pin · MCP bearer token · installed license | Never travels with the project |
| Current session | Live values · Raw Traffic window · Trend samples · floating-bar positions · unexported run output | Lost unless recorded/exported |
A practical team workflow
Keep one canonical project
Store the .busloom.json beside related firmware or test assets. Relative TLS paths resolve from the project directory.
Create named profiles
Use one profile per real endpoint or bench. Use Duplicate As to create a variant instead of overwriting another engineer's setup.
Review before committing
Project files are readable JSON. Check connection endpoints, certificate paths, new tags, write-capable automation, and view ranges.
Create a focused version
Professional local Git integration commits only the active project file. It does not initialize a repository, change branches, push, or include unrelated files.
Save, recovery, and reopening
Save and Save As write the project. An unsaved recovery draft is maintained locally as crash protection, but it is not a second portable project. Opening another project replaces project-owned configuration and clears project-specific runtime such as prior scan results; recordings and reports open as independent Replay tabs instead.