ai-assisted commits

AI help for commits, on your terms.

AI Cortex adds optional AI help when you configure a provider: commit message drafts, an explanation of one side of a conflict and conflict resolution suggestions. It asks your provider which models your account can use, keeps secrets local-first and shows what each function sends. Git stays fully usable without AI.

FluxGit Commit Studio with the collapsible AI commit assistant on synthetic demo data
Real FluxGit interface · synthetic demo data
FluxGit AI Cortex settings for Anthropic: the saved model is no longer offered to this account, a warning explains that requests with it will fail and offers a current model, and the live catalog read from the provider API lists three models
Models read live from the provider · a saved model that is gone is flagged before a request fails · real FluxGit interface, synthetic demo data

The problem: AI in dev tools is often forced and opaque.

Many tools bolt AI on as a mandatory, always-on feature with unclear data handling. Developers want assistance that is optional, transparent and never blocks normal Git.

Current scope

AI Cortex is in beta and provider-dependent. External providers require consent, secrets and a clear fallback; FluxGit does not promise unlimited AI and AI must never be treated as a substitute for review.

How FluxGit helps.

commits

Assisted commit messages

Generate a commit message draft from the staged diff when a provider is configured.

models

Live model catalog

AI Cortex asks your provider which models your account can use as soon as a key is saved, and warns when a saved model is gone. A short, dated fallback covers an unreachable catalog.

conflicts

Conflict suggestions are drafts

An AI conflict suggestion only fills the editor. Nothing is written until you review and apply it, and Apply refuses a file that still contains conflict markers.

optional

Git works without AI

Provider tests and a clear fallback keep Git usable when AI is off or unreachable.

Privacy and security posture.

Secrets are handled local-first. Nothing is sent until you press an AI action, and only to the provider you chose; with a local Ollama endpoint it stays on your machine. Settings show what each function sends: a commit draft sends the staged diff, an explanation sends that side of the file, and a conflict suggestion sends the base, current and incoming versions of the conflicted file. Normal Git never requires AI.

Related features.