Playwright extension debug button hangs with grey spinner

[IvanQL]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

win32

Kiro Version

0.11.133

Bug Description

Test server starts (test-server -c playwright.config.ts) but no test is dispatched
"Run" works fine, only "Debug" is broken
Same setup works correctly in VS Code
Started happening after the latest Kiro update

Steps to Reproduce

1. Open any Playwright project in Kiro with the Playwright Test for VS Code extension installed
2. Open the Testing sidebar (flask icon)
3. Locate any test (API or UI)
4. Click the "Debug" button (bug icon) next to a test
5. Observe the Debug Console output

Actual result:
The Debug Console shows the test server starting successfully: C:\Program Files\nodejs\node.exe node_modules@playwright\test\cli.js test-server -c playwright.config.ts Listening on ws://127.0.0.1:XXXXX/...
A grey spinner appears next to the test in the Testing sidebar
The test never actually runs — the server sits idle waiting for a command that never arrives
The spinner stays indefinitely until manually cancelled

Expected Behavior

Expected Result: The test server starts, the debugger attaches, and the selected test executes with breakpoints active.

Conversation ID

2dec4960-da83-4ea9-ad05-197ae5fd6bd0
2dec4960-da83-4ea9-ad05-197ae5fd6bd0
2dec4960-da83-4ea9-ad05-197ae5fd6bd0
2dec4960-da83-4ea9-ad05-197ae5fd6bd0

Additional Context

No response

[github-actions]

Thanks for opening this issue and providing such detailed reproduction steps! We can see that the Playwright extension's debug functionality is hanging after the test server starts, with the test never actually being dispatched — especially frustrating since it works fine in VS Code and the "Run" button works as expected. A maintainer will take a look at this shortly. We appreciate you helping us improve Kiro! 🙌

[IvanQL]

Rollback to Kiro Version 0.11.132 is a temporary workaround for this issue

[AnilMaktala]

Duplicate of #7820 — Playwright debug button hanging is tracked there.

Closing as duplicate.

[IvanQL]

@AnilMaktala Thanks for your response. I hope the issue will be resolved. One small thing I'm a bit confused about: how could issue ID 7781 (created earlier) be a duplicate of ID 7820 (created later)? But anyway, thanks for your support!