You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Track compatibility transition for extension command and alias collisions #5432
Follow-up to the compatibility transition requested in #5134, which addresses the alias collision reported in #5081.
The existing PR rejects normalized command/alias collisions during installation. The requested transition needs to preserve existing installations while preventing overwrites and removals of another extension’s generated files.
Proposed stages
Adapt fix(extensions): reject aliases that resolve to installed skill names #5134 to issue a deprecation warning and complete installation while leaving conflicting outputs unregistered. Report each skipped command/alias and its existing owner. Preserve the existing owner’s files during install, forced reinstall, update, and removal.
Reject conflicting registration by default, with an explicit override that still preserves another extension’s files. Choose whether the override reuses --force or uses a dedicated option before implementing this stage.
Remove the override and enforce the rejection after maintainers decide the transition is ready.
Behavior and regression coverage to define
Compare actual output paths for each configured integration. Dotted and hyphenated names can collide in skills layouts while remaining distinct in command-file layouts.
Account for primary commands, aliases, shared skills directories, and companion prompt files.
Keep registration metadata consistent with the outputs actually created. A skipped alias must not acquire ownership of an existing file.
Preserve the installed owner’s bytes when installing or removing a conflicting extension, including after a failed update and rollback.
Cover existing installations, forced reinstalls, updates, disabled extensions, and changes of integration output mode.
Make the warning identify the affected alias/output and the owning extension, with a migration path for extension authors.
No release schedule is proposed. The stage-one implementation remains pending in #5134.
Posted on behalf of chelsealong. Codex (model GPT-6, autonomous) drafted this tracking issue from the maintainer’s review request.
Activity