Skip to main content
Book a demo

Connect Hex to Windsurf

Give Windsurf governed access to Hex’s 18 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Windsurf setup guide

Set up

Add Hex to Windsurf in four steps

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

  1. 1

    Approve Hex in Runlayer

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

  2. 2

    Connect Windsurf to Runlayer

    Users add the Runlayer Plugin to Windsurf by following Runlayer’s setup guide. Windsurf reaches Hex’s 18 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Windsurf setup guide
  3. 3

    Sign in to Hex

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

  4. 4

    Use Hex from Windsurf

    Hex’s approved tools appear in Windsurf. Every call is checked against policy and recorded.

Tools

18 Hex tools in Windsurf

Runlayer policy decides which of these Windsurf users can call.

  • Continue thread

    Continue a Hex Thread by adding a new message and triggering the agent to process it.

  • Create cell

    Create a new cell in the draft version of a project.

  • Create project

    Create a new project in the workspace with the specified title, and optionally a description.

  • Create thread

    Create a new Hex Thread to ask a question about your data.

  • Delete cell

    Delete a cell from the draft version of a project by ID

  • Get cell

    Get a single cell by ID

  • Get cell image

    Get the rendered PNG image of a chart cell, returned as an image.

  • Get cell output

    Get the latest output preview for a SQL cell in the active draft notebook session.

See all 18 Hex tools

Control

What Runlayer can see and stop in Windsurf

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

  • Gateway policy (available)

    Every Hex call from Windsurf passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Windsurf 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 Windsurf runs it.

  • Block output after it runs (not available)

    Windsurf ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Windsurf has no way to receive replacement output, so Runlayer cannot mask it. The gateway still applies policy to the call.

In Windsurf

  • Enforcement needs Windsurf 1.12.31 or newer.
  • When Runlayer denies a call, Windsurf shows the reason to the user; Runlayer cannot adjust the call’s inputs.

Frequently asked questions

Connect more

Find another combination