Connect Cloudflare Browser Rendering to GitHub Copilot
Give GitHub Copilot governed access to Cloudflare Browser Rendering through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Cloudflare Browser Rendering to GitHub Copilot in four steps
Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.
- 1
Approve Cloudflare Browser Rendering in Runlayer
Add Cloudflare Browser Rendering from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect GitHub Copilot to Runlayer
GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Cloudflare Browser Rendering’s tools through the plugin’s search and execute tools.
GitHub Copilot setup guide - 3
Sign in to Cloudflare Browser Rendering
Sign in the way Cloudflare Browser Rendering requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Cloudflare Browser Rendering from GitHub Copilot
Cloudflare Browser Rendering’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.
Tools
Cloudflare Browser Rendering tools in GitHub Copilot
Cloudflare Browser Rendering reports its tools when your organization connects it, so the list depends on your deployment.
Control
What Runlayer can see and stop in GitHub Copilot
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot exposes to Runlayer.
Gateway policy (available)
Every Cloudflare Browser Rendering call from GitHub Copilot passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, GitHub Copilot as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.
Frequently asked questions
Connect more