GitComet Pro AI Features
AI Features
Turn on GitComet Pro's optional AI features, choose a local model, an API endpoint, or a coding agent CLI as the provider, and use AI commit messages, explanations, AI notes, merge conflict help, and coding agent session status.
GitComet Pro's AI features are optional and off by default. Nothing AI-related runs, and nothing is sent anywhere, until you turn them on and set up a provider. Every action that sends an AI request carries an AI mark, so you can tell it apart from the rest of the app.
Turn on AI and choose a provider
- Open Settings (
Cmd+,on macOS,Ctrl+,on Windows and Linux) and choose AI Providers. - Turn on AI features.
- Select a provider tile, fill in its settings, and choose Save. Test connection sends the provider a short test request.
| Provider | What it uses |
|---|---|
| Local model | A model server on this computer. Requests stay on this machine. |
| OpenAI compatible | Any API that speaks the OpenAI format. Enter its Endpoint (the base URL, including /v1 where it needs one), Model name, and API key. |
| Anthropic Messages | Anthropic's Messages API, with your own API key. |
| Claude Code CLI, Codex CLI, OpenCode CLI, GitHub Copilot CLI | The coding agent CLI installed on this computer, under your own sign-in to it. GitComet Pro finds it on your PATH; enter a Binary path to use another. |
Each provider has its own switch. When several are on, requests go to the one marked Default; choose Make default to change it. The Network line at the top of the page always says where requests go, for example Requests stay on this machine or Requests go to a host.
API keys are kept in your operating system's keychain, never in GitComet Pro's settings file. Remove… deletes a provider and its saved key.
Turning AI features off stops every AI path at once and leaves the AI views empty.
AI commit messages
With staged changes, choose the AI button in the commit box, next to Previous commit messages. GitComet Pro writes a message for the staged changes and puts it in the commit box, where you can edit it before committing.
Explain a change
Open a file's change in History, then run Explain this change from the command palette or press Cmd+Option+E on macOS or Ctrl+Alt+E on Windows and Linux. The explanation appears in the AI tab of the sidebar.
Annotate this change asks for a short note on each hunk of the selected commit or of your working tree changes, with a risk level for each. Select a note to open its file in the diff. Notes are the model's reading of the change, not a verdict.
Resolve merge conflicts with AI
When a merge stops with conflicts, History shows Resolve using AI next to Abort merge. It needs one of the CLI providers; a model endpoint alone cannot edit files.
- GitComet resolves what it safely can first and stages the files it resolved completely.
- GitComet Pro then starts the CLI as an agent in your working copy, with the conflicts that are left, a summary of both branches, and any instructions you add.
- Follow the conversation in the panel that opens. You can change the model, the reasoning effort, and the access level while it runs.
| Access | What the agent may do |
|---|---|
| Sandboxed (default) | Edit files and run commands. GitComet Pro refuses Git commands that change history. |
| Ask first | Every command and edit waits for your approval. |
| Full access | Whatever the CLI itself allows. GitComet Pro does not guard the history. |
GitComet Pro stages the files the agent resolves, and never commits. Some files are never handed to the agent and are named with the reason, including files deleted, added, or renamed on one side, submodules, symbolic links, Git LFS files, files that .gitattributes merges another way, non-UTF-8 text, and files changed on disk since the merge stopped.
Stop and close ends the session. Minimizing the panel keeps the agent working.
Coding agent sessions
GitComet Pro shows the coding agents you run yourself, in their own apps or terminals, while they work on a repository: Claude Code, Codex, OpenCode, and GitHub Copilot CLI. It does not start or drive them.
With AI on and the agent's CLI provider turned on:
- History marks the commit each live session works from, coloured by its status: running, waiting for you, or idle.
- The Coding agents sidebar section and a status item list the sessions.
- A session's menu can bring its window to the front or open it in the agent's app, resume it in a terminal, copy its resume command or session id, and open its worktree.
Session status hooks
Without hooks, GitComet Pro reads the status from what each agent records. For Claude Code and Codex, you can also install hooks that report when a session waits for you. In Settings → AI Providers, select the agent and choose Install hooks. GitComet Pro writes them into the agent's own settings file and copies the file aside first, as *.before-gitcomet-pro:
- Claude Code:
~/.claude/settings.json(or the folder inCLAUDE_CONFIG_DIR); - Codex:
~/.codex/hooks.json(or the folder inCODEX_HOME). Codex asks you to trust new hooks in/hooksbefore it runs them.
Each hook runs GitComet Pro's own command, which records only a session's id, folder, and status, never a prompt. Uninstall hooks removes them. If you move the app, install the hooks again.
Terminal windows on GNOME
On GNOME, only GNOME Shell may bring another app's window to the front. To let a click on an agent raise the terminal window it runs in, choose Install GNOME extension under AI Providers. The extension lists windows and raises the one GitComet Pro asks for, nothing else. GNOME starts a new extension after you log out and back in.
Privacy
- Requests go straight to the provider you chose. They do not pass through GitComet Pro's servers. With a local model they stay on your computer.
- CLI providers run with their tools off for commit messages, explanations, and notes: one run per request, in an empty folder, keeping nothing. The CLI uses your own sign-in and its own provider.
- Resolve using AI is the exception. It runs the CLI as an agent in your working copy, with the access level you choose.
- Reading agent sessions is metadata only. GitComet Pro reads session ids, folders, status, times, and session titles from what the agents leave on disk, never prompts or messages. It writes nothing to an agent's settings unless you install hooks.