A native Windows automation bridge that enables LLMs to control Google Chrome through intelligent protocol selection, providing secure, performant, and reliable browser automation specifically optimized for AI-driven interactions.
Build a production-ready automation bridge that combines Windows UI Automation with Chrome DevTools Protocol, WebDriver, and Native Messaging to create the most flexible and secure browser automation platform for LLM interactions.
- Security First: Every feature must pass security review before implementation
- Protocol Agnostic: Support multiple automation methods, selecting the best for each task
- LLM Optimized: Design APIs and responses specifically for LLM consumption
- Production Ready: Build for reliability, monitoring, and enterprise deployment
- Extensible Architecture: Enable plugin system for custom capabilities
Surfboard implements a layered architecture:
- Core Layer: Win32 APIs for window discovery and management
- Automation Layer: Windows UI Automation for application interaction
- Browser Layer: Chrome DevTools Protocol, WebDriver, and Extensions API
- Communication Layer: WebSocket server optimized for LLM interaction
- Security Layer: Sandboxing, authentication, and audit logging
🚧 Currently in Phase 0: Foundation & Planning
See Roadmap.md for detailed development timeline and progress tracking.
- Windows 10 version 1809 minimum (Windows 11 recommended)
- Google Chrome 64+ (Chrome 117+ recommended for full CDP support)
- .NET 6+ or Visual Studio 2022 with Windows development workload
- Windows SDK 10.0.26100
- Windows SDK for UI Automation APIs
- Chrome with
--remote-debugging-portcapability - WebSocket library for real-time communication
- Code signing certificate (for UIAccess functionality in production)
Coming soon - currently in development
- Technical Specification - Comprehensive technical research and implementation guidance
- Development Roadmap - 24-week development plan with phase gates
- Architecture Documentation - Coming in Phase 0
- Security Model - Coming in Phase 0
This project is currently in early development. Contribution guidelines will be established during Phase 0.
License to be determined
Security is our top priority. Please see our Security Policy for reporting vulnerabilities.
Security documentation will be completed during Phase 0