Integration · GitHub

Mention an agent in a GitHub issue. It comes back with a pull request.

Install the GitHub app on the repositories you choose and mention @zwrm-agent in an issue or pull request. The agent works on a branch in its own machine and answers in the thread.

Book a demo How to set it up

Install the app once. Then mention it where the work is.

The agent gets the repositories you pick and the permissions GitHub shows you during the installation.

01
Install the GitHub app

Install the zwrm GitHub app on the repositories the agent should work in, and only on those.
02
Choose the agent

Pick the agent that answers in those repositories, with its instructions, skills and budget.
03
Mention it

Write @zwrm-agent in an issue or pull request. Each issue keeps its own workspace, so follow-ups build on what came before.
04
Review the pull request

The agent pushes to a branch and opens a pull request. Merging stays with you.

With a dedicated GitHub user for the agent instead of the app, you can also assign issues to it and request its review.

Read the docs

What the agent can do on GitHub. In the repositories you choose.

The app asks for these permissions when you install it. Workflow files stay off unless you allow them.

Agents can read

Code in the repositories the app is installed on
Issues, pull requests and their comments
Actions runs, checks and commit statuses

Agents can write

Branches and commits
Pull requests and review comments
Issue comments and labels
Workflow files, only if you grant that permission

Agents can’t

Work in repositories the app isn’t installed on
Take assigned issues as an app: GitHub allows that only for users
Merge on its own: it leaves merging to you unless you ask

Branch protection rules apply to the agent like to anyone else on the repository.

Pull requests, not surprises. In the repositories you choose.

Only where it’s installed

The app works only in the repositories you install it on, with the permissions GitHub shows you during the installation.

Branches, not the main line

The agent is told never to push to the default branch and never to merge unless someone asks. Your branch protection applies as well.

Its own machine per run

Each run happens in an isolated microVM, apart from your other agents and systems.

A daily cap

Mentions start a limited number of runs per day, on top of the agent’s own daily budget.

Every run is logged in the dashboard, with the tools the agent called and what came back.

How zwrm handles security

Routines on GitHub. Explained once, they run on their own.

On every new issue

Issue triage

Labels each new issue, asks for missing steps to reproduce and links related issues.

Ole · Research
Mon · 09:00 →

Release notes draft

Collects last week’s merged pull requests and posts draft release notes in the team’s chat for review.

Pia · Writing
Daily · 06:00

Dependency updates

Checks for outdated dependencies and opens one pull request per update, with the changelog linked.
Wanda · Operations

All routines

More integrations. Same setup, other tools.

All integrations

Notion

Mention an agent on a shared page. It answers in the thread as its own Notion user.
Microsoft 365

Mail, calendars, files and Teams chats, through a Microsoft 365 user of the agent’s own.
HubSpot

Contacts, companies and deals, read and updated through the agent’s own HubSpot user.
DATEV

Open items and accounting data, through an MCP server or exports you set up.
Front

Conversations in your shared inboxes: reply drafts, comments and tags.