Skip to content

feat(extension): let an MCP client label its own tab group - #42360

Open
Yury Semikhatsky (yury-s) wants to merge 1 commit into
microsoft:mainfrom
yury-s:fix-41840
Open

feat(extension): let an MCP client label its own tab group#42360
Yury Semikhatsky (yury-s) wants to merge 1 commit into
microsoft:mainfrom
yury-s:fix-41840

Conversation

@yury-s

Copy link
Copy Markdown
Member

Summary

  • New browser_set_group_label MCP tool (listed in --extension mode only) and matching tab-group-label CLI command: renames the connection's own Chrome tab group to Playwright · <label>, deduplicated with a (2), (3)... suffix against other active connections.
  • New session-level extension.setGroupLabel relay command, no protocol version bump; older extensions produce a clear "update the extension" error. A connection can only relabel its own group.

Fixes #41840

Adds a browser_set_group_label tool and a matching tab-group-label CLI
command, available in --extension mode, that rename the connection's own
Chrome tab group to "Playwright · <label>", deduplicated against the
other active connections' groups.

Fixes: microsoft#41840
@github-actions

Copy link
Copy Markdown
Contributor

Test results for "MCP"

8142 passed, 1361 skipped


Merge workflow run.

}

private _takenGroupStyles(exclude?: ConnectedTabGroup): GroupStyle[] {
return [...this._connections.values()].filter(group => group !== exclude).map(group => group.groupStyle);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NIT: you could do this to avoid an extra iteration

Suggested change
return [...this._connections.values()].filter(group => group !== exclude).map(group => group.groupStyle);
return Array.from(this._connections.values(), group => group.groupStyle).filter(group => group !== exclude);

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.

Proposal: let an MCP client label its own tab group (browser_set_group_label)

2 participants