One browser per run
When a digital worker learns a task or runs a saved workflow, Ramain starts a cloud browser for that run alone. It is not the browser on your laptop: signing in to a portal in your own tab does not sign the digital worker in, and nothing it does touches your machine.
The session carries what it needs to be understood later: the workflow it belongs to, the version that launched it, the inputs it received and its current status. When the run ends, the browser is released.
Why isolation matters
Portal automation goes wrong when many jobs share one browser, one cookie store or one long-lived desktop. Logins leak from one task into another, tabs drift, and when something fails nobody can say which job left the screen in that state.
Keeping each run in its own browser removes that guesswork. Two runs of the same workflow with different inputs cannot step on each other, and one team's work never shows up in another team's session.
Watch, step in, replay
While a run is active you can open it and watch the browser live, next to the inputs it collected and the step it is on. If the run needs a person, for an answer or a sign-off, it waits in that state rather than failing.
After it finishes, the run keeps its recording and step log. You can replay what the digital worker saw and did, step by step, which is how operations and audit teams check the work without re-running it.