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
refactor(kosong)!: drop the select_tools capability spelling entirely
No catalogued model or shipped configuration ever used the capability,
so there is nothing to migrate: remove the deprecated select_tools
field/config-string acceptance and the hasDynamicallyLoadedTools compat
helper. dynamically_loaded_tools is the only spelling — read directly
where consumed. The select_tools builtin tool and the tool-select flag
keep their names (client-side mechanism vocabulary).
Copy file name to clipboardExpand all lines: .changeset/dynamically-loaded-tools-capability.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,4 +4,4 @@
4
4
"@moonshot-ai/kimi-code-sdk": patch
5
5
---
6
6
7
-
Rename the dynamic tool loading model capability to its canonical name `dynamically_loaded_tools` (the model-level ability to accept message-level tool declarations). The previous `select_tools` spelling — which named the client-side mechanism rather than the model capability — remains fully supported as a deprecated alias in model alias `capabilities` config and in catalog entries, so no configuration changes are required. The SDK's catalog-to-alias mapping now emits the canonical name.
7
+
Rename the dynamic tool loading model capability to `dynamically_loaded_tools` (the model-level ability to accept message-level tool declarations). The previous `select_tools` spelling — which named the client-side mechanism rather than the model capability — is removed outright: no catalogued model or shipped configuration ever used it, so there is nothing to migrate. Model alias `capabilities` config, catalog entries, and the SDK's catalog-to-alias mapping all use the new name.
0 commit comments