Can it push code or merge pull requests?

No. The connector covers code search, issues and pull-request review — the judgement work around a change rather than the merge button. That is a deliberate line: an agent is genuinely useful at reading a diff and saying what it does, and your branch protections should stay the thing that decides what lands.

My repositories belong to an organisation. Will it work?

That depends on the organisation. GitHub lets an owner require approval before any third-party OAuth app can reach org-owned repositories, so if the connect flow succeeds but the agent cannot see your work repos, that approval is almost always what is missing. An owner grants it once, in the organisation’s settings.

Is it reading my private code?

Only what you authorised on GitHub’s consent screen, and only when a brief asks it to. The grant lives on GitHub’s side, so you can review or revoke it from your GitHub settings at any time, independently of Burrak.

Developer tools

GitHub + Burrak AI

Give an agent your repositories — issues, pull requests and the code itself.

Connects with OAuth — revoke any time

GitHub holds the work and the record of the work. An agent with access can do the reading around it that nobody has time for: reconstructing why a change was made, turning a vague report into an issue an engineer can act on, or reviewing a pull request for the things a linter cannot see. It reads code and history rather than only metadata, so its answers come from your repository instead of from what a model remembers about the library you happen to use.

In the connector catalogue: Search code, manage issues, review pull requests.

Things you could ask for

Written the way you would actually say them. An agent plans the steps itself.

“Read this pull request and tell me what it changes, what it might break, and what the description leaves out.”
“Turn this support thread into a properly written issue with reproduction steps, and label it by the area it touches.”
“Find every place we still call the deprecated auth helper and list the files that need updating.”
“Summarise what merged this week into release notes written for customers, not engineers.”
“Work out why this function was written the way it was, using the commit history and the pull request that introduced it.”

GitHub authorises this connector at the account level — there is no per-repository picker, so it can reach the repositories your account can reach. If that is wider than you want, connect from an account with narrower access.

Connecting it

1Create a Burrak account — the free plan is enough to try this.
2Open Connectors and choose GitHub.
3Authorise Burrak in GitHub's own window. Your password never reaches us; we receive a token you can revoke whenever you like.
4Give an agent a task. It will use the connector when the work calls for it.

Start free How connectors work

GitHub and Burrak, in practice

Can it push code or merge pull requests?: No. The connector covers code search, issues and pull-request review — the judgement work around a change rather than the merge button. That is a deliberate line: an agent is genuinely useful at reading a diff and saying what it does, and your branch protections should stay the thing that decides what lands.
My repositories belong to an organisation. Will it work?: That depends on the organisation. GitHub lets an owner require approval before any third-party OAuth app can reach org-owned repositories, so if the connect flow succeeds but the agent cannot see your work repos, that approval is almost always what is missing. An owner grants it once, in the organisation’s settings.
Is it reading my private code?: Only what you authorised on GitHub’s consent screen, and only when a brief asks it to. The grant lives on GitHub’s side, so you can review or revoke it from your GitHub settings at any time, independently of Burrak.