Skip to main content

Connect GitHub to Raycast

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

Set up

Add GitHub to Raycast in four steps

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

  1. 1

    Approve GitHub in Runlayer

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

  2. 2

    Connect Raycast to Runlayer

    Users add the Runlayer Plugin to Raycast by following Runlayer’s setup guide. Raycast reaches GitHub’s 100 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Raycast setup guide
  3. 3

    Sign in to GitHub

    Each user signs in to GitHub with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use GitHub from Raycast

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

Tools

100 GitHub tools in Raycast

Runlayer policy decides which of these Raycast users can call.

  • Get actions

    Get details about specific GitHub Actions resources.

  • List actions

    Tools for listing GitHub Actions resources.

  • Actions run trigger

    Trigger GitHub Actions workflow operations, including running, re-running, cancelling workflow runs, and deleting workflow run logs.

  • Add comment to pending review

    Add review comment to the requester's latest pending pull request review.

  • Add issue comment

    Add a comment and/or reaction to a specific issue or issue comment in a GitHub repository.

  • Add reply to pull request comment

    Add a reply and/or reaction to an existing pull request comment.

  • Assign copilot to issue

    Assign Copilot to a specific issue in a GitHub repository.

  • Assign copilot to issue with intent

    Assign Copilot to a specific issue in a GitHub repository.

See all 100 GitHub tools

Control

What Runlayer can see and stop in Raycast

Some controls apply to every client at the gateway. Others depend on what Raycast exposes to Runlayer.

  • Gateway policy (available)

    Every GitHub call from Raycast passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Raycast as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for Raycast yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination