ai-runtime-governance

To inventory local AI tools, you can run executable scripts to map installed models, CLIs, and IDE settings paths. This creates a single source of truth for governing configurations across runtimes like Codex, Claude, and VS Code.

Configuration drift detection identifies unauthorized or accidental changes in AI runtime settings from a known baseline. You need it to maintain governance and generate audit-ready reports for local developer environments.

You can back up AI CLI configurations and apply safe rollback changes by creating backup records before modifications. This governance workflow supports single-program or global path unification with executable rollback points.

Yes, this governance workflow supports GitHub CLI, Windsurf, Gemini, Codex, Claude, and VS Code. It maps their skill, MCP, rules, and agent settings to apply controlled changes with audit trails across these specific runtimes.

The best way to unify configuration paths is using a governance skill to inventory installed tools, back up current settings, and execute a documented path-unification plan. This ensures controlled changes with rollback records.

You should avoid a global governance workflow if you only need to modify a single AI program. Use the single-program governance mode instead to isolate changes and prevent unintended drift in other runtime configurations.