← Integracje

Chrome DevTools with OHarness

  • Wtyczka
  • Narzędzia deweloperskie

Drive Chrome to debug pages, network requests and performance. OHarness works with Chrome DevTools out of the box.

Ta strona jest napisana po angielsku. Terminy, które wyjaśnia, są tymi, których szuka się po angielsku, a przetłumaczony termin fachowy to już inny termin.

What you get

Plugin7 skills and 1 MCP server. MCP servers: chrome-devtools.
Published byGoogle Chrome
Pinned sourceChromeDevTools/chrome-devtools-mcp@a878bca

How it signs in

The plugin itself needs no sign-in: its skills and agents are text the agent reads when they are relevant. The MCP servers it names connect the way any connector does — through the browser, or with a key the vendor's own setup asks for.

Try it

Once Chrome DevTools is connected, a first prompt to see it work:

Use Chrome DevTools to look into the bug in this branch and propose a fix with a test.

Adding it

  1. Download OHarness for the Mac, or install the CLI anywhere Node runs.
  2. In the composer, open the + menu and find Chrome DevTools under Plugins.
  3. Install it. The skills are there for every session in the project from then on.

Links

Common questions

Does OHarness work with Chrome DevTools?

Yes. Chrome DevTools ships in OHarness as a plugin, so it is in the menu on first launch with nothing to look up.

What does the Chrome DevTools plugin install?

7 skills and 1 MCP server. It is installed from ChromeDevTools/chrome-devtools-mcp at commit a878bca, the exact version OHarness was checked against, rather than whatever is on a branch today.

Is OHarness affiliated with Google Chrome?

No. OHarness works with Chrome DevTools through its public plugin; Chrome DevTools and its logo belong to Google Chrome.

More in developer tools

Code simplifier · Context7 · DeepWiki · Feature development · Frontend design · GitHub

Chrome DevTools and its logo belong to Google Chrome. Listed because OHarness works with it, not because Google Chrome endorses OHarness.

Use Chrome DevTools from OHarness

The same Chrome DevTools tools in every session, whichever of the model providers is underneath.