Files and directories

`~/.browspark/`

Path	Written by	Contents
`tools.json`	companion, when dashboard policies change	`{"disabled": ["browser_upload", …]}`. The combined disabled list is loaded on start before extensions reconnect.
`profile/`	Chrome/Chromium	Persistent profile of the `default` developer context.
`profiles/<name>/`	Chrome/Chromium	Profiles of named developer contexts. The `chrome` and `chromium` choices share these legacy paths.
`profiles/.brave/<name>/`	Brave	Profiles of Brave developer contexts.
`profiles/.firefox/<name>/`	Firefox	Profiles of Firefox developer contexts.
`profiles/.zen/<name>/`	Zen	Profiles of Zen developer contexts.
`downloads/`	developer browsers	Downloads made in developer contexts; `browser_status` gives the exact directory.
`artifacts/`	companion	Exports, see below.

Artifacts

Files are named by kind and id. Chromium-specific traces and profiles open in DevTools; other exports use their usual formats. Firefox and Zen have documented export limits.

Kind	Extension	Opens in
Performance trace	`.json`	DevTools Performance panel, Perfetto UI
CPU profile	`.cpuprofile`	DevTools Performance / JavaScript Profiler
Heap snapshot	`.heapsnapshot`	DevTools Memory panel
Allocation sampling	`.heapprofile`	DevTools Memory panel
Network export	`.har`	DevTools Network, HAR viewers
Lighthouse	`.html`, `.json`	Browser, Lighthouse viewer
Recorder flow	`.json`	`devtools_recorder`
Playwright export	`.spec.ts`	Playwright
PDF	`.pdf`	Any viewer

Tools that accept path write there as well as, or instead of, the artifacts directory (the tool page says which).

Extension storage

Storage	Keys	Lifetime
`chrome.storage.local`	`port`, `instanceId`, `shareAll`, `stopped`, `activityLog`, `devMode`, `disabledTools`, `toolCatalog`, `idleDetachMs`, `overlay`, `backgroundMode`, `graphEnabled`	Persistent per browser profile
`chrome.storage.session`	`browserSessionId`, `shared` (tab ids shared individually), `excluded`	Until the browser restarts
`localStorage` of the dashboard page	theme, last selected setup client, expanded rows	Persistent, UI conveniences only

Each profile has its own extension storage. Firefox uses the equivalent browser.storage APIs. instanceId identifies that extension installation and browserSessionId distinguishes browser runs, so recycled native tab IDs do not select stale tabs. The activity log and current graph snapshot are held in the extension background process’s memory. Graph node positions and canvas pan/zoom are held in the dashboard tab’s memory; reloading the tab resets its arrangement.

Repository layout

Folder	Contents
`companion/src/`	MCP server: `index.ts` (transports, relay, HTTP), `bridge.ts` (WebSocket and HTTP routes), `graph.ts` (connection snapshots), `session.ts` (tab routing, contexts), `cdp.ts` (Chromium developer browsers), `firefox.ts` (Firefox/Zen developer browsers), `browsers.ts` (executable discovery), `page.ts` (snapshots, input, reading), `tools.ts` (browser tools), `live.ts`, `artifacts.ts`, `context.ts` (tool wrapper, policy, per-agent state), `devtools/` (one module per DevTools panel)
`companion/test/`	Unit tests, e2e scenarios, the harness, the capability and docs generators
`extension/`	`shared/` (background process, dashboard, `app.html`, `app.css`, `assets/`), `chromium/manifest.json`, `firefox/manifest.json` — one shared codebase, per-browser manifests
`shared/`	`protocol.ts`, the wire protocol; `firefox-dom.ts`, the DOM adapter used by both the companion and the Firefox extension
`test-apps/`	Deterministic pages, API, service worker and source-mapped script used by the tests
`docs/`	This site

Get started

Connect an agent

Concepts

Dashboard

Guides

Reference

Files and directories

`~/.browspark/`

Artifacts

Extension storage

Repository layout

​~/.browspark/

​Artifacts

​Extension storage

​Repository layout

`~/.browspark/`

Artifacts

Extension storage

Repository layout