Audit trail for agent configuration
GAL keeps your AI coding agents on one approved configuration. Every change is versioned and synced to developers with one command, so you can see who changed what and when.
Why agent configuration needs a history
Every AI coding agent reads its own configuration files: instructions, permissions, and tool settings. Those files change quietly, on individual machines and in individual repositories.
No Change History
When an agent starts behaving differently, nobody can say what changed in its configuration, who changed it, or when.
No Approved Version
Each developer and each repository carries its own agent setup. There is no single approved configuration to point to.
Silent Drift
Local edits drift away from what the team agreed on, and nobody notices until an agent behaves differently on one machine.
How GAL keeps the history
GAL discovers your agent configuration, standardizes it on one approved version, and syncs that version to every developer.
Discover
Install the GAL GitHub App. GAL finds the agent configuration files in your repositories, for Claude Code, Cursor, Copilot, and other AI coding agents.
Standardize and Approve
Choose one approved configuration for your organization. Each change to it becomes a new version, recorded with who made it and when.
Sync
Developers pull the approved version with one command, gal sync --pull, so every machine runs the same configuration.
What the audit trail records
GAL keeps the configuration your AI coding agents run with under version history.
Versioned Configuration
Every approved configuration is kept as a version, so you can see what your agents were set up to do at any point.
Who Changed What, and When
Each change to the approved configuration is recorded with who made it and when.
One Approved Source
One approved configuration for the whole organization, instead of a different setup on every machine.
One-Command Sync
Developers pull the approved version with gal sync --pull, so local setups stay on the approved configuration.
Who it is for
Security Teams
See which configuration your AI coding agents were given, and trace each change to who made it and when.
Learn moreEngineering Leaders
Give every developer the same approved agent configuration, instead of a different setup on every machine.
Platform Teams
Roll out configuration changes as approved versions, synced to every developer with one command.
Learn moreFrequently asked questions
What does GAL record?
GAL keeps each approved version of your AI coding agents' configuration, with who changed it and when.
Why keep a history of agent configuration?
An agent's configuration decides how it behaves: its instructions, its permissions, and the tools it can use. When something changes, a versioned history tells you what changed, who changed it, and when.
Does GAL work with all AI coding agents?
GAL supports Claude Code, Cursor, GitHub Copilot, Windsurf, Gemini Code Assist, and Codex. We continuously add support for new AI coding agents as they emerge.
How do developers get the approved configuration?
They run one command, gal sync --pull, and their local setup matches the approved version.
Start your agent configuration history
Discover your agents' configuration, approve one version, and sync it to every developer with one command.
Start Free Trial