Connect Nimble to GitHub Copilot CLI
Give GitHub Copilot CLI governed access to Nimble’s 27 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Nimble 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 Nimble in Runlayer
Add Nimble 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 Nimble’s 27 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
GitHub Copilot CLI setup guide - 3
Sign in to Nimble
Sign in the way Nimble requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Nimble from GitHub Copilot CLI
Nimble’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.
Tools
27 Nimble tools in GitHub Copilot CLI
Runlayer policy decides which of these GitHub Copilot CLI users can call. 16 read data only and 5 can change or delete data.
Nimble crawl run
Nimble Crawl: one-time bulk fetch of a known doc tree or URL list.
Nimble crawl status
Check the status and progress of a running or completed crawl job.
Nimble crawl list
List crawl jobs, optionally filtered by status.
Nimble crawl terminate
Cancel a running or queued crawl job.
List extraction templates
Browse Extraction Templates — reusable, site-specific structured scrapers.
Get extraction template
Get an Extraction Template's input/output schema before running it.
Run extraction template
Run an Extraction Template against 1–few known items (URL or site ID).
Generate extraction template
Generate a new Extraction Template — only when the user explicitly asks to.
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 Nimble 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