Can Runavelo control multiple browsers on one computer?
Supported Runavelo editions can operate multiple independent browser sessions in parallel, including background sessions that do not take over the foreground browser.
PARALLEL BROWSER AUTOMATION
Run independent browser workflows without taking over your screen.
Supported Runavelo editions can control multiple isolated browser sessions on one computer. Define each job, cap concurrency, keep state separate, and inspect the workflow and logs when one session needs attention.
ISOLATION BEFORE SPEED
Concurrency is useful only when state remains correct.
Several tabs in one profile can share login state, cookies, and storage. For work involving different accounts, regions, customers, or independent jobs, each unit needs a deliberate session boundary and its own inputs, output, and status.
1. QueueValidate independent jobs and their required inputs.
2. IsolateCreate or choose the intended browser session for each job.
3. ControlAdmit only the configured number of active workers.
4. ReconcileValidate results, close sessions, and merge output safely.
BACKGROUND CDP INTERACTION
Target webpage elements, not screen coordinates.
Runavelo web click, input, hover, and drag commands use Chrome DevTools Protocol. This allows a controlled page to receive an element-level action without moving the global physical mouse across the user's desktop.
Background operation still requires good selectors and readiness checks. Prefer stable attributes and element relationships over coordinates, generated class names, or labels that include a changing page number.
BOUNDED CONCURRENCY
Treat parallelism as a resource budget.
The correct limit depends on memory, CPU, page complexity, network capacity, service limits, and the cost of recovering several simultaneous failures. Start small, measure completed work and error rates, and add backpressure so excess jobs wait in a queue.
Parallelism should change scheduling, not business meaning. First make the worker flow correct sequentially. Then isolate it as a repeatable unit and prevent workers from writing unsafely to the same workbook, file, or record.
RESPONSIBLE ACCESS
Respect permission, terms, and service capacity.
Use documented APIs when they are the appropriate supported route. For browser tasks, follow the target service's terms, account rules, robots guidance, rate limits, and applicable law. RFC 9309 standardizes the Robots Exclusion Protocol but explicitly does not make robots rules a form of access authorization.
Do not circumvent authentication or technical controls. Stop on explicit denial, retain only permitted data, and make request volume predictable.
OBSERVABLE BY WORKER
Know which session produced every result and error.
Parallel logs need a job identifier alongside workflow, line number, time, level, and message. Record page transitions, record counts, retry reasons, final output, and cleanup. Do not place passwords, tokens, cookies, or unnecessary personal data in logs.
If one worker fails while others finish, the workflow should preserve that worker's root error and report partial completion honestly instead of collapsing the whole run into a generic failure.
AI-ASSISTED REPAIR
Diagnose the failed session with real context.
The assistant can inspect the visible workflow, command parameters, runtime logs, and error stack. It can distinguish a page-specific selector from a timeout, wrong session, or missing stop condition and propose a focused workflow change.
Once approved, ordinary browser steps return to deterministic execution. Repeated interactions do not require a model call unless the workflow deliberately contains one.
VERIFICATION
Test the conditions that expose concurrency defects.
Cover single-page and multi-page jobs, empty results, final-page detection, expired authentication, a worker that fails while peers succeed, queue length above the concurrency cap, duplicate inputs, service throttling, application shutdown, and output already present. Confirm that browser sessions close after every terminal path.
A fast wrong workflow is still wrong. Validate record counts and output ownership before increasing worker count. Scale only after session isolation and recovery are proven.
QUESTIONS
Parallel browser automation FAQ
Are parallel tabs the same as isolated sessions?
No. Tabs in one normal profile may share cookies and storage. Independent sessions are intended to keep browser state separate.
Does browser automation use the physical mouse?
Runavelo web click, input, hover, and drag operations use Chrome DevTools Protocol. They target browser elements rather than moving the global physical mouse.
Is unlimited concurrency recommended?
No. Set a conservative limit based on computer resources, workflow behavior, service capacity, account rules, and published rate limits.
ENGINEERING REFERENCES
Primary specifications and documentation
- Chrome DevTools Protocol Target domain documents browser contexts and background targets.
- Playwright isolation documentation explains independent cookies, local storage, and session storage.
- RFC 9309 defines the Robots Exclusion Protocol and its limitations.
See a complete paginated collection pattern.
Start with one correct visual workflow, then decide where isolation and bounded concurrency add real value.