Integrations

Turn GitHub Issues Into Pull Requests

GitHub Issues is the most direct way to run Codowave, because the issue and the code live in the same place. There's no separate tracker to sync — Codowave reads your open issues, picks the ones that match your filters, and opens a PR linked straight back to the issue it resolved.

If your backlog is a list of GitHub issues that keep getting deferred, this is the integration that clears them while your team stays focused on the work only humans can do.

Start your 5-day trial

How the GitHub Issues Integration Works

Codowave is GitHub-native from the ground up, so this path has the least setup. Install the app, point it at a repo, and it starts reading.

Install the GitHub App. Three minutes, no infrastructure to stand up.
Set your filters. Choose which labels, assignees, and complexity ranges Codowave should pick up — for example, bug or good-first-issue issues under five story points that are unassigned.
The multi-agent loop runs. Planner decomposes the issue and flags affected files, Coder implements against your repo's conventions, Reviewer scores the diff, Tester runs your suite and adds missing tests.
A PR opens, linked to the issue. It references the issue number so GitHub closes the issue on merge, includes a written summary, and attaches the test output. CI status posts back to the PR.

The issue is the spec. You don't write a prompt per issue — the metadata you already maintain (title, body, labels) is what Codowave reads.

What Codowave Reads and Writes

GitHub object	How Codowave uses it
Issue title and body	The spec — what to build, scope, expected behavior
Labels	Filtering — which issues to pick up, which to avoid
Assignee	Targeting — unassigned only, or a dedicated agent queue
Issue comments	Clarification — Codowave asks here when an issue is ambiguous
Branch	One branch per issue, named for the issue
Pull request	Opened with summary, linked issue, attached test output
CI checks	Read back so the agent can iterate on failures
Branch protection	Respected — Codowave works within your rules

The PR Codowave opens looks like one a careful junior engineer opened: a linked issue, a clear summary, and passing tests attached.

Safety Built In

Both controls that engineering leads ask about are on by default.

Watch-only mode, week one. Codowave opens PRs but never auto-merges. You review the first few, check that the test output and conventions look right, and build confidence before handing over any merge authority.
Cost ceiling per run. Each agent run has a hard dollar cap. If an issue would exceed it, Codowave stops, returns partial work in a draft PR, and flags the issue. No surprise Anthropic bill.

For large issues, Codowave auto-decomposes the work into smaller stages internally before it starts writing, so a sprawling issue becomes a sequence of reviewable changes rather than one giant unreviewable diff.

Why GitHub-Native Matters

Some AI tools bolt onto GitHub through a chat interface, where Slack or a UI is the real source of truth and the PR is an afterthought. Codowave treats GitHub as the system of record. It respects your labels, links PRs to issues, posts CI status back, and works within branch protection.

That depth pays off over time. After roughly ten merged PRs, pattern memory learns your repo — naming, file layout, test style — and the Reviewer agent checks each new diff against those learned conventions before opening the PR. Codowave runs in isolated per-org Docker containers and uses your own Anthropic Claude key, so your code stays scoped to your org and the model spend is yours.

Get Started

Sign up at codowave.com/signup — the free plan covers 3 issues, no card required.
Install the GitHub App and connect a repo.
Set filters, or use the defaults to start.
Review the first PRs in watch-only mode.
Enable auto-merge for the low-risk categories you trust.

Plans start at $20/mo — see pricing. For how the scoring works, see how Codowave picks which issues to work on.