BrowserSkill: Connecting AI Coding Agents to Your Logged-In Browser Tencent has open-sourced BrowserSkill (bsk), a lightweight local bridge that connects shell-capable AI coding agents such as Claude Code, Cursor, and Codex directly to a developer's already logged-in browser. The tool uses a three-tier Rust CLI and daemon architecture with a Chromium extension to let agents inherit existing session cookies and logins, borrow open tabs, capture screenshots, and request human help for CAPTCHAs or verification prompts without hijacking the user's active window. One of the biggest hurdles in modern AI-assisted software development is giving agents reliable access to the web. Whether you are using Claude Code, Cursor, Codex, or custom autonomous agents, software engineering rarely happens in a vacuum. Developers constantly need agents to verify UI flows on localhost, check staging dashboards, inspect documentation, or automate repetitive web tasks. Until now, developers were forced to choose between two deeply flawed approaches: To solve this dilemma, Tencent open-sourced BrowserSkill bsk —a lightweight, local bridge connecting shell-capable AI agents directly to your already logged-in browser without interrupting your active workflow. Here is a complete technical look at how BrowserSkill works, its architecture, and how to configure it for your coding agents. When an engineer builds an internal feature or tests a pull request, they are usually already authenticated into GitHub, Jira, AWS Console, or their local development environment. Spinning up a headless Playwright instance means: BrowserSkill bypasses this entirely by recognizing a fundamental truth: the developer's browser is already authenticated. By securely bridging the agent to the developer's existing browser profile, the agent inherits all session cookies, local storage, and active logins out of the box. BrowserSkill avoids screen hijacking through a clean three-tier architecture: ┌─────────────────────────────────────────────────────────────┐ │ AI Coding Agent Claude Code / Cursor / etc. │ └──────────────────────────────┬──────────────────────────────┘ │ Shell commands ▼ ┌─────────────────────────────────────────────────────────────┐ │ bsk CLI & Daemon Rust │ └──────────────────────────────┬──────────────────────────────┘ │ Local IPC / WebSocket ▼ ┌─────────────────────────────────────────────────────────────┐ │ BrowserSkill Extension │ └──────────────────────────────┬──────────────────────────────┘ │ ┌──────────────┴──────────────┐ ▼ ▼ User's Main Window Agent Window Dedicated Your daily browsing; Agent executes tasks here; never stolen or frozen background, non-intrusive bsk CLI & Background Daemon Rust : Agents can interact directly with authenticated web apps, staging dashboards, and internal services without needing separate test accounts or API access tokens. request-help Autonomous agents often get stuck on edge cases: CAPTCHAs, SMS verifications, or high-risk confirmation dialogues. Instead of failing silently or crashing the session, BrowserSkill allows the agent to trigger a help request: bsk request-help --session