Will multiple Agents or accounts interfere with each other?

Create an independent browser session for each task. If you need to save login state for different accounts, use a separate Context for each account to avoid mixing browser state.

Have each Agent connect to and control its own session to keep its pages and interactions separate. With Chromium and a project plan that supports persistent Contexts, you can save each account’s login state separately.

The same Context cannot be used by multiple active sessions in read-write mode at once. Close the session using it normally and wait until the Context is available before reusing it. Parallel tasks remain subject to your project’s concurrency limit.

Independent sessions do not override a website’s account rules. If multiple tasks modify the same record on a website, your program must still coordinate the order of those operations.