Skip to content

feat(cli): detach --close-tabs for extension sessions - #44084

Merged
Pavel Feldman (pavelfeldman) merged 1 commit into
microsoft:mainfrom
pavelfeldman:detach-close-tabs
Nov 12, 2026
Merged

Pavel Feldman (pavelfeldman) merged 1 commit into
microsoft:mainfrom
pavelfeldman:detach-close-tabs

Conversation

@pavelfeldman

Copy link
Copy Markdown
Member

Summary

  • playwright-cli detach --close-tabs closes the tabs of a session attached with --extension before it detaches, so no gray tab group stays. Without the option, the tabs stay open as before.
  • The playwright-cli skill now documents attach through the extension: browser name, --session as the tab group title, --session-color, and the two ways to detach.

@github-actions

Copy link
Copy Markdown
Contributor

Test results for "MCP"

3 failed
❌ [chrome] › mcp/crash.spec.ts:31 › crash recovery › reports the navigation error, then resets and logs the crash @mcp-ubuntu-latest-chrome
❌ [chrome] › mcp/crash.spec.ts:58 › crash recovery › lists only one tab @mcp-ubuntu-latest-chrome
❌ [chrome] › mcp/crash.spec.ts:79 › crash recovery › marks non-current crashed tab in the tab list @mcp-ubuntu-latest-chrome

5232 passed, 631 skipped


Merge workflow run.

@microsoft-playwright-automation

Copy link
Copy Markdown
Contributor

🟢 All three failures are pre-existing

Hi, I'm the Playwright bot. I checked the failures: the same three tests fail with the same errors on main, without this PR's changes.

Details

Covers MCP run 43314158708 at 2665c0a423c4efd7d3f24025e532b825b6480190, as reported in the merged test report.

The changes affect CLI detach handling, extension tests and documentation. These crash tests start the MCP server directly, not the CLI daemon, and never call detach --close-tabs.

Pre-existing flake / infra

All three failures also occur in the Chrome job on main, at 8882d1c85ef808500d99a2e28778e544c8a77fef, before this PR's run:

  • mcp/crash.spec.ts:31 — reports the navigation error, then resets and logs the crash: the same 30-second timeout at toPass() while waiting for crash recovery.
  • mcp/crash.spec.ts:58 — lists only one tab: the same 30-second timeout and Error: Not connected at the subsequent browser_tabs call.
  • mcp/crash.spec.ts:79 — marks non-current crashed tab in the tab list: the same 30-second timeout and Error: Not connected at the subsequent browser_tabs call.

This proves the failures predate the PR; it does not establish whether they are intermittent. No fix in this PR is indicated.

Checked the failures on Linux by the Playwright bot - agent run

@pavelfeldman
Pavel Feldman (pavelfeldman) merged commit fb10ea7 into microsoft:main Nov 12, 2026
10 of 11 checks passed
Pavel Feldman (pavelfeldman) pushed a commit to microsoft/playwright-cli that referenced this pull request Nov 18, 2026
## ✨ Highlights

- **🗂️ Identify and resume your extension sessions**
([#496](#496)) —
`playwright-cli attach --extension=chrome --session=docs-review
--session-color=blue` labels the tab group with your session name
instead of a truncated product name. Disconnected groups remain
available to select on the next connection. Use `--no-tab-group` to
leave your existing tab organization alone.
([microsoft/playwright#44047](microsoft/playwright#44047))
- **🧹 Close an agent's tabs when its work is done** — `playwright-cli
-s=docs-review detach --close-tabs` closes that extension session's tabs
before disconnecting. Plain `detach` still leaves the tabs open for
later.
([microsoft/playwright#44084](microsoft/playwright#44084))
- **🖥️ Install stable Chrome on Linux ARM64**
([microsoft/playwright#43998](microsoft/playwright#43998))
— `playwright-cli install-browser chrome` now installs Google's ARM64
Debian package instead of rejecting the architecture.
([microsoft/playwright#44020](microsoft/playwright#44020))

## 🐛 Fixes

- `fix(server): do not reveal the endpoint path over HTTP` — attaching
to a Playwright browser server with `--endpoint` now requires its full
`ws://` or `wss://` endpoint, including the path; HTTP endpoint
discovery has been removed. HTTP URLs for `--cdp` are unaffected.
([microsoft/playwright#44190](microsoft/playwright#44190))
- `fix(mcp): do not wait for busy pages longer than 10s when connecting
over CDP` — a busy existing tab no longer blocks `playwright-cli attach
--cdp=http://localhost:9222` indefinitely. Pages that cannot initialize
within 10 seconds are made available later when they respond.
([microsoft/playwright#44052](microsoft/playwright#44052),
[microsoft/playwright#44105](microsoft/playwright#44105))
- `fix(cli): suggest matching ffmpeg installer for video recording` —
when `video-start` needs ffmpeg, its error now recommends
`playwright-cli install-browser ffmpeg`, which installs the revision
used by the CLI.
([#540](#540),
[microsoft/playwright#44088](microsoft/playwright#44088))
- `fix(mcp): validate run-code input` — `playwright-cli run-code`
without code or `--filename` reports a clear input error instead of an
internal `TypeError`.
([microsoft/playwright#44080](microsoft/playwright#44080),
[microsoft/playwright#44087](microsoft/playwright#44087))
- `fix(locator): select among visible elements in first/last/nth with
locateOnlyVisible` — with `browser.contextOptions.locateOnlyVisible`
enabled, locators used in `run-code` apply `first()`, `last()` and
`nth()` to visible matches instead of selecting a hidden element and
finding nothing. Explicit visibility filters still take precedence.
([microsoft/playwright#43855](microsoft/playwright#43855),
[microsoft/playwright#44083](microsoft/playwright#44083))
- `fix(chromium): apply timezone to service workers` — Chromium service
workers honor `browser.contextOptions.timezoneId` from their first
statement, keeping date handling consistent with pages.
([microsoft/playwright#43983](microsoft/playwright#43983),
[microsoft/playwright#44021](microsoft/playwright#44021))
- `fix(tracing): hold dropped screencast frames while throttling` —
recording with `playwright-cli tracing-start` uses less browser CPU on
idle animated pages without changing the frames kept in the trace.
([microsoft/playwright#44053](microsoft/playwright#44053),
[microsoft/playwright#44068](microsoft/playwright#44068))
- `fix(trace-viewer): harden snapshot rendering` — Trace Viewer blocks
navigation and form submission from recorded snapshots. Trace-file
routes also reject frame navigations, and its server checks WebSocket
origins.
([microsoft/playwright#44177](microsoft/playwright#44177),
[microsoft/playwright#44178](microsoft/playwright#44178))

## 📦 Upgrading

Node.js 20 or newer is required.

```bash
npm install -g @playwright/cli@0.1.25
```

Co-authored-by: microsoft-playwright-automation[bot] <203992400+microsoft-playwright-automation[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants