This project, kimi-webbridge-fleet, is a tool designed to enhance the capabilities of AI agents by allowing them to drive multiple Chrome profiles simultaneously. It acts as a layer over Kimi WebBridge, enabling the use of one daemon per Chrome profile, managed by a single router with deterministic ports. This eliminates the limitation of Kimi WebBridge's single connection slot, allowing for concurrent use of different Chrome profiles, such as personal and work accounts, without the need to manually switch extensions or quit the browser.
Multi-Profile Support: Drive multiple Chrome profiles concurrently, each with its own distinct login and session.
Seamless Integration: Acts as a drop-in layer over Kimi WebBridge, requiring no patching of existing installations.
Automated Connection: Features a zero-click connection process that automatically points each profile's extension to its dedicated daemon, eliminating manual steps.
Platform Specificity: Currently optimized for macOS and Google Chrome, with clear indications for potential porting to other platforms.
Command-Line Interface (CLI): Provides a robust CLI for managing profiles, starting/stopping daemons, and interacting with the fleet.
Idle Auto-Close: Automatically closes inactive daemons after a configurable period to conserve resources, while keeping browser tabs open.
Direct Profile Access: Allows direct interaction with specific Chrome profiles by name, email, or directory.
The tool is built using Node.js and leverages various system commands and file interactions specific to macOS for managing Chrome processes and profiles. It interacts with Chrome's internal storage (LevelDB) and session files to achieve its functionality without relying on Chrome's remote debugging protocol, which has limitations in recent Chrome versions.
Installation can be done via npm, directly from source, or as a Claude Code skill. The project provides comprehensive documentation for setup, quickstart guides, and detailed CLI commands for managing the multi-profile environment. It requires a pre-existing Kimi WebBridge installation.
Built with