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
[Question] Skills在使用“渐进式工具 Tool 披露”,使用人工介入(Human-in-the-Loop)时,No ToolCallback found for tool name #4606
Skills在使用“渐进式工具 Tool 披露”,使用人工介入(Human-in-the-Loop)点击确认时,会报错
java.lang.IllegalStateException: No ToolCallback found for tool name: queryTool
at com.alibaba.cloud.ai.graph.agent.node.AgentToolNode.lambda$executeToolCallWithInterceptors$4(AgentToolNode.java:547) ~[spring-ai-alibaba-agent-framework-1.1.2.2.jar:1.1.2.2]
Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException:
Assembly trace from producer [reactor.core.publisher.MonoCompletionStage] :
reactor.core.publisher.Mono.fromFuture(Mono.java:629)
com.alibaba.cloud.ai.graph.executor.NodeExecutor.executeNode(NodeExecutor.java:126)
Error has been observed at the following site(s):
I reproduced this on current main. The dynamic callback exposed by SkillsInterceptor is stored only in the first run's RunnableConfig.context; HITL resume normally creates a new config, so AgentToolNode cannot resolve the approved tool.
I am working on a focused fix that keeps progressive schema disclosure unchanged while allowing Skill-managed callbacks to be resolved again for execution after resume, with a deterministic regression test covering read_skill -> dynamic tool -> HITL -> approve -> execute.
Activity
suwe12 commentedon May 8, 2026
有实例代码吗
benym commentedon May 11, 2026
It is still likely that the model has a certain probability of returning an unknown ToolCall. Skill is merely a trigger point.
releated to #4525
silent1995 commentedon Aug 26, 2026
他说的应该是tool只绑定到skill上,并且在inteceptor设置了在该工具被调用前中断,因为我也遇到了这种情况。
dangzitou commentedon Aug 30, 2026
I reproduced this on current
main. The dynamic callback exposed bySkillsInterceptoris stored only in the first run'sRunnableConfig.context; HITL resume normally creates a new config, soAgentToolNodecannot resolve the approved tool.I am working on a focused fix that keeps progressive schema disclosure unchanged while allowing Skill-managed callbacks to be resolved again for execution after resume, with a deterministic regression test covering
read_skill -> dynamic tool -> HITL -> approve -> execute.