Desktop only
Browser session management is available in the RealTimeX Desktop app.
Browser Tool
Browser Tool is the session manager for RealTimeX Browser. Use it to create isolated browser profiles, keep authenticated sessions available for agent workflows, and control how browser state is separated between tasks.
The built-in Agent Browser plugin uses these browser sessions when an agent needs to browse or automate the web.
Where to find it
- Open
Settings > Tools > Browser Toolin RealTimeX Desktop.
What the Browser Tool manages
- the default browser session
- named browser sessions
- cookies and authentication state per session
- profile storage and open tabs
- debug ports and session guardrails
Default session vs named sessions
Default session
- stays open as the general-purpose browser profile
- unrestricted
- uses the default debug port
- best for quick manual browsing
Named sessions
- keep separate cookies, auth state, tabs, and profile storage
- get their own debug port
- start in anchored-origin mode
- work well for site-specific agent workflows or separate accounts
Anchored-origin mode keeps a named session tied to the first site origin it opens, which is useful when you want tighter guardrails for agent browsing flows.
Typical setup
- Open Browser Tool.
- Create a named session if you want an isolated profile.
- Open the session.
- Sign in to the sites you need.
- Return to your agent or workflow and run the browser-backed task.
- Reopen, clear, or delete the session later as needed.
Common tasks
Open or focus a session
Use Open Session for a stopped session or Focus Session for a running one.
Clear session data
Use this when you want to remove stored cookies and auth state without deleting the session entry itself.
Delete a named session
Use this when you no longer need the profile. Deleting removes the named session after the browser stops running.
When to use named sessions
- you want separate logins for different accounts
- you want one browser profile per workspace or task
- you want authenticated browsing without mixing state with your default session
- you want origin-aware guardrails for agent handoff
Troubleshooting
- If Browser Tool says a port is already in use, stop the conflicting process and try again.
- If a site stops working, clear that session and sign in again.
- If you need a fresh environment, create a new named session instead of reusing the default one.