Skip to main content
Book a demo

Connect shadcn/ui to GitHub Copilot

Give GitHub Copilot governed access to shadcn/ui’s 7 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo GitHub Copilot setup guide

Set up

Add shadcn/ui to GitHub Copilot in four steps

Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.

  1. 1

    Approve shadcn/ui in Runlayer

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

  2. 2

    Connect GitHub Copilot to Runlayer

    Install the Runlayer CLI so GitHub Copilot can reach shadcn/ui, which runs on the user’s machine.

    GitHub Copilot setup guide
  3. 3

    Sign in to shadcn/ui

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

  4. 4

    Use shadcn/ui from GitHub Copilot

    shadcn/ui’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.

Tools

7 shadcn/ui tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot users can call.

  • Get project registries

    Get configured registry names from components.json - Returns error if no components.json exists (use init_project to create one)

  • List items in registries

    List items from registries (requires components.json - use init_project if missing)

  • Search items in registries

    Search for components in registries using fuzzy matching (requires components.json).

  • View items in registries

    View detailed information about specific registry items including the name, description, type and files content.

  • Get item examples from registries

    Find usage examples and demos with their complete code.

  • Get add command for items

    Get the shadcn CLI add command for specific items in a registry.

  • Get audit checklist

    Make sure to run the tool after all required steps have been completed.

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 shadcn/ui 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

Find another combination