| 🐛 fix: fallback to skill activation when activateTools cannot find identifier (#14010)
* 🐛 fix: fallback to skill activation when activateTools cannot find identifier
When an LLM calls activateTools with a skill identifier (e.g. "lobehub"),
the tool lookup fails with "Not found" because skills and tools are separate
registries. Now activateTools falls back to activateSkill for identifiers
not found as tools, so skills can be activated regardless of which API the
LLM chooses to call.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* 🐛 fix: fallback to skill activation when activateTools cannot find identifier
When an LLM calls activateTools with a skill identifier (e.g. "lobehub"),
the tool lookup fails because skills and tools are separate registries.
Two changes:
1. ActivatorExecutionRuntime.activateTools() now falls back to activateSkill
for identifiers not found as tools
2. selectActivatedSkillsFromMessages() now also extracts skills from
activateTools messages (pluginState.activatedSkills[]), so downstream
stepContext and execScript zip resolution work correctly
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> | 1 个月前 |
| ✨ feat(skills): recognize project-level skills in the homogeneous agent runtime (#15110) | 1 天前 |
| 🐛 fix: manual tool disabled (#13218)
fix: manual tool disabled | 1 个月前 |
| ✨ feat(skills): recognize project-level skills in the homogeneous agent runtime (#15110) | 1 天前 |
| ✨ feat(activator): require activation reason (#14597) | 12 天前 |
| ✨ feat(activator): require activation reason (#14597) | 12 天前 |
| ✨ feat(skills): recognize project-level skills in the homogeneous agent runtime (#15110) | 1 天前 |