@guildai-services/guildai~github package provides agents with access to the GitHub REST API through Guild’s GitHub App integration.
The
@guildai-services/guildai~github package is available to every Guild workspace. Its tools and response schemas are generated from GitHub’s official OpenAPI specification, so tool names match GitHub’s REST API operation IDs — for example, github_pulls_get maps to the pulls_get operation.Authentication
- Type: GitHub App
- Token management: Generated on-demand and refreshed automatically
- Scoping: Limited to repositories where the Guild GitHub App is installed
Setup
1
Open Credentials
Go to Credentials in Guild.
2
Connect GitHub
Click GitHub and authorize the Guild app on your organization or repository.
3
Select repositories
Choose which repositories to grant access to.
Usage
Selecting specific tools
Agents perform better with fewer tools. Usepick() to include only what your agent needs. Tools are named with the github_ prefix — for example, pulls_get becomes github_pulls_get.
Trimming responses
GitHub API responses can be large. UseguildServiceTool() with githubSchemasLite to strip unnecessary fields before the LLM sees them.
API endpoints
Gists
Gists
Organizations
Organizations
Repositories
Repositories
Branches
Branches
Commits
Commits
Contents
Contents
Issues
Issues
Pull requests
Pull requests
Check runs
Check runs
Workflows & actions
Workflows & actions
Releases
Releases
Deployments
Deployments
Search
Search
Users
Users
Webhook events
GitHub uses an app-scoped webhook model — a single webhook receives all events and Guild routes them to matching triggers.
Guild preprocesses webhook payloads before passing them to agents, removing avatar URLs, permalink URLs, and deeply nested metadata to reduce payload size.
Limitations
- Access is scoped to repositories where the GitHub App is installed
- Rate limits follow GitHub’s standard limits (5,000 requests/hour for authenticated apps)