browser_session

Developer-mode browsers: a separate Chrome the companion launches, without the user’s logins. Only launch one when the user explicitly asks for it, or when a tool reported that an operation needs developer mode (heap snapshots, Lighthouse, raw CDP). For everyday work use the user’s shared tabs. Each named context is a separate Chrome with its own persistent profile; several can run in parallel. launch/close/status take a context (default “default”); contexts lists saved profiles; delete removes a stopped context’s profile.

Everyday work happens in the user’s shared tabs. The dashboard’s Settings page decides whether a separate browser may open at all (Only when needed, Always, Never).

Parameters

enum

required

One of: launch, status, close, contexts, delete.

string

Context name, e.g. “work” or “personal” (default “default”)

boolean

close: close every running context

string

Initial URL for launch

boolean

Launch without a window (watch it via the live view URL in browser_status)

string

string[]

Extra Chrome switches

boolean

Open Chrome DevTools for every tab so the user can watch the standard panels while you work (default: true unless headless)

string

Proxy server for this browser, e.g. “http://proxy:8080” or “socks5://127.0.0.1:1080”

string[]

Unpacked extension directories to load into this browser

string

Where downloads land (default ~/.browspark/downloads/<context>)

Example

Launch the default context

{
  "action": "launch"
}

Launch a named, headless context behind a proxy

{
  "action": "launch",
  "context": "scraper",
  "headless": true,
  "proxy": "socks5://127.0.0.1:1080",
  "url": "https://example.com"
}

Close everything

{
  "action": "close",
  "all": true
}

Browser automation

Developer tools

Parameters

Example

​Parameters

​Example

Parameters

Example