See who's doing what
Every open PR, review request and assigned issue, per person and per team, across your orgs. An Inbox for your own queue, a standup for yesterday, time off on the calendar.
Coding agents can turn an issue into a pull request in an afternoon. But knowing who's overloaded, which reviews are stuck, whether the board matches the code, and what shipped this week still means clicking through GitHub, boards, spreadsheets and chat.
Gannin puts the team's work, its delivery and its agents in the same window, so the bottleneck is never the part nobody can see.
Every open PR, review request and assigned issue, per person and per team, across your orgs. An Inbox for your own queue, a standup for yesterday, time off on the calendar.
Work on This turns an issue into a Claude Code session, tabbed beside the others, with a live diff, its questions answered in a click, and its PRs and checks watched for you.
Plans, requirements and findings in your team's harness repo, linked to the issues they're about. Plan with Claude, break a requirement into issues, and keep the board in step.
Who has what in flight, and your own reviews, PRs and issues in one queue.
Cycle time by stage, first review, rework and PR size, by month or quarter, against goals.
Findings on the diff to keep, edit or dismiss, posted to GitHub as one review.
Agents on issues, in tabs, on your Mac or your server, with live diffs and quick replies.
Plans and requirements beside the code, epics, and a board kept honest.
Where the effort goes, by category, against the mix you're aiming for.
Yesterday per person, and live capture of what customers are raising.
Run time, failures, flaky workflows and red default branches, repo by repo.
Each issue gets its own Claude Code session in a tab. Gannin tells you which one needs you, shows the question with its options, keeps a live diff of every worktree, and resumes the conversation after a restart.
Cycle time split into coding, waiting, rework and merging, by month, quarter or year, against the period before and your goals. Gannin says which stages, repos and people moved it, and writes the weekly digest.
When a review lands on you, start Claude on it from the notification or the menu bar. Its findings sit on the PR's diff by severity. Keep, edit or dismiss each, add your own, and post one review to GitHub.
Pick the orgs you look after. Gannin reads your PRs, issues, boards and Actions; everything you enter syncs through your own iCloud.
Choose the repo where plans and standards live, or create one. The team's settings can live there too, reviewed like code.
Click Work on This. Claude Code starts in the harness with the issue's brief, on your Mac or your server, signed in as you.
[TESTIMONIAL: a sentence or two from an engineering lead, in their words]
[TESTIMONIAL: a sentence or two from an engineer using the agents]
A SwiftUI app talking straight to GitHub. No Gannin server in the middle.
What you enter syncs through your private iCloud, or lives in your team's own harness repo.
Claude runs through your own Claude Code login, only when you ask. Gannin never handles your Claude credentials.
Board moves, labels, issues and reviews are shown to you before anything is written to GitHub.
Download Gannin for Mac, sign in with GitHub, and pick an org.
macOS [VERSION] or later ยท [PRICING NOTE]