Skip to main content
Book a demo

Connect AirOps to Windsurf

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

Book a demo Windsurf setup guide

Set up

Add AirOps to Windsurf in four steps

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

  1. 1

    Approve AirOps in Runlayer

    Add AirOps 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 AirOps’s 100 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Windsurf setup guide
  3. 3

    Sign in to AirOps

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

  4. 4

    Use AirOps from Windsurf

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

Tools

100 AirOps tools in Windsurf

Runlayer policy decides which of these Windsurf users can call.

  • Accept opportunity

    Accept pending opportunities for a campaign and add them to the campaign action grid.

  • Add AEO region

    Add a region (ISO alpha-2 country code) to a Brand Kit's configured AEO regions.

  • Add grid column

    Add a new column to a grid table.

  • Analytics chart

    Query analytics data and display it as an interactive chart.

  • Automated feedback report

    AirOps only feedback tool.

  • Bulk update AEO prompt tags

    Apply a single tag operation (add or remove) to a batch of AEO prompts in one Brand Kit, atomically.

  • Bulk update AEO prompt topics

    Reassign a batch of AEO prompts to an existing topic in one Brand Kit.

  • Commit AEO prompt assignments

    Commit the current prompt-assignment draft for a Brand Kit to live.

See all 100 AirOps 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 AirOps 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