Running a profile

Positions every running profile in ids on the primary display's work area. grid gives each window an equal cell, cascade overlaps them with their title bars clickable, stack returns them all to full size on top of each other. Bounds go through the browser rather than the window manager, because Chromium owns its own geometry and undoes anything moved from outside. A profile that is no longer running is counted in skipped, not an error — the rest still move.

Delivers text as real keystrokes into whatever is focused in each profile, in parallel. Each window samples its own timing rather than mirroring one keystroke stream: forty sessions typing the same password with millisecond-identical intervals is itself a correlation signal, which is the flaw in mirroring input verbatim. Click into the right field in each window first — the keystrokes go wherever focus already is.

Navigates the focused page of each running profile to url. A profile with no page open gets a new tab rather than being reported as a failure, since that is what was asked for.

Launches the browser with the profile’s fingerprint, proxy and cookies already applied, and returns the DevTools endpoint to attach to. A profile with a proxy is not started until that proxy has answered — see the 502 below. Starting an already-running profile returns the existing session rather than launching a second one. On macOS, and only when the perProfileDockIcon setting is on — it is off by default — a visible launch also gets a Dock tile of its own, drawn for the project: its colour, its glyph and its name, which is what identifies a window at Dock size. A launch through this route wears an API ribbon on that tile — a blue band across the top-left corner — so a browser a script opened is tellable from one somebody opened by hand. The tiles come from a small pool of window identities rather than one per profile, because macOS greets every bundle identifier it has not seen with a notification banner, for ever; the pool bounds that at the most browsers you have ever had open at once. Re-dressing a slot for its next occupant costs about 0.7s at launch, and nothing when the slot has not changed hands. Pass offscreen for any run nobody is going to watch — it parks the window off the edge of the screen and skips the Dock identity, which is what you want for scraping, warm-up and checks. It is not the same as headless: the browser is still headed, so it keeps the real User-Agent and the real GPU.

Shuts the browser down properly rather than killing it: the request goes over DevTools so Chromium runs beforeunload handlers, tears down tabs, serialises the session and flushes its cookie and storage databases before exiting. It escalates to a signal only if that does not finish. This is why a clean stop is not instantaneous — and why the tabs come back next time.

The current session for one profile. Returns an idle record rather than a 404 when the profile is not running, so callers can poll without special-casing.

Everything currently open, across all projects. Each row carries inspectedBy — the inspecting proxy that browser was launched through, or null. It answers a different question from GET /settings: the setting says what the next launch will do, this says what an open browser is doing, and they disagree for as long as a profile started before the switch is still open. Chromium takes its proxy from the command line and there is no way in from outside, so turning traffic inspection on does not reach a browser that is already running — restarting it is what moves it.

Cleanly stops every running profile, in parallel. stopped is true only when every browser closed; one that would not is named in failures with the reason, never folded into a success.