Connected Apps

GitHub

Turn your AI into a development teammate.

Connect GitHub so MoClaw can read repositories, inspect pull requests, work with issues, collect CI evidence, and help move engineering work forward from chat. It can look at code and comments, summarize what changed, and use scoped GitHub App access instead of asking you to paste tokens into prompts.

How it works

3 steps to wire up GitHub, no engineering required.

  1. 1

    Install the GitHub app

    Authorize the MoClaw GitHub app for your account or organization and choose the repositories it can access.

  2. 2

    Ask with repository context

    Paste a PR, issue, branch, or repository URL, or ask MoClaw to inspect a connected repository by name.

  3. 3

    Let MoClaw gather evidence

    MoClaw reads files, PR metadata, review comments, issues, workflow runs, check annotations, and other relevant GitHub context before answering or acting.

Why it matters

GitHub work usually spans many small surfaces: a pull request diff, review comments, CI logs, issue context, branch state, and the repository files themselves. MoClaw brings those pieces into one task loop.

After GitHub is connected, you can ask for a PR review summary, a failing check investigation, a release issue triage, or a codebase lookup without manually copying links and logs. MoClaw can read the relevant repository context, choose the right GitHub action, and return a structured answer you can use immediately.

The connection is designed around scoped access. You choose the GitHub account or organization installation, and the app uses installation-scoped credentials for repository work. That keeps the integration usable for serious engineering tasks while avoiding the usual habit of pasting personal access tokens into a chat window.

Try saying

Real prompts you can paste into GitHub.

  • Summarize the open review comments on this PR and tell me which ones need code changes.
  • Find why the latest GitHub Actions run failed and give me the smallest fix to try.
  • Create an issue for the flaky login test and attach the relevant CI evidence.
  • Compare this feature branch against main and explain the behavioral risk.

Step by step demo

What actually happens when you send the prompt.

Prompt 01 4 steps

“Summarize the open review comments on this PR and tell me which ones need code changes.”

What MoClaw does

  1. 1 Reads the pull request metadata, changed files, and review threads.
  2. 2 Groups unresolved comments by file and severity.
  3. 3 Separates actionable code changes from clarification-only comments.
  4. 4 Returns a prioritized checklist with links back to the source comments.
Result

You get a concise PR review brief: '3 actionable changes: fix retry handling in billing.ts, add a regression test for empty webhooks, and update the migration comment. 2 comments are questions only.'

Prompt 02 4 steps

“Find why the latest GitHub Actions run failed.”

What MoClaw does

  1. 1 Finds the latest workflow run for the branch.
  2. 2 Reads failed jobs, check runs, and annotations.
  3. 3 Pulls the relevant log snippets and matches them to the changed files.
  4. 4 Explains the likely root cause and the next fix.
Result

MoClaw reports: 'The frontend test failed because the connector registry now includes Sentry, but the mocked state omitted it. Add sentry to the fixture before rerunning.'

FAQ

Quick answers about pricing, privacy, and limits.

Does MoClaw need access to every repository?
No. You choose which repositories the GitHub app can access during installation, and you can change that scope from GitHub settings.
Can MoClaw read private repositories?
Yes, if the GitHub app is installed with access to those repositories. Private repository access follows the same app installation scope you configure in GitHub.
Can it work with pull requests and CI?
Yes. The connector exposes pull request, review, check run, workflow run, job log, repository content, issue, and comment actions for agent workflows.
Is this the same as pasting a GitHub token into chat?
No. MoClaw uses the connected GitHub app and scoped connector credentials, so repository access is managed through GitHub rather than raw tokens in prompts.

Try MoClaw free.

1,000 credits a month, or bring your own key for unlimited usage.

Cancel anytime