Connect OpenClaw to GitHub

September 13, 2026Claworc Team

Tags:integrations

GitHub is where most software teams keep their code, and with it their issues, pull requests, CI runs and release history. It is also a steady source of small chores: labeling the issues that came in overnight, chasing a pull request that has sat without review for three days, or answering “which PR changed that config file?” for the fourth time.

With Claworc’s External Connections, an OpenClaw agent can work inside your GitHub account or organization on your behalf. You authorize GitHub once through a popup, Composio holds the resulting token, and the agent gets an auto-generated claworc-github skill that describes which GitHub tools exist and how to call them. The agent never sees a password, an OAuth token or a personal access token.

Tools available to OpenClaw agents

Composio’s GitHub toolkit is one of its largest, with more than 800 actions covering repositories, issues, pull requests, Actions, projects and organization settings. These are the ones an OpenClaw agent reaches for most often:

• List and filter issues — open or closed issues in a repository, filtered by label, assignee, milestone or date, so the agent can see what needs attention.
• Open issues — create a new issue with a title, body, labels and assignees, for example after the agent spots a failing check or a bug report elsewhere.
• Label and comment — label and reply on issues so triage decisions are visible to the whole team.
• Read pull requests — find open pull requests and read the changed files in each one.
• Review pull requests — leave a review with comments, approve, or request changes.
• Search and read code — search across repositories and read a specific file at a given branch or commit.
• Check Actions runs — see workflow runs and their status without opening the Actions tab.

Every tool is called through a small broker running next to the agent, so the agent only needs to describe what it wants done in plain language and let the skill handle the rest.

Use cases

Issue triage every morning

Ask the agent to list every issue opened in the last 24 hours, read each one, and apply labels such as bug, feature or needs-info. Where a report is missing a reproduction, it posts a short comment asking for one. When you open the issues page, the new arrivals are already sorted and the obvious questions have already been asked.

First-pass pull request review

Point the agent at a repository and have it look at every open pull request without a review. It reads the changed files, checks them against your contributing guidelines, and leaves a review that flags missing tests, unclear naming or a changed file that touches a sensitive area. Human reviewers still approve; they just start from a summary instead of a blank diff.

Answer questions about the codebase

“Where do we set the default timeout for outbound webhooks?” The agent searches the code, reads the relevant file and points you to the line, along with the pull request that last changed it. Useful for onboarding, incident calls and anyone who does not have the repository checked out.

Get started

Connecting GitHub takes three steps: an admin adds a Composio API key to Claworc’s settings, you open the instance’s Settings tab, click + Add connection, pick GitHub and sign in. The claworc-github skill appears in the instance a moment later. The full walkthrough, including the exact Composio permissions the key needs, is in the External Connections documentation.