browser

Name: browser
Availability: InStock
Author: Glide

Orchestrate six isolated browser instances with per-agent profiles and login re-sync.

10|Updated Dec 30, 2025

Search Tags:#automation #MCP #Playwright #parallel #session-management #browser

Ready to run

npx skills add https://github.com/glideapps/glide-code --skill browser-glideapps

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browser
Source: https://github.com/glideapps/glide-code/tree/main/glide/skills/browser
Command: npx skills add https://github.com/glideapps/glide-code --skill browser-glideapps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes the management of six independent browser instances, each with its own profile, to prevent session conflicts when running multiple agents concurrently.

Core Features & Use Cases

Six isolated browser instances with dedicated profile directories.
Clear assignment of each agent to a specific browser to enable parallel tasks.
Re-sync and login workflow to refresh profiles across all browsers as needed.

Quick Start

Start the skill and assign each agent to a dedicated browser, e.g. "Build the Tasks screen using browser 1" and "Design the Projects screen using browser 2".

Frequently Asked Questions about browser

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run parallel browser automation tasks without session conflicts?▼

Parallel browser automation requires isolated sessions to prevent conflicts. This Skill orchestrates six independent browser instances, each with dedicated profiles, and assigns agents to specific browsers so concurrent tasks—like UI testing across different screens—maintain separate authentication and state.

Can I automate multiple browser tasks at the same time?▼

Yes. This Skill enables parallel agent operations by managing six isolated browser instances simultaneously. Assign each agent to a dedicated browser instance, and they run concurrent tasks without interfering with each other's sessions or login state.

How do I manage authentication across multiple browser sessions?▼

The Skill implements a login and re-sync workflow that refreshes profiles across all browser instances as needed. Each browser maintains its own profile directory, and the workflow ensures shared authentication is synchronized without session conflicts between agents.

What's the best way to coordinate browser automation for UI testing?▼

Coordinate browser-driven UI testing by using isolated browser instances with per-agent assignment. This Skill manages six parallel sessions with independent profiles, ideal for testing multiple screens or workflows simultaneously while keeping each agent's interactions isolated.

Do I need separate browser profiles for concurrent automation?▼

Yes. Concurrent automation requires separate profiles to prevent session conflicts. This Skill automates profile management across six dedicated browser instances, eliminating the need to manually configure isolation and ensuring agents operate independently.

Can I use Playwright with multiple parallel browser instances?▼

Yes. This Skill orchestrates parallel Playwright-driven browser sessions by managing six independent instances with isolated profiles and coordinated agent-to-browser assignments, enabling concurrent UI automation and testing workflows.