-
MCP sessions work like the CLI: the MCP now runs code in relay sessions. MCP tabs belong to their session, survive relay upgrades and show in
playwriter session list. Cancelling a tool call in the client stops the running execute. New MCP tools:session_list: active sessions and the browsers a new session can usesession_new: pick a browser key,headless,cloud(with proxy options),directCDP or aremotecontrol id, pluspatchrightandtabGroupsession_update: switchpatchrightor the tab groupsession_delete: delete a session, optionally closing its tabs
executeandresettake an optionalsession. Without it they use a default session, created on first use when one browser is connected.Breaking: the MCP no longer reads
PLAYWRITER_DIRECT, andplaywriter --patchrightis removed. Usesession_newwithdirectorpatchrightinstead. -
Clients cannot open Playwriter's extension pages:
Target.createTargetandpage.goto()could openchrome-extension://<playwriter id>/...pages, and code there had the extension's privileges. The extension now rejects these URLs withPlaywriter clients cannot open extension pages.Extension pages are also removed from an attached tab's back/forward history. Needs extension 0.0.175. -
Hardened local relay:
- Websites can no longer start or stop a skill recording with a cross-origin
POSTto/recorder/*. Privileged routes check the exactapplication/jsonmedia type. playwriter serve --hostwith any non-loopback address, for example a LAN IP, now requires--token.~/.playwriteris0700, andrelay-server.logandcdp.jsonlare0600.cdp.jsonlredactsCookie,Set-Cookie,Authorizationand cookie results.- Relay tokens are compared in constant time, and the Chrome for Testing zip downloads to a private temp folder.
- Websites can no longer start or stop a skill recording with a cross-origin
-
Clearer Patchright guidance for agents: the skill tells agents to use
--patchrighton every production site where you are logged in, and never on localhost or the site being built in the current project.