Skip to main content
Book a demo

Connect LaunchDarkly to Claude Code

Give Claude Code governed access to LaunchDarkly’s 141 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude Code setup guide

Set up

Add LaunchDarkly to Claude Code in four steps

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

  1. 1

    Approve LaunchDarkly in Runlayer

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

  2. 2

    Connect Claude Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Claude Code, and an Anthropic org install also reaches Claude Code. With direct tool listing turned on for your deployment, LaunchDarkly’s 141 tools show up in Claude Code’s own tool list (supported Claude Code versions).

    Claude Code setup guide
  3. 3

    Sign in to LaunchDarkly

    An admin adds LaunchDarkly credentials to Runlayer once. They never sit in the client’s configuration.

  4. 4

    Use LaunchDarkly from Claude Code

    LaunchDarkly’s approved tools appear in Claude Code. Every call is checked against policy and recorded.

Tools

141 LaunchDarkly tools in Claude Code

Runlayer policy decides which of these Claude Code users can call.

  • Apply agentcontrol config approval

    Apply an already-approved AgentControl Config approval request.

  • Apply approval request

    Apply an already-approved flag approval request.

  • Archive flag

    Archive a feature flag (reversible).

  • Check flag rollout complete

    Check whether a feature flag is fully rolled out to a single deterministic variation across all traffic-bearing environments.

  • Check removal readiness

    Detailed safety check before removing a feature flag.

  • Clone agentcontrol config variation

    Clone an existing AgentControl Config variation with selective overrides.

  • Copy flag config

    Copy a flag's targeting configuration from one environment to another.

  • Create agent graph

    Create a new agent graph in a project.

See all 141 LaunchDarkly tools

Control

What Runlayer can see and stop in Claude Code

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

  • Gateway policy (available)

    Every LaunchDarkly call from Claude Code passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Claude Code 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.

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude Code prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • OTLP telemetry (available)

    Claude Code can export OpenTelemetry logs to Runlayer for observe-only session reconstruction.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Claude Code runs it.

  • Block output after it runs (available)

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

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in Claude Code and pass the rest through.

In Claude Code

  • When a tool fails, Runlayer records the error but cannot hide it.

Frequently asked questions

Connect more

Find another combination