feat: add Claude plugin browser URL config#1851
Conversation
|
Thanks for the PR, we should implement the suggestion from #1981 (comment) to generate all configuration options. |
OrKoN
left a comment
There was a problem hiding this comment.
We should update the generator to generate the userConfig options as suggested in #1981 (comment)
85870eb to
0eca9b6
Compare
|
Updated this to generate plugin userConfig from the CLI options and wire the generated values through env defaults, so browserUrl and future options are not maintained by hand. |
| "chrome-devtools-mcp@latest" | ||
| ] | ||
| ], | ||
| "env": { |
There was a problem hiding this comment.
I think we should keep using arguments for the configuration and do not introduce environment variables. I think the initial version of this PR used arguments.
There was a problem hiding this comment.
I think I actually saw this in another PR #1981
There was a problem hiding this comment.
Updated this in 8b3a6e2: generated plugin user config now stays on CLI args, and the env-default path was removed.
0eca9b6 to
8b3a6e2
Compare
15ac743 to
fd04ae4
Compare
Summary
browserUrluser config option for connecting to a running debuggable Chrome instancechrome-devtools-mcpwith--browser-url, while a blank value keeps the default automatic Chrome launch behaviorpluginConfigssettings shape for the plugin optionFixes #1232
Testing
.claude-plugin/plugin.jsonwithJSON.parsenpm run check-formatnpm run gen