Connect LaunchDarkly to OpenCode
Give OpenCode governed access to LaunchDarkly’s 141 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add LaunchDarkly to OpenCode in four steps
Admins approve the server once. Everyone in OpenCode then gets it through the same governed connection.
- 1
Approve LaunchDarkly in Runlayer
Add LaunchDarkly from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect OpenCode to Runlayer
Users add the Runlayer Plugin to OpenCode by hand using Runlayer’s generic MCP steps. OpenCode reaches LaunchDarkly’s 141 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
OpenCode setup guide - 3
Sign in to LaunchDarkly
An admin adds LaunchDarkly credentials to Runlayer once. They never sit in the client’s configuration.
- 4
Use LaunchDarkly from OpenCode
LaunchDarkly’s approved tools appear in OpenCode. Every call is checked against policy and recorded.
Tools
141 LaunchDarkly tools in OpenCode
Runlayer policy decides which of these OpenCode 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.
Control
What Runlayer can see and stop in OpenCode
Some controls apply to every client at the gateway. Others depend on what OpenCode exposes to Runlayer.
Gateway policy (available)
Every LaunchDarkly call from OpenCode passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, OpenCode as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for OpenCode yet, so control happens at the gateway.
Frequently asked questions
Connect more