awesome-repositories.com
Blog
MCP
awesome-repositories.com

Descubre los mejores repositorios open-source con nuestra búsqueda potenciada por IA.

ExplorarBúsquedas curadasAlternativas open-sourceSoftware autohospedableBlogMapa del sitio
ProyectoAcerca deCómo clasificamosPrensaServidor MCP
Aviso legalPrivacidadTérminos
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·
remorses avatar

remorses/playwriter

0
View on GitHub↗
2,866 estrellas·111 forks·HTML·mit·6 vistaschromewebstore.google.com/detail/playwriter-mcp/jfeammnjpkecdekppnclgkkffahnhfhe↗

Playwriter

Playwriter is a browser automation framework and remote controller that manages stateful sessions and executes programmatic commands via the Chrome DevTools Protocol. It provides a system for controlling web browsers to interact with pages and extract data through both programmatic APIs and a command-line interface.

The project features a visual element selector that generates screenshots with accessibility labels, mapping visual interface elements to programmatic selectors to help agents navigate. It supports remote browser control through WebSocket tunneling, allowing users to manage browser instances running on external machines.

The framework covers isolated session management using sandboxed contexts and persistent state management to maintain continuity between separate commands. It also includes tools for headless browser testing and internal debugging of page scripts.

Features

  • Browser Automation Frameworks - A comprehensive framework for managing stateful browser sessions and interacting with web elements via programmatic APIs.
  • Agentic Browser Controllers - Acts as a bridge enabling AI agents to visually identify and interact with web browser elements.
  • Persistent State Management - Implements a persistent object to store interaction history and state across separate command executions.
  • CDP WebSocket Tunnels - Establishes WebSocket tunnels to connect to remote Chrome DevTools Protocol endpoints for browser control.
  • Stateful Session Persistence - Maintains browser context and authentication state across multiple API calls to ensure continuity of interactions.
  • Browser Session Managers - Manages isolated browser process sessions and data directories to prevent interference between automation agents.
  • Context Isolation Managers - Isolates browsing contexts and profiles using independent session identifiers to prevent data leakage between tasks.
  • Browser Session Persistence - Maintains and reuses browser sessions and isolated contexts to ensure a consistent state across automation commands.
  • Remote Browser Controllers - Manages and controls remote browser instances running on different machines via standardized messaging.
  • Chrome DevTools Protocols - Uses the Chrome DevTools Protocol to execute low-level page manipulation and browser control via JSON-RPC messages.
  • Remote Browser Connections - Allows connecting to browser instances running on remote machines via local networks or secure tunnels.
  • Command Line Interfaces - Ships a command-line tool for executing discrete JavaScript snippets against a remote browser without persistent local connections.
  • Browser Interaction CLIs - Provides a CLI for executing JavaScript commands to navigate pages and interact with elements in a running browser.
  • Accessibility-Based Selector Mappings - Generates screenshots with accessibility labels to map visual interface elements to programmatic selectors for AI agents.
  • Programmatic API Interfaces - Provides a programmatic interface to connect and automate a browser server using the Chrome DevTools Protocol.
  • Headless Browser Testing Frameworks - Automates web interactions and provides debugging for internal page scripts within headless browser environments.
  • Visual Element Locators - Provides a visual element locator that generates accessibility-labeled screenshots to help automation agents identify UI elements.
  • Automation Element Inspectors - Provides a tool to visually inspect elements and generate accessibility-labeled screenshots for automation agents.
  • DevTools Protocol Clients - Ships a client and CLI that communicates with browsers through the Chrome DevTools Protocol to control page behavior.

Historial de estrellas

Gráfico del historial de estrellas de remorses/playwriterGráfico del historial de estrellas de remorses/playwriter

Búsqueda con IA

Explora más repositorios increíbles

Describe lo que necesitas en lenguaje sencillo: la IA clasifica miles de proyectos open-source curados por relevancia.

Start searching with AI

Alternativas open-source a Playwriter

