osaurus-browser

Headless browser sign-in can be automated securely using a dedicated helper window that authenticates per-agent sessions without exposing credentials in chat. This isolates login flows while persisting cookies and localStorage on disk.

Per-agent session persistence isolates browser sessions on disk, storing cookies, localStorage, and IndexedDB separately for each agent. This ensures multi-agent environments maintain independent authenticated states across navigations.

Browser sessions are kept isolated across multiple agents using per-agent on-disk storage and a browser lock mechanism for coordination. This separates cookies, localStorage, and IndexedDB so agents never share session state.

Console and network requests can be inspected during headless browser automation using built-in inspection tools. These tools capture request details and console output while agents navigate pages and drive interactions.

Headless browser automation works for multi-agent data gathering by combining per-agent session isolation with page snapshot collection. Agents navigate sites, sign in securely, and extract data without sharing credentials or session state.

To start automating browser interactions with per-agent isolation, you need three core functions: browser_open_login to authenticate, browser_navigate to load pages, and browser_do to drive interactions. These maintain persistent sessions across tasks.