ChromeDevTools / ChromeDevTools/chrome-devtools-mcp
Replace individual input tools with a WebDriver-like API
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 52.3k
- Forks
- 4.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 83
Description
Is your feature request related to a problem? Please describe.
Currently, we have hover, click and press_key tools which are rather low level and to send multiple of them the client needs to be able to issue multiple tool calls (which might involve multiple LLM round trips). In addition, we support some low level input commands but not all like the perform_actions API.
Describe the solution you'd like
WebDriver defines the perform actions API https://www.w3.org/TR/webdriver-bidi/#command-input-performActions that allows sending a sequence of actions in one tool call. We can replace our existing low level APIs with an API similar to WebDriver (but integrated with our other concepts like uids). We should not replace higher level APIs though, like fill, fill_form, drag.
Describe alternatives you've considered
Current approach.
Additional context
We need to test if the models have any difficulties using the WebDriver like API.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing hover, click, and press_key tools and the linked WebDriver perform actions specification. Work out the proposed action sequence API, including how it integrates with uids while preserving higher-level tools such as fill, fill_form, and drag; done means the low-level input use cases can be sent in one call and the API can be tested with models.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100