Connect Pigment to GitHub Copilot CLI
Give GitHub Copilot CLI governed access to Pigment’s 101 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Pigment 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 Pigment in Runlayer
Add Pigment 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 Pigment’s 101 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
GitHub Copilot CLI setup guide - 3
Sign in to Pigment
Sign in the way Pigment requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Pigment from GitHub Copilot CLI
Pigment’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.
Tools
101 Pigment tools in GitHub Copilot CLI
Runlayer policy decides which of these GitHub Copilot CLI users can call.
Add list items
Add one or more new items (rows) to a dimension/list with their property values in a single operation.
Batch share blocks
Share multiple lists and metrics in a single operation, making them visible and usable across applications within the organization.
Calendar add time dimension
Add a new time dimension to existing Application calendar.
Create calendar
Creates a new gregorian calendar in the Pigment application.
Calendar expand
Expands or shrinks a calendar's date range.
Get calendar
Retrieves detailed configuration of a specific calendar.
Calendar remove time dimension
Remove a time dimension from the Application's calendar.
Clear widget preview
Removes the Draft View preview from a single Board widget for the current user, so the widget shows its saved View again.
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 Pigment 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