Skip to content

feat: add Claude plugin browser URL config#1851

Open
officialasishkumar wants to merge 4 commits into
ChromeDevTools:mainfrom
officialasishkumar:feat/plugin-browser-url-config
Open

feat: add Claude plugin browser URL config#1851
officialasishkumar wants to merge 4 commits into
ChromeDevTools:mainfrom
officialasishkumar:feat/plugin-browser-url-config

Conversation

@officialasishkumar
Copy link
Copy Markdown
Contributor

Summary

  • add a Claude plugin browserUrl user config option for connecting to a running debuggable Chrome instance
  • pass the option through to chrome-devtools-mcp with --browser-url, while a blank value keeps the default automatic Chrome launch behavior
  • document the Claude Code pluginConfigs settings shape for the plugin option

Fixes #1232

Testing

  • parsed .claude-plugin/plugin.json with JSON.parse
  • npm run check-format
  • npm run gen

@OrKoN
Copy link
Copy Markdown
Collaborator

OrKoN commented May 6, 2026

Thanks for the PR, we should implement the suggestion from #1981 (comment) to generate all configuration options.

Copy link
Copy Markdown
Collaborator

@OrKoN OrKoN left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should update the generator to generate the userConfig options as suggested in #1981 (comment)

@officialasishkumar officialasishkumar force-pushed the feat/plugin-browser-url-config branch from 85870eb to 0eca9b6 Compare May 11, 2026 05:51
@officialasishkumar
Copy link
Copy Markdown
Contributor Author

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.

Comment thread .claude-plugin/plugin.json Outdated
"chrome-devtools-mcp@latest"
]
],
"env": {
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I actually saw this in another PR #1981

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated this in 8b3a6e2: generated plugin user config now stays on CLI args, and the env-default path was removed.

@OrKoN OrKoN self-requested a review May 11, 2026 11:58
@officialasishkumar officialasishkumar force-pushed the feat/plugin-browser-url-config branch from 0eca9b6 to 8b3a6e2 Compare May 12, 2026 05:11
@OrKoN OrKoN force-pushed the feat/plugin-browser-url-config branch from 15ac743 to fd04ae4 Compare May 21, 2026 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Plugin mode: support --browserUrl via pluginConfigs

2 participants