Skip to main content
Book a demo

Connect Chrome DevTools to Goose

Give Goose governed access to Chrome DevTools’s 26 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Goose setup guide

Set up

Add Chrome DevTools to Goose in four steps

Admins approve the server once. Everyone in Goose then gets it through the same governed connection.

  1. 1

    Approve Chrome DevTools in Runlayer

    Add Chrome DevTools from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Goose to Runlayer

    Install the Runlayer CLI so Goose can reach Chrome DevTools, which runs on the user’s machine. Auto Sync can then write Chrome DevTools into Goose on macOS, Windows, and Linux.

    Goose setup guide
  3. 3

    Sign in to Chrome DevTools

    Sign in the way Chrome DevTools requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Chrome DevTools from Goose

    Chrome DevTools’s approved tools appear in Goose. Every call is checked against policy and recorded.

Tools

26 Chrome DevTools tools in Goose

Runlayer policy decides which of these Goose users can call. 10 read data only.

  • Click

    Clicks on the provided element

  • Close page

    Closes the page by its index.

  • Drag

    Drag an element onto another element

  • Emulate

    Emulates various features on the selected page.

  • Evaluate script

    Evaluate a JavaScript function inside the currently selected page.

  • Fill

    Type text into a input, text area or select an option from a element.

  • Fill form

    Fill out multiple form elements at once

  • Get console message

    Gets a console message by its ID.

See all 26 Chrome DevTools tools

Control

What Runlayer can see and stop in Goose

Some controls apply to every client at the gateway. Others depend on what Goose exposes to Runlayer.

  • Gateway policy (available)

    Every Chrome DevTools call from Goose passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Goose as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Goose runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Goose’s model sees it.

  • Redact output in place (not available)

    Goose cannot apply masking, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination