Connect Socket to OpenCode
Give OpenCode governed access to Socket’s 1 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Socket to OpenCode in four steps
Admins approve the server once. Everyone in OpenCode then gets it through the same governed connection.
- 1
Approve Socket in Runlayer
Add Socket from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect OpenCode to Runlayer
Install the Runlayer CLI so OpenCode can reach Socket, which runs on the user’s machine. Auto Sync can then write Socket into OpenCode on macOS, Windows, and Linux.
OpenCode setup guide - 3
Sign in to Socket
An admin adds Socket credentials to Runlayer once. They never sit in the client’s configuration.
- 4
Use Socket from OpenCode
Socket’s approved tools appear in OpenCode. Every call is checked against policy and recorded.
Tools
1 Socket tools in OpenCode
Runlayer policy decides which of these OpenCode users can call. 1 read data only.
Depscore
Query dependency security scores across npm, PyPI, cargo, and other package ecosystems.
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 Socket 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