Connect Skyvern to GitHub Copilot CLI
Give GitHub Copilot CLI governed access to Skyvern’s 77 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Skyvern to GitHub Copilot CLI in four steps
Admins approve the server once. Everyone in GitHub Copilot CLI then gets it through the same governed connection.
- 1
Approve Skyvern in Runlayer
Add Skyvern from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect GitHub Copilot CLI to Runlayer
Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches Skyvern’s 77 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
GitHub Copilot CLI setup guide - 3
Sign in to Skyvern
Sign in the way Skyvern requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Skyvern from GitHub Copilot CLI
Skyvern’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.
Tools
77 Skyvern tools in GitHub Copilot CLI
Runlayer policy decides which of these GitHub Copilot CLI users can call. 34 read data only and 11 can change or delete data.
Create browser session
Create a new browser session to start interacting with websites.
Close browser session
Close a browser session when you're done.
List browser sessions
List all active browser sessions.
Get browser session
Get details about a specific browser session -- status, timeout, availability.
Connect to browser session
Connect to an existing browser -- a cloud session by ID or any browser via CDP URL.
Perform browser action (ai)
Perform actions on a page by describing what to do in plain English.
Extract data from page (ai)
Extract structured data from the current page using AI with screenshots and a dedicated extraction LLM.
Validate page condition (ai)
Check if a condition is true on the current page — cheapest AI option for yes/no questions.
Control
What Runlayer can see and stop in GitHub Copilot CLI
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot CLI exposes to Runlayer.
Gateway policy (available)
Every Skyvern call from GitHub Copilot CLI 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 CLI 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 or permission request before GitHub Copilot CLI runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.
In GitHub Copilot CLI
- When a tool fails, Runlayer records the error but cannot replace it.
Frequently asked questions
Connect more