Proyectos open-source similares, clasificados según cuántas características comparten con Playwriter.
  • steel-dev/steel-browserAvatar de steel-dev

    steel-dev/steel-browser

    6,450Ver en GitHub↗

    Steel is a cloud browser automation platform that provides a REST API for launching and controlling remote Chrome browser sessions. It enables programmatic browsing and web scraping using standard automation tools like Puppeteer, Playwright, and Selenium, connecting to cloud-hosted browser instances via WebSocket and the Chrome DevTools Protocol. The platform supports both headless and headful browser sessions, with language-specific SDKs for TypeScript and Python. The service distinguishes itself through comprehensive anti-detection capabilities, including residential proxy rotation, CAPTCHA

    TypeScriptaiai-agentsai-tools
    Ver en GitHub↗6,450
  • vercel-labs/agent-browserAvatar de vercel-labs

    vercel-labs/agent-browser

    36,203Ver en GitHub↗

    This project is an agentic framework designed to enable autonomous web navigation and browser automation. It functions as a controller that translates natural language instructions into deterministic browser actions, allowing agents to interact with websites, perform data extraction, and manage complex authentication flows. By leveraging accessibility trees and semantic element resolution, the framework mimics human-like navigation, moving beyond brittle DOM selectors to interact reliably with modern web interfaces. The framework distinguishes itself through its focus on secure, scalable exec

    Rust
    Ver en GitHub↗36,203
  • chromedp/chromedpAvatar de chromedp

    chromedp/chromedp

    13,137Ver en GitHub↗

    chromedp is a browser automation framework and driver that controls web browsers via the Chrome DevTools Protocol. It functions as a headless browser automation tool and web browser controller, enabling the programmatic management of browser sessions, targets, and network responses through a remote debugging interface. The project provides specialized capabilities for Chrome DevTools Protocol automation, including headless browser testing, web scraping and data extraction, and mobile device emulation. It also supports browser-based visual regression by capturing precise screenshots of web pag

    Go
    Ver en GitHub↗13,137
  • browser-use/browser-harnessAvatar de browser-use

    browser-use/browser-harness

    15,265Ver en GitHub↗

    This project is an automation framework that connects large language models to web browsers via the Chrome DevTools Protocol for autonomous task execution. It functions as a bridge between intelligent agents and browser engines, allowing for the direct control of browser sessions and profiles. The framework features a self-healing agent capable of generating and executing custom scripts during runtime to resolve failures and optimize browser tasks. It supports stealthy deployment through the use of integrated proxies and captcha solvers to bypass bot detection and security mitigations. The s

    Pythonai-agentbrowser-agentbrowser-automation
    Ver en GitHub↗15,265
Ver las 30 alternativas a Playwriter→

Preguntas frecuentes

¿Qué hace remorses/playwriter?

Playwriter is a browser automation framework and remote controller that manages stateful sessions and executes programmatic commands via the Chrome DevTools Protocol. It provides a system for controlling web browsers to interact with pages and extract data through both programmatic APIs and a command-line interface.

¿Cuáles son las características principales de remorses/playwriter?

Las características principales de remorses/playwriter son: Browser Automation Frameworks, Agentic Browser Controllers, Persistent State Management, CDP WebSocket Tunnels, Stateful Session Persistence, Browser Session Managers, Context Isolation Managers, Browser Session Persistence.

¿Qué alternativas de código abierto existen para remorses/playwriter?

Las alternativas de código abierto para remorses/playwriter incluyen: steel-dev/steel-browser — Steel is a cloud browser automation platform that provides a REST API for launching and controlling remote Chrome… vercel-labs/agent-browser — This project is an agentic framework designed to enable autonomous web navigation and browser automation. It functions… chromedp/chromedp — chromedp is a browser automation framework and driver that controls web browsers via the Chrome DevTools Protocol. It… browser-use/browser-harness — This project is an automation framework that connects large language models to web browsers via the Chrome DevTools… cyrus-and/chrome-remote-interface — This project is a Node.js library and browser automation framework that provides a JavaScript interface for the Chrome… ultrafunkamsterdam/nodriver — nodriver is an asynchronous Chromium browser automation framework that provides headless control and web scraping…