Connect GitHub to Goose
Give Goose governed access to GitHub’s 100 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add GitHub to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Approve GitHub in Runlayer
Add GitHub from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Goose to Runlayer
Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches GitHub’s 100 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to GitHub
Each user signs in to GitHub with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use GitHub from Goose
GitHub’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
100 GitHub tools in Goose
Runlayer policy decides which of these Goose 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.
Control
What Runlayer can see and stop in Goose
Some controls apply to every client at the gateway. Others depend on what Goose exposes to Runlayer.
Gateway policy (available)
Every GitHub call from Goose passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Goose 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 before Goose runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Goose’s model sees it.
Redact output in place (not available)
Goose cannot apply masking, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.
Frequently asked questions
Connect more