Connect Exa to GitHub Copilot
Give GitHub Copilot governed access to Exa’s 3 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Exa 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 Exa in Runlayer
Add Exa 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 Exa’s 3 tools through the plugin’s search and execute tools.
GitHub Copilot setup guide - 3
Sign in to Exa
Sign in the way Exa requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Exa from GitHub Copilot
Exa’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.
Tools
3 Exa tools in GitHub Copilot
Runlayer policy decides which of these GitHub Copilot users can call. 1 read data only.
Agent run
Start or resume an Exa Agent run for multi-step research, list-building, or enrichment.
Web fetch Exa
Read a webpage's full content as clean markdown.
Web search Exa
Search the web for any topic and get clean, ready-to-use content.
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 Exa 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