AI for the tedious parts — on your terms
Git Navigator's AI help is optional and local-first. It drafts commit messages from your staged diff and proposes how to split an overgrown change into focused commits — using your editor's language model (VS Code) or a local CLI such as Claude Code or Codex on the desktop. There is no Git Navigator backend in the loop.
Where AI helps
Generate commit messages
Draft a commit message from the current staged diff, then edit it before committing. The message is a starting point you own, not an automatic commit.
Plan split commits
Ask AI to suggest how a large change should be divided, then use Git Navigator's hunk-level split to carry out the plan by selecting the code blocks for each commit.
Local-first, no backend
AI features run through your editor's language model support or a local CLI. Git Navigator does not require or run its own AI backend, so your diffs are not routed through a service we operate.
Entirely optional
On the desktop, AI is behind a build feature flag so the core product ships without "AI bloat"; in VS Code it uses the editor's existing language-model support. Everything Git Navigator does works with AI turned off.
Using AI in the commit flow
- Stage your changes. Stage the files (or specific hunks) you want in the next commit, just as you would for any commit in Git Navigator.
- Generate a message. Ask Git Navigator to draft a commit message from the staged diff, then review and edit it before committing.
- Plan a split. For a large change, ask AI to propose a split into focused commits, then select the hunks for each piece in the split-commit overlay.
Frequently asked questions
Does Git Navigator send my code to its own servers for AI features?
No. AI features are local-first: they use your editor's language model support in VS Code, or a local CLI such as Claude Code or Codex on the desktop. Git Navigator does not run its own AI backend.
What can the AI actually do?
Two things in the commit workflow: generate a commit message from your staged diff, and plan how to split a large change into smaller, focused commits. Both produce suggestions you review and edit — nothing is committed automatically.
Is AI required to use Git Navigator?
No. AI assistance is entirely optional. On the desktop it sits behind a build feature flag so the app can ship without it, and every core feature works with AI turned off.
How does AI split planning relate to manual split commits?
AI proposes a division; you carry it out with the same hunk-level split-commit flow described on the Commit Management page. The AI plan is guidance for which hunks belong together, not a separate mechanism.