Summary
The integrations reference still documents a kimi --migrate-legacy behavior that #3097 removed. #3097 ("make agent-context extension a full opt-in", released in v0.12.0) removed the KIMI.md -> AGENTS.md context migration from the kimi integration — _migrate_legacy_kimi_context_file and the context_file = "AGENTS.md" handling are gone. --migrate-legacy now only moves the skills directory (.kimi/skills/ -> .kimi-code/skills/).
Stale text (two places in docs/reference/integrations.md)
- Supported-agents table (kimi row): "...and (when the
agent-context extension is enabled) migrates KIMI.md context into AGENTS.md"
- Integration-specific options table (kimi
--migrate-legacy): "...when the agent-context extension is enabled, also migrates KIMI.md to AGENTS.md"
Both promise a migration the CLI no longer performs.
Suggested fix
Drop the KIMI.md -> AGENTS.md clause from both lines so the docs match the current code.
note: i used an ai assistant to help investigate and write this up.
Summary
The integrations reference still documents a
kimi--migrate-legacybehavior that #3097 removed. #3097 ("make agent-context extension a full opt-in", released in v0.12.0) removed theKIMI.md->AGENTS.mdcontext migration from the kimi integration —_migrate_legacy_kimi_context_fileand thecontext_file = "AGENTS.md"handling are gone.--migrate-legacynow only moves the skills directory (.kimi/skills/->.kimi-code/skills/).Stale text (two places in
docs/reference/integrations.md)agent-contextextension is enabled) migratesKIMI.mdcontext intoAGENTS.md"--migrate-legacy): "...when theagent-contextextension is enabled, also migratesKIMI.mdtoAGENTS.md"Both promise a migration the CLI no longer performs.
Suggested fix
Drop the
KIMI.md->AGENTS.mdclause from both lines so the docs match the current code.note: i used an ai assistant to help investigate and write this up.