ChromeDevTools / ChromeDevTools/chrome-devtools-mcp
can we add a download folder to config for automating some download task.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 52.3k
- Forks
- 4.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 83
Description
while run automated download task, using default download folder can sometimes be annoying. It is better to add download folder to config so we can go to this specific download folder for files downloaded. Thanks. To run a chrome mannualy from command line can also do this.
I don't know if Chrome DevTools can access the download list and if yes, add a tool to get download history could be more direct to handle automation.
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 locating the configuration and Chrome command-line or automation entry points that control downloaded files, then check whether Chrome DevTools exposes download history. Done means the requested download folder can be configured for automated downloads, with the separate history-tool idea clarified or scoped independently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100