feat(dashboard): add show --pick-locator secondary entrypoint#40336
feat(dashboard): add show --pick-locator secondary entrypoint#40336Skn0tt wants to merge 4 commits into
Conversation
Adds `cli show --pick-locator` as a dashboard-centric alternative to `cli pick`. The dashboard daemon switches into pick-locator mode and the picked ref/locator is written back to the CLI process. Existing BrowserContext.PickLocator event and browser_pick_locator MCP tool are unchanged.
Collapses the parallel `triggerAnnotate`/`registerAnnotateWaiter`/ `triggerPickLocator`/`registerPickLocatorWaiter` flows in the dashboard daemon into a single `elicit(kind, socket)` API serialized via a promise queue. Also drops the dashboard-side `pickLocator` channel method now that the daemon owns the entry point.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
pavelfeldman
left a comment
There was a problem hiding this comment.
There was a couple of old 'pick' tests (port them?) and the old tool (remove it?)
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
@copilot resolve the merge conflicts in this pull request |
Signed-off-by: Pavel Feldman <pavel.feldman@gmail.com>
Test results for "MCP"39 failed 6523 passed, 913 skipped Merge workflow run. |
Test results for "tests 1"5 flaky41265 passed, 847 skipped Merge workflow run. |
|
superceded by #40344 |
Summary
cli show --pick-locatoras a dashboard-centric alternative tocli pick.elicit(kind, socket)API serialized via a promise queue.pickLocatorchannel method now that the daemon owns the entry point.I wasn't yet able to drop the
context.on('pickLocator')event because it's unclear how MCP calls into show.