Let any MCP-speaking coding agent drive your real, logged-in browser tab.
Users
18
+15 in 30 days
Rating
5.0 / 5
unchanged in 30 days
Ratings
2
+1 in 30 days
Store rank
#156K
#130K among extensions
Version
0.2.13
updated 12 Oct 2026
Users
monthly, 1 months
Latest, 16 Oct 2026:18 usersMove the mouse over the chart for any month
Ratings count
monthly, 1 months
Latest, 16 Oct 2026:2 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About TaskWindow
TaskWindow lets any coding agent — Claude Code, Cursor, Windsurf, Codex, or any MCP client — drive your real, logged-in Chrome: the tabs you're already signed into, without touching the windows you're working in.
[coding agent] --MCP--> [TaskWindow daemon on your machine] --WebSocket--> [extension] --CDP--> [your tab]
SETUP (5 MINUTES) Requires Node 18+ and Chrome 116+.
Run: npm install -g taskwindow
Run: taskwindow install The guided installer detects your coding agents (pick any combination or None), installs the background daemon as a login service, and downloads the extension. In Chrome, turn on Developer mode and load the extension via the installer's guided flow.
TRY IT Ask your agent: "Open example.com in a new tab and take a screenshot." A blue tab group named after your task appears in a separate TaskWindow window — the agent's workspace, shared by every task, kept open by a pinned tab no agent can close. Then try: "Find the sign-up link and read the page's headings."
WHAT THE AGENT GETS
Tabs: create, list, close, navigate, reload
See: screenshots, page structure, text extraction, element search
Act: click, type, key presses, scrolling, form filling, file upload
Debug: console messages, network requests
Efficiency: multi-step batches, GIF recording, responsive viewport testing
HOW ISOLATION WORKS
Every tab the agent creates goes into a named tab group for that task. By default the agent can only see and act on its own groups — never yours.
Sessions are isolated: concurrent agents never share tabs, even with the same task name.
The daemon listens on 127.0.0.1 only. Pairing uses a short-lived, single-use code; a long-lived token is issued only to your own daemon.
Agent actions are visible: a phantom cursor and glow show where the agent is acting, and Chrome shows its standard "started debugging this browser" infobar while it does.
REQUIREMENTS & LIMITS
Chrome/Chromium 116+ (Chrome, Edge, Brave, Arc…)
Node 18+ for the local daemon
Page tools run in the top frame; native alert()/confirm() dialogs block the attached tab
Open source: https://github.com/clawnify/taskwindow