Connect Statsig to Windsurf
Give Windsurf governed access to Statsig’s 93 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Statsig to Windsurf in four steps
Admins approve the server once. Everyone in Windsurf then gets it through the same governed connection.
- 1
Approve Statsig in Runlayer
Add Statsig from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Windsurf to Runlayer
Users add the Runlayer Plugin to Windsurf by following Runlayer’s setup guide. Windsurf reaches Statsig’s 93 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Windsurf setup guide - 3
Sign in to Statsig
Sign in the way Statsig requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Statsig from Windsurf
Statsig’s approved tools appear in Windsurf. Every call is checked against policy and recorded.
Tools
93 Statsig tools in Windsurf
Runlayer policy decides which of these Windsurf users can call.
Approve autotune review
Approve an in-flight review of an autotune experiment.
Approve dynamic config review
Approve an in-flight review of a dynamic config.
Approve experiment review
Approve an in-flight review of an experiment (A/B test).
Approve gate review
Approve an in-flight review of a gate (feature flag).
Cancel autotune review
Cancel (withdraw) an in-flight review of an autotune experiment.
Cancel dynamic config review
Cancel (withdraw) an in-flight review of a dynamic config.
Cancel experiment review
Cancel (withdraw) an in-flight review of an experiment (A/B test).
Cancel gate review
Cancel (withdraw) an in-flight review of a gate (feature flag).
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 Statsig 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