Enterprise Configuration

Complete reference for the Git AI config.json file used to control repository scope, prompt storage, update behavior, and telemetry in enterprise deployments.

Git AI reads its configuration from a single JSON file on each developer machine:

Linux / macOS: $HOME/.git-ai/config.json
Windows: %USERPROFILE%\.git-ai\config.json

Deploy this file through MDM, endpoint management, or a bootstrap script alongside the binary. See Developer Install for full installation details.

Every key is optional. Missing keys fall back to defaults.

Configuration Reference

Option	Type	Description	Default
`git_path`	`Path`	Absolute path to the original `git` binary. Always set this in MDM deployments to point at `git-og`.	Shell `$PATH` lookup
`prompt_storage`	`"default"` \| `"notes"` \| `"local"`	Controls where prompt and session data is stored. See Prompt Storage.	`"default"`
`exclude_prompts_in_repositories`	`Pattern[]`	Glob patterns for repositories whose prompts are excluded from authorship logs. `["*"]` excludes all.	`[]`
`allow_repositories`	`Pattern[]`	Restrict the CLI to remotes matching these patterns. See CLI Configuration for details.	`[]` (all allowed)
`exclude_repositories`	`Pattern[]`	Block the CLI in remotes matching these patterns. See CLI Configuration for details.	`[]`
`telemetry_oss`	`"off"`	Disable anonymous performance metrics and error logging sent to Git AI maintainers.	Enabled
`telemetry_enterprise_dsn`	`string`	Sentry-compatible DSN for receiving performance metrics and error logs internally.	None
`disable_version_checks`	`boolean`	Skip the asynchronous version checks that run on `fetch`, `pull`, and `push`.	`false`
`disable_auto_updates`	`boolean`	Keep version checks active but prevent automatic binary updates. The CLI displays a manual upgrade prompt instead.	`false`
`update_channel`	`"latest"` \| `"next"`	Release channel to follow. `latest` = stable releases, `next` = prereleases.	`"latest"`

Only repositories belonging to an organization connected via the SCM app sync agent sessions, telemetry, and AI attributions to the Git AI dashboard. Connecting an SCM organization automatically includes every repository within it — no per-repo configuration is needed.

Repositories outside the connected SCM organization are not processed by the platform, regardless of client-side config.json settings.

Update Controls

Most enterprises roll out new binaries on a controlled schedule. Three options control how Git AI checks for and installs updates.

Option	Effect
`update_channel`	`"latest"` follows stable releases. `"next"` follows prereleases — useful for an early-adopter group.
`disable_version_checks`	Completely skips the asynchronous checks that run on `fetch`, `pull`, and `push`. Use this only when managing upgrades entirely through MDM or a deploy pipeline.
`disable_auto_updates`	Keeps version checks active but prevents automatic installation. The CLI displays a "run `git-ai upgrade`" message instead.

A common enterprise pattern: assign the "next" channel to a small early-adopter group, keep everyone else on "latest", and disable auto-updates organization-wide so upgrades only happen through the managed rollout process.

{
    "update_channel": "latest",
    "disable_auto_updates": true
}

Telemetry

OSS Telemetry

By default, Git AI sends anonymous performance metrics and error reports to the Git AI maintainers. Disable this by setting telemetry_oss to "off".

{
    "telemetry_oss": "off"
}

Enterprise Telemetry

Set telemetry_enterprise_dsn to a Sentry-compatible DSN to route performance metrics and error logs to an internal observability stack.

{
    "telemetry_enterprise_dsn": "https://[email protected]/123"
}

For custom forks built from source, the DSN can also be set at build time:

SENTRY_ENTERPRISE="https://[email protected]/123" \
cargo build --release

Full Example

A realistic enterprise configuration covering repository scope, prompt handling, update controls, and telemetry:

{
    "git_path": "/usr/local/bin/git-og",
    "update_channel": "latest",
    "disable_auto_updates": true,
    "telemetry_oss": "off",
    "telemetry_enterprise_dsn": "https://[email protected]/123"
}