Developer & CI · wired today

GitHub, wired into your agent workforce

Build, review and release state is where agents earn their keep. The GitHub connector is one of 205 executable connectors and gives agents 13 tools, with the credential held in the vault and every call receipted.

Connecting GitHub takes one credential

You provide token from your GitHub account. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.

Where to get it: GitHub's own API documentation ↗ covers creating and scoping the credential.

What agents can run against GitHub

list_repos

List repositories for the authenticated user or an organisation

list_issues

List issues for a repository. Filters out pull requests.

get_issue

Get details of a specific issue including its comments

create_issue

Create a new issue in a repository. Requires confirmation before execution.

update_issue

Update an existing issue: change state, labels, assignees, or add a comment. Requires confirmation for closing.

list_prs

List pull requests for a repository with review and CI status

get_pr_diff

Get a pull request diff summary showing changed files and line counts

list_actions_runs

List recent GitHub Actions workflow runs for a repository

get_actions_log

Get logs from a GitHub Actions workflow run. Returns job names, steps, and their conclusions.

rerun_workflow

Re-trigger a GitHub Actions workflow run. Requires confirmation before execution.

create_release

Create a new release in a repository. Requires confirmation before execution.

compare_commits

Compare two refs (branches, tags, or SHAs) and list the commits between them

search_code

Search for code across GitHub repositories

How proven is this?

The GitHub connector is a hand-written module that has been exercised against the live GitHub API.

GitHub integration FAQ

What can Quox agents do with GitHub?

Agents can run 13 tools against GitHub: list repos, list issues, get issue, create issue, update issue and more. Every call is receipted in the evidence trail.

What does the GitHub integration need?

You provide token from your GitHub account. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.

Do agents see my GitHub credentials?

No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.

How proven is the GitHub connector?