Skip to main content
Book a demo

Connect Lucid to GitHub Copilot CLI

Give GitHub Copilot CLI governed access to Lucid’s 42 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo GitHub Copilot CLI setup guide

Set up

Add Lucid 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. 1

    Approve Lucid in Runlayer

    Add Lucid from the catalog and choose who can use it and which of its tools are allowed.

  2. 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 Lucid’s 42 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    GitHub Copilot CLI setup guide
  3. 3

    Sign in to Lucid

    Sign in the way Lucid requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Lucid from GitHub Copilot CLI

    Lucid’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.

Tools

42 Lucid tools in GitHub Copilot CLI

Runlayer policy decides which of these GitHub Copilot CLI users can call. 2 read data only.

  • Create embed

    Internal tool for MCP Apps extension only.

  • Create embed session token

    Internal tool for MCP Apps extension only.

  • Exchange legacy embed session

    Internal tool for MCP Apps extension only.

  • Fetch Lucid document content

    Retrieves the structured content of a specific Lucid document by its ID.

  • Get MCP resource

    Reads a resource from this MCP server by URI.

  • List document thread comments

    List comments on a specific collaboration thread of a Lucid document.

  • List document threads

    List collaboration threads on a Lucid document.

  • Add block

    Add a new block (shape) to a Lucid document.

See all 42 Lucid tools

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 Lucid 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

Find another combination