Skip to content

fix: include the tab id in get_tab_id's text response#2381

Merged
OrKoN merged 1 commit into
ChromeDevTools:mainfrom
thomasbachem:fix/get-tab-id-text-output
Jul 20, 2026
Merged

fix: include the tab id in get_tab_id's text response#2381
OrKoN merged 1 commit into
ChromeDevTools:mainfrom
thomasbachem:fix/get-tab-id-text-output

Conversation

@thomasbachem

Copy link
Copy Markdown
Contributor

As discussed in #2366: get_tab_id gates on --experimentalInteropTools, but its result only went into structuredContent, which is dropped unless --experimentalStructuredContent is also set – so with interop alone the tool always returned an empty text response.

This appends a Tab ID: <id> line to the text response and keeps structuredContent.tabId as-is – key: value so it stays trivially parseable.

Testing

The existing returns the tab id test asserted empty responseLines, which pinned the old behavior – now it asserts the Tab ID: line. Verified end-to-end over stdio with --experimentalInteropTools alone: the text response is Tab ID: <id> where it was "" before.

@thomasbachem thomasbachem changed the title fix: include the tab id in get_tab_id's text response fix: include the tab id in get_tab_id's text response Jul 16, 2026
`get_tab_id` gates on `--experimentalInteropTools`, but its result only
went into `structuredContent`, which is dropped unless
`--experimentalStructuredContent` is also set – with interop alone the
tool always returned an empty text response.

Append a `Tab ID: <id>` line to the text response, keeping
`structuredContent.tabId` as-is.
@thomasbachem
thomasbachem force-pushed the fix/get-tab-id-text-output branch from 417555a to ea51275 Compare July 16, 2026 20:06

@OrKoN OrKoN left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Thanks!

@OrKoN
OrKoN added this pull request to the merge queue Jul 20, 2026
Merged via the queue into ChromeDevTools:main with commit dcbaf49 Jul 20, 2026
19 checks passed
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