roam-playwright-session

Persistent Playwright session management for Roam Research stores local storage artifacts and authenticated user profiles in a local directory. This allows developers to bypass manual login and verify UI behavior rapidly.

Yes, you can test multi-user graph interactions by launching multiple separate Playwright browser instances. This skill manages isolated profiles for concurrent testing across multiple accounts to verify cross-account synchronization in real-time.

Yes, configured environment variables are required for secure credential handling before launching persistent Playwright sessions. You also need local directory access to ensure session persistence for your Roam Research extension testing workflows.

Automating isolated development workflows is best achieved by managing multiple authenticated user profiles through persistent Playwright sessions. This approach facilitates rapid testing of Roam extension features in a pre-authenticated environment.

Persistent local storage artifacts are required to maintain authenticated state across Playwright testing sessions. Without them, the browser cannot preserve login credentials, forcing repetitive manual authentication for every Roam extension test run.

You can launch a specific persistent Playwright session by executing the playwright open command with your desired slot number. This targets a specific pre-authenticated profile to start testing your Roam extension immediately.