Summary
As of #3256 (v0.12.3), the Copilot integration supports a skills mode via --integration-options "--skills", and installing Copilot without it now emits a deprecation warning that the legacy markdown default will be phased out. This behavior does not appear to be documented yet in docs/reference/integrations.md.
Observations
- The Copilot row in the supported-agents table has an empty Notes cell, while other skills-capable integrations (codex, kimi, devin, etc.) describe their skills behavior there.
_warn_legacy_markdown_default() (src/specify_cli/integrations/copilot/__init__.py) tells users to pass --integration-options "--skills", but that option is not listed in the Integration-Specific Options table (only generic and kimi are).
Note
I recognize the skills default is mid-rollout (the warning explicitly precedes making it the default), so the docs may intentionally be waiting until that lands. Filing this only to flag the gap happy to leave it to the maintainers to decide whether/when documenting it fits the rollout plan. Not opening a PR for this reason.
Summary
As of #3256 (v0.12.3), the Copilot integration supports a skills mode via
--integration-options "--skills", and installing Copilot without it now emits a deprecation warning that the legacy markdown default will be phased out. This behavior does not appear to be documented yet indocs/reference/integrations.md.Observations
_warn_legacy_markdown_default()(src/specify_cli/integrations/copilot/__init__.py) tells users to pass--integration-options "--skills", but that option is not listed in the Integration-Specific Options table (onlygenericandkimiare).Note
I recognize the skills default is mid-rollout (the warning explicitly precedes making it the default), so the docs may intentionally be waiting until that lands. Filing this only to flag the gap happy to leave it to the maintainers to decide whether/when documenting it fits the rollout plan. Not opening a PR for this reason.