Skip to main content
Book a demo

Connect Hugeicons to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

Add Hugeicons 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 Hugeicons in Runlayer

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

  2. 2

    Connect GitHub Copilot to Runlayer

    GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Hugeicons’s 5 tools through the plugin’s search and execute tools.

    GitHub Copilot setup guide
  3. 3

    Sign in to Hugeicons

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

  4. 4

    Use Hugeicons from GitHub Copilot

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

Tools

5 Hugeicons tools in GitHub Copilot

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

  • List icons

    Get a list of all available Hugeicons icons

  • Search icons

    Search for icons by name or tags.

  • Get platform usage

    Get platform-specific usage instructions for Hugeicons

  • Get icon glyphs

    Get all glyphs (unicode characters) for a specific icon across all available styles

  • Get icon glyph by style

    Get the glyph (unicode character) for a specific icon with a particular style

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