New GitComet Pro is out now

GitComet
Download

Review every pull request from your desktop

GitComet Pro connects your forges and your coding agents to one fast Git client. Your code and your tokens stay on your machine.

Get GitComet Pro See how review works

Linux, macOS and Windows. Installs beside the free edition.

GitComet PRO

review · forges · agents

  • Claude Code
  • OpenAI Codex
  • OpenCode
  • Copilot CLI
  • Local models
  • Anthropic API
  • OpenAI-compatible
  • GitHub
  • GitLab
  • Azure DevOps
  • Bitbucket
  • Gitea
  • Forgejo
  • Self-hosted

Also works with OpenRouter, llama.cpp, LM Studio GitHub Enterprise · GitLab self-managed · Bitbucket Data Center · Azure DevOps Server · Codeberg

Review and approval

From review request to merge, without opening a browser

Pick up a pull request, read it in GitComet's diff, comment, approve and merge. Your review goes to the forge in one piece, and the next push only shows you what changed.

Review Pull Requests Without a Browser

53 seconds
Pick up a pull request in GitComet Pro, read it in GitComet’s diff, comment on a line, approve and merge it without opening a browser. Then see your coding agents in History and write a commit message with your own AI.

Watch with the written walkthrough

Steps shown in the video
  1. Open Explore and select Pull requests. The queue lists the pull requests waiting for your review. Select one to read its description and conversation, then choose Review.
  2. The pull request’s changed files open in GitComet’s diff. Press R to mark each file reviewed as you read it; the file list shows how many are done.
  3. Select a line and press C to comment on it. Choose Save as draft to keep the comment on your device until you finish the review, or Comment to post it now.
  4. Choose Finish review. With every file reviewed and one draft waiting, select Approve and finish. The verdict and the draft go to the forge together; finishing never merges.
  5. Open the pull request’s Checks tab to confirm the checks passed, then merge it straight from GitComet.
  6. In History, coding agent sessions appear next to the commits they touch, with their status. Right-click a session to bring it to the front, copy its resume command or open a terminal there.
  7. Stage a change and use the spark in the commit message box. Its tooltip says what it sends and which provider answers; AI stays off until you switch it on.

  1. Pick up

    Pull requests waiting for you, your local branches and the working tree, in one review queue across every forge you connect.

  2. Read

    GitComet's own diff, with Difftastic. Mark each file reviewed; when the author pushes again, only the files whose content changed come back.

  3. Comment

    Comment on a line and reply in threads. Post a comment at once, or save it as a draft for the review you send at the end.

  4. Decide

    Finish the review with Comment, Approve or Request changes, as far as your forge accepts them. Submitting never merges.

  5. Merge

    Checks, merge method, auto-merge and the merge queue. Merge the bottom of a stack and rebase the rest in one step.

Read the review guide in the docs

Forges

Six forges, cloud or self-hosted, one way of working

Connect several accounts at once. Review, comments and merging work the same everywhere, and each forge keeps its own options where it has them.

GitHub

Cloud
github.com
Self-hosted
GitHub Enterprise

Approve, request changes, viewed files synced to GitHub, stacked pull requests and the merge queue.

GitLab

Cloud
gitlab.com
Self-hosted
GitLab self-managed

Approve, and request changes on GitLab 18.11 and later. Comments wait as draft notes; auto-merge and merge trains.

Azure DevOps

Cloud
Azure DevOps Services
Self-hosted
Azure DevOps Server

Approve and comment, pipelines, and auto-complete when the checks pass.

Bitbucket

Cloud
Bitbucket Cloud
Self-hosted
Bitbucket Data Center

Approve and request changes, which Bitbucket Data Center records as Needs work.

Gitea

Cloud
gitea.com
Self-hosted
Your own Gitea

Approve, request changes and comment, on gitea.com or your own server, even behind a path such as /git.

Forgejo

Cloud
Codeberg
Self-hosted
Your own Forgejo

The same review flow as Gitea, for Codeberg and Forgejo instances.

Other Git hosts, including AWS CodeCommit, work as plain Git with links to commits. How forge connections work

Coding agents and AI

Your agents, in the history they are writing

GitComet Pro works with the coding agents you already use, under your own sign-in. AI features are optional, and each one tells you what it sends before it sends it.

Coding agents in History

History shows your Claude Code, Codex, OpenCode and Copilot sessions next to the commits they touch, with their status. Right-click a session to resume it.

AI when you ask for it

Commit messages, explanations, change notes and pull request descriptions. Every AI action carries the spark mark, and its tooltip says what it asks, what it sends and who answers.

Your provider, or none

Use the Claude Code, Codex, OpenCode or Copilot CLI you already have, your own Anthropic or OpenAI-compatible key, or a local model so nothing leaves the machine. One switch turns AI off.

Projects and profiles

Group repositories into projects and switch Git identity per project, so work and personal commits never mix.

Local by design

Your code never passes through us

Tokens stay in your keychain

Forge sign-ins and refresh tokens are stored in your operating system's keychain, never on our servers.

Straight to your forge

Pull requests, comments and merges go from your desktop directly to the forge. Our service handles only your account and licence.

Nothing approved by default

A new forge connection can't touch any repository until you approve it, and you can end a session at any time.

Pricing

Pick a licence

Every licence includes all of GitComet Pro. The free edition stays free, and you can keep using it beside Pro.

  • Review and approval on six forges
  • Several forge accounts at once
  • Projects and per-project Git identity
  • Coding agents in History
  • Optional AI with your own provider
  • Everything in the free edition

Questions

Questions about GitComet Pro

Does GitComet Pro replace the free edition?

No. GitComet Pro installs beside the free edition as a separate app with its own settings, so you can keep both.

Do you see my code or my forge tokens?

No. Forge sign-ins are stored in your operating system's keychain, and pull requests, comments and merges go from your desktop directly to the forge. The GitComet Pro service handles only your account and licence. AI requests go only to the provider you choose.

Does GitComet Pro work offline?

Yes. GitComet Pro keeps a signed licence on the device and checks in with the account service from time to time.

Can I use a self-hosted forge?

Yes. GitComet Pro works with GitHub Enterprise, GitLab self-managed, Bitbucket Data Center, Azure DevOps Server, Gitea and Forgejo, including instances served under a path.

Is AI required?

No. AI features are optional and off until you choose a provider. One switch turns all of them off again.