upgrade-settings

To turn agent schema drift into an upgrade plan, compare the latest agent schema against your installed configuration to identify new features and deprecated settings. This generates an ordered, implementation-focused plan with exact files, affected keys, and safe steps.

Schema drift occurs when your installed agent configuration diverges from the latest agent schema. You need to check for drift when upgrading settings, leveraging new schema features, or deprecating old settings to ensure your configuration remains current and compatible.

Generate an upgrade plan for deprecated config settings by analyzing the active agent schema and comparing it to your installed configuration. The resulting plan categorizes outdated keys into deprecate/remove and investigate-later buckets with specific file-level guidance.

Yes, the schema upgrade analysis supports different agent families. The comparison is explicitly scoped to the initiating agent family, including Claude Code, Codex, OpenCode, or Pi, ensuring the upgrade plan targets the correct environment.

The best way to identify safe steps for adopting new schema features is to compare your active agent schema with your current config. The analysis outputs precise file-level guidance and the smallest safe implementation steps categorized as adopt now.