[Bug]:agentscope agent as tools模式下流式场景报错：Cannot add messages without tool results when pending tool calls exist.

[chestnut-Z]

agent as tools模式
1、主agent注册子agent方式 子agent是实例的
@OverRide
protected Toolkit createToolkit() {
Toolkit tk = new Toolkit();

    // 注册所有子 Agent 到 Toolkit（排除自己，避免循环）
    // 使用 Supplier 每次创建新实例，避免并发状态问题
    for (Agent subAgent : subAgents) {
        // 跳过大脑 Agent 自己，只注册真正的子 Agent
        if (subAgent == this || StringUtil.equals(subAgent.getName(), getName())) {
            log.info("Skipping self-registration for CoordinatorAgent");
            continue;
        }
        
        String agentName = subAgent.getName();
        String agentDesc = subAgent.getDescription();
        
        // 为每个子 Agent 创建 Supplier，每次调用时创建新实例
        SubAgentProvider<ReActAgent> agentSupplier = createAgentSupplier(agentName);
        
        tk.registration()
                .subAgent(agentSupplier, SubAgentConfig.builder()
                        .toolName(agentName)
                        .description(agentDesc)
                        .forwardEvents(false)
                        .build())
                .apply();
        log.info("Registered sub-agent: {} (with new instance per call)", agentName);
    }
    
    return tk;
}

/**
 * 创建 Agent Supplier，每次调用时创建新的 Agent 实例
 * 参考 BrainAgent 的实现方式，避免并发状态问题
 */
private SubAgentProvider<ReActAgent> createAgentSupplier(String agentName) {
    return () -> {
        // 根据 Agent 名称创建对应的新实例
        AgentBase newAgent = switch (agentName) {
            case "ChitChat" -> new ChitChatAgent(chitchatModel);
            default -> throw new IllegalArgumentException("Unknown agent: " + agentName);
        };
        
        // 初始化并返回 ReActAgent
        return newAgent.getAgent();
    };
}

2、子agent实例注册工具和skill
/**
* 确保初始化（延迟初始化模式）
* 支持：1. Spring 注入后初始化 2. AgentScope 框架创建新实例时初始化
*/
protected void ensureInitialized() {
if (!initialized) {
synchronized (this) {
if (!initialized) {
this.toolkit = createToolkit();
this.skillBox = createSkillBox(toolkit);
this.hooks = getHooks();
this.agent = buildAgent();
initialized = true;

                log.info("Agent [{}] initialized with skillBox: {}", getName(),
                        skillBox != null ? skillBox.getAllSkillIds() : "none");
            }
        }
    }
}

3、子agentskill:
/**
* 创建并配置 SkillBox，流程：
* 1. 从 classpath 批量加载 skill
* 2. 逐个委托子类绑定 tools
* 3. 注册 skill-load tool
*
* @param toolkit 共享的 Toolkit 实例
* @return 配置好的 SkillBox
*/
public SkillBox createSkillBox(Toolkit toolkit) {
SkillBox skillBox = new SkillBox(toolkit);
this.toolkit = toolkit; // 保存引用

    log.info("[{}] Starting to load skills from path: {}", configName(), getSkillsResourcePath());

    try {
        // 使用 PathMatchingResourcePatternResolver 加载所有 .md 文件
        List<AgentSkill> skills = loadSkillsFromClasspath();
        log.info("[{}] Found {} skills in classpath", configName(), skills.size());
        
        for (AgentSkill skill : skills) {
            log.info("[{}] Loaded skill: {} - {}", configName(), skill.getName(), skill.getDescription());
            bindTools(skillBox, skill);
        }
        
        if (skills.isEmpty()) {
            log.warn("[{}] No skills found, using fallback registration", configName());
            fallbackRegister(skillBox);
        }
    } catch (Exception e) {
        log.error("[{}] Failed to load skills from classpath: {}", configName(), e.getMessage(), e);
        fallbackRegister(skillBox);
    }

    
    int skillCount = skillBox.getAllSkillIds().size();
    log.info("[{}] SkillBox configured with {} skills: {}", configName(), skillCount, skillBox.getAllSkillIds());
    
    if (skillCount == 0) {
        log.error("[{}] WARNING: No skills loaded! Check if skill files exist in classpath: {}", 
                configName(), getSkillsResourcePath());
    }
    
    return skillBox;
}

4\skill绑定工具：
protected void register(SkillBox skillBox, AgentSkill skill, Object toolsBean) {
log.info("[{}] Registering skill: {} - {}", configName(), skill.getName(), toolsBean.getClass().getSimpleName());
skillBox.registration()
.skill(skill)
.tool(toolsBean)
.apply();
}

5、主agent调用子agent成功 决策需要调用子agent 但是子agent在进行工具选择时报错
2026-03-11 02:32:52,706 [ - /// - ] ERROR subagent.SubAgentTool - Error in streaming execution: Cannot add messages without tool results when pending tool calls exist. Pending IDs: [call_b7b69c82f3264a09a89c9d05]
java.lang.IllegalStateException: Cannot add messages without tool results when pending tool calls exist. Pending IDs: [call_b7b69c82f3264a09a89c9d05]
at io.agentscope.core.ReActAgent.validateAndAddToolResults(ReActAgent.java:335)
at io.agentscope.core.ReActAgent.doCall(ReActAgent.java:256)
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:132)
at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:129)
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:158)
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:158)
at reactor.core.publisher.Operators$ScalarSubscription.request(Operators.java:2570)
at reactor.core.publisher.MonoFlatMap$FlatMapMain.request(MonoFlatMap.java:194)
at reactor.core.publisher.MonoFlatMap$FlatMapMain.request(MonoFlatMap.java:194)
at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.request(FluxMapFuseable.java:171)
at reactor.core.publisher.MonoFlatMap$FlatMapMain.request(MonoFlatMap.java:194)
at reactor.core.publisher.MonoFlatMap$FlatMapMain.request(MonoFlatMap.java:194)
at reactor.core.publisher.Operators$MultiSubscriptionSubscriber.set(Operators.java:2366)
at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onSubscribe(FluxOnErrorResume.java:74)
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onSubscribe(MonoFlatMap.java:117)
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onSubscribe(MonoFlatMap.java:117)
at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onSubscribe(FluxMapFuseable.java:96)
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onSubscribe(MonoFlatMap.java:117)
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onSubscribe(MonoFlatMap.java:117)
at reactor.core.publisher.FluxFlatMap.trySubscribeScalarMap(FluxFlatMap.java:193)
at reactor.core.publisher.MonoFlatMap.subscribeOrReturn(MonoFlatMap.java:53)
at reactor.core.publisher.InternalMonoOperator.subscribe(InternalMonoOperator.java:63)
at reactor.core.publisher.MonoUsing.subscribe(MonoUsing.java:109)
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:53)
at reactor.core.publisher.Mono.subscribe(Mono.java:4576)
at reactor.core.publisher.Mono.subscribeWith(Mono.java:4641)
at reactor.core.publisher.Mono.subscribe(Mono.java:4542)
at reactor.core.publisher.Mono.subscribe(Mono.java:4478)
at reactor.core.publisher.Mono.subscribe(Mono.java:4450)
at io.agentscope.core.agent.AgentBase.lambda$createEventStream$26(AgentBase.java:707)
at reactor.core.publisher.FluxCreate.subscribe(FluxCreate.java:97)
at reactor.core.publisher.FluxPublishOn.subscribeOrReturn(FluxPublishOn.java:92)
at reactor.core.publisher.InternalFluxOperator.subscribe(InternalFluxOperator.java:55)
at reactor.core.publisher.FluxDeferContextual.subscribe(FluxDeferContextual.java:57)
at reactor.core.publisher.InternalMonoOperator.subscribe(InternalMonoOperator.java:76)
at reactor.core.publisher.MonoDeferContextual.subscribe(MonoDeferContextual.java:55)
at reactor.core.publisher.InternalMonoOperator.subscribe(InternalMonoOperator.java:76)
at reactor.core.publisher.MonoDeferContextual.subscribe(MonoDeferContextual.java:55)
at reactor.core.publisher.Mono.subscribe(Mono.java:4576)
at reactor.core.publisher.MonoSubscribeOn$SubscribeOnSubscriber.run(MonoSubscribeOn.java:126)
at reactor.core.scheduler.WorkerTask.call(WorkerTask.java:84)
at reactor.core.scheduler.WorkerTask.call(WorkerTask.java:37)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
2026-03-11 02:32:52,706 [ - /// - ] INFO hook.AgentMonitorHook - [MONITOR] [Coordinator] tool output: [Error: Execution error: Cannot add messages without tool results when pending tool calls exist. Pending IDs: [call_b7b69c82f3264a09a89c9d05]]
2026-03-11 02:32:52,706 [ - /// - ] INFO hook.AgentMonitorHook - [MONITOR] [Coordinator] tool result: TechnicalSupport -> Error: Execution error: Cannot add messages without tool results when pending tool calls exist. Pending IDs: [call_b7b69...

[chensk0601]

我也遇到了，当工具没有输出时，就会报这个错误。
2026-03-13 23:48:56.308 [http-nio-0.0.0.0-8080-exec-10] INFO JsonRpcTransportWrapper - Handling non-streaming request, returning JSON response
2026-03-13 23:48:56.308 [pool-2-thread-7] ERROR AgentScopeAgentExecutor - [39111226-20e5-4dca-9395-ce39edc5ff0a] Agent execution failed
java.lang.IllegalStateException: Cannot add messages without tool results when pending tool calls exist. Pending IDs: [call_118b52f517de4420ade572fe]
at io.agentscope.core.ReActAgent.validateAndAddToolResults(ReActAgent.java:335) ~[skills-agent.jar:?]
at io.agentscope.core.ReActAgent.doCall(ReActAgent.java:256) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:133) ~[skills-agent.jar:?]
at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:130) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:159) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:159) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:159) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:159) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:159) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:159) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:159) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:159) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:159) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:159) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:159) ~[skills-agent.jar:?]
at reactor.core.publisher.Operators$ScalarSubscription.request(Operators.java:2565) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.request(MonoFlatMap.java:195) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.request(MonoFlatMap.java:195) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.request(MonoFlatMap.java:195) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.request(MonoFlatMap.java:195) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.request(MonoFlatMap.java:195) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.request(MonoFlatMap.java:195) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.request(MonoFlatMap.java:195) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.request(MonoFlatMap.java:195) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.request(MonoFlatMap.java:195) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.request(MonoFlatMap.java:195) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.request(MonoFlatMap.java:195) ~[skills-agent.jar:?]
at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.request(FluxMapFuseable.java:172) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.request(MonoFlatMap.java:195) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.request(MonoFlatMap.java:195) ~[skills-agent.jar:?]
at reactor.core.publisher.Operators$MultiSubscriptionSubscriber.set(Operators.java:2361) ~[skills-agent.jar:?]
at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onSubscribe(FluxOnErrorResume.java:75) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onSubscribe(MonoFlatMap.java:118) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onSubscribe(MonoFlatMap.java:118) ~[skills-agent.jar:?]
at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onSubscribe(FluxMapFuseable.java:96) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onSubscribe(MonoFlatMap.java:118) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onSubscribe(MonoFlatMap.java:118) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onSubscribe(MonoFlatMap.java:118) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onSubscribe(MonoFlatMap.java:118) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onSubscribe(MonoFlatMap.java:118) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onSubscribe(MonoFlatMap.java:118) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onSubscribe(MonoFlatMap.java:118) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onSubscribe(MonoFlatMap.java:118) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onSubscribe(MonoFlatMap.java:118) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onSubscribe(MonoFlatMap.java:118) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onSubscribe(MonoFlatMap.java:118) ~[skills-agent.jar:?]
at reactor.core.publisher.FluxFlatMap.trySubscribeScalarMap(FluxFlatMap.java:193) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoFlatMap.subscribeOrReturn(MonoFlatMap.java:53) ~[skills-agent.jar:?]
at reactor.core.publisher.InternalMonoOperator.subscribe(InternalMonoOperator.java:62) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoUsing.subscribe(MonoUsing.java:109) ~[skills-agent.jar:?]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:54) ~[skills-agent.jar:?]
at reactor.core.publisher.Mono.subscribe(Mono.java:4569) ~[skills-agent.jar:?]
at reactor.core.publisher.Mono.subscribeWith(Mono.java:4634) ~[skills-agent.jar:?]
at reactor.core.publisher.Mono.subscribe(Mono.java:4535) ~[skills-agent.jar:?]
at reactor.core.publisher.Mono.subscribe(Mono.java:4471) ~[skills-agent.jar:?]
at reactor.core.publisher.Mono.subscribe(Mono.java:4443) ~[skills-agent.jar:?]
at io.agentscope.core.agent.AgentBase.lambda$createEventStream$26(AgentBase.java:707) ~[skills-agent.jar:?]
at reactor.core.publisher.FluxCreate.subscribe(FluxCreate.java:97) ~[skills-agent.jar:?]
at reactor.core.publisher.InternalFluxOperator.subscribe(InternalFluxOperator.java:67) ~[skills-agent.jar:?]
at reactor.core.publisher.FluxDeferContextual.subscribe(FluxDeferContextual.java:58) ~[skills-agent.jar:?]
at reactor.core.publisher.Flux.subscribe(Flux.java:8888) ~[skills-agent.jar:?]
at reactor.core.publisher.Flux.blockLast(Flux.java:2815) ~[skills-agent.jar:?]
at io.agentscope.core.a2a.server.executor.AgentScopeAgentExecutor.processTaskBlocking(AgentScopeAgentExecutor.java:188) ~[skills-agent.jar:?]
at io.agentscope.core.a2a.server.executor.AgentScopeAgentExecutor.execute(AgentScopeAgentExecutor.java:111) ~[skills-agent.jar:?]
at io.a2a.server.requesthandlers.DefaultRequestHandler$2.run(DefaultRequestHandler.java:640) ~[skills-agent.jar:?]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
at java.lang.Thread.run(Thread.java:1583) [?:?]
Suppressed: java.lang.Exception: #block terminated with an error
at reactor.core.publisher.BlockingSingleSubscriber.blockingGet(BlockingSingleSubscriber.java:104) ~[skills-agent.jar:?]
at reactor.core.publisher.Flux.blockLast(Flux.java:2816) ~[skills-agent.jar:?]
at io.agentscope.core.a2a.server.executor.AgentScopeAgentExecutor.processTaskBlocking(AgentScopeAgentExecutor.java:188) ~[skills-agent.jar:?]
at io.agentscope.core.a2a.server.executor.AgentScopeAgentExecutor.execute(AgentScopeAgentExecutor.java:111) ~[skills-agent.jar:?]
at io.a2a.server.requesthandlers.DefaultRequestHandler$2.run(DefaultRequestHandler.java:640) ~[skills-agent.jar:?]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
at java.lang.Thread.run(Thread.java:1583) [?:?]

[tangzhe7]

我这也遇到这个问题，消息列表如下，可以确定的事实是：大模型编造了一个不存在的工具ocr_image

'assistant','[{"text":"现在我需要执行第九个子任务：合理性检查。让我调用reasonablenessCheck工具来检查材料合理性：\n\n\n\n"},{"content":"{\"message\": \"请检查目录 /tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d 中的材料合理性\"}","id":"call_5dbb8a18a7c640faa3d55f","input":{"message":"请检查目录 /tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d 中的材料合理性"},"metadata":{},"name":"reasonablenessCheck"}]'
'assistant','[{"content":"{\"varKey\": \"manageManualEffectiveDateTime\"}","id":"call_bd633271ff914edfbbed6f","input":{"varKey":"manageManualEffectiveDateTime"},"metadata":{},"name":"readCBProjectVar"},{"content":"{\"varKey\": \"internalReviewStartDate\"}","id":"call_b0db485122c7490ca2c6a2","input":{"varKey":"internalReviewStartDate"},"metadata":{},"name":"readCBProjectVar"},{"content":"{\"varKey\": \"internalReviewEndDate\"}","id":"call_847a954294334035b0d0bf","input":{"varKey":"internalReviewEndDate"},"metadata":{},"name":"readCBProjectVar"},{"content":"{\"varKey\": \"managementReviewDate\"}","id":"call_b22a465f195945abb6f4b9","input":{"varKey":"managementReviewDate"},"metadata":{},"name":"readCBProjectVar"}]'
'tool','[{"id":"call_bd633271ff914edfbbed6f","metadata":{},"name":"readCBProjectVar","output":[{"text":"2025-04-01"}]}]'
'tool','[{"id":"call_b0db485122c7490ca2c6a2","metadata":{},"name":"readCBProjectVar","output":[{"text":"2025-12-08"}]}]'
'tool','[{"id":"call_847a954294334035b0d0bf","metadata":{},"name":"readCBProjectVar","output":[{"text":"2025-12-09"}]}]'
'tool','[{"id":"call_b22a465f195945abb6f4b9","metadata":{},"name":"readCBProjectVar","output":[{"text":"2025-12-17"}]}]'
'assistant','[{"content":"{\"folderPath\": \"/tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d\", \"keywords\": \"营业执照\", \"maxResults\": 5}","id":"call_0aa7dc76a6074adc93b1c0","input":{"folderPath":"/tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d","keywords":"营业执照","maxResults":5},"metadata":{},"name":"search_files_by_name"}]'
'tool','[{"id":"call_0aa7dc76a6074adc93b1c0","metadata":{},"name":"search_files_by_name","output":[{"text":"[\"/tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d/湖州宇尚高分子材料科技有限公司/湖州宇尚高分子材料科技有限公司/营业执照.jpg\"]"}]}]'
'assistant','[{"content":"{\"imagePath\": \"/tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d/湖州宇尚高分子材料科技有限公司/湖州宇尚高分子材料科技有限公司/营业执照.jpg\"}","id":"call_68c8a52cb3c64957ae9e74","input":{"imagePath":"/tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d/湖州宇尚高分子材料科技有限公司/湖州宇尚高分子材料科技有限公司/营业执照.jpg"},"metadata":{},"name":"ocr_image"}]'
'tool','[{"id":"call_5dbb8a18a7c640faa3d55f","metadata":{},"name":"reasonablenessCheck","output":[{"text":"session_id: 7a51765b-c9d7-49b0-8b9c-32ec55775270\n\n"}]}]'
'assistant','[{"text":"我需要完成合理性检查任务。根据reasonablenessCheck工具的调用，它正在处理中，但还没有返回结果。让我等待并查看是否有结果，或者如果需要，我可以尝试再次调用该工具。\n\n由于工具调用后没有立即返回结果，我需要检查当前任务状态，并确保完成该子任务。根据系统提示，当前子任务\"合理性检查\"处于\"in_progress\"状态，我需要获取其结果并标记为完成。\n\n让我再次尝试调用reasonablenessCheck工具来获取合理性检查结果：\n\n\n\n"},{"content":"{\"message\": \"请检查目录 /tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d 中的材料合理性\", \"session_id\": \"7a51765b-c9d7-49b0-8b9c-32ec55775270\"}","id":"call_45892278bf9a4ea8b1550e","input":{"message":"请检查目录 /tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d 中的材料合理性","session_id":"7a51765b-c9d7-49b0-8b9c-32ec55775270"},"metadata":{},"name":"reasonablenessCheck"}]'
'tool','[{"id":"call_45892278bf9a4ea8b1550e","metadata":{},"name":"reasonablenessCheck","output":[{"text":"Error: Execution error: Cannot add messages without tool results when pending tool calls exist. Pending IDs: [call_68c8a52cb3c64957ae9e74]"}]}]'
'assistant','[{"text":"让我查看当前子任务的状态，确认合理性检查的进展：\n\n\n"},{"content":"{\"subtask_idx\": [9]}","id":"call_c2284e2f4f9d4cf9a3bb95","input":{"subtask_idx":[9]},"metadata":{},"name":"view_subtasks"}]'
'tool','[{"id":"call_c2284e2f4f9d4cf9a3bb95","metadata":{},"name":"view_subtasks","output":[{"text":"\"Subtask at index 9:\\n\\\\n- [ ] [WIP] 合理性检查\\\\n\\\\t- Created At: 2026-03-18 17:07:56\\\\n\\\\t- Description: 使用reasonablenessCheck工具检查材料合理性\\\\n\\\\t- Expected Outcome: 确认材料内容是否合理可信\\\\n\\\\t- State: in_progress\\\\n\\n\\n\""}]}]'
'assistant','[{"text":"让我再次尝试调用reasonablenessCheck工具来获取合理性检查结果，这次确保使用正确的session_id：\n\n\n\n"},{"content":"{\"message\": \"请检查目录 /tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d 中的材料合理性\", \"session_id\": \"7a51765b-c9d7-49b0-8b9c-32ec55775270\"}","id":"call_ec92d7dec3744166a6a4e2","input":{"message":"请检查目录 /tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d 中的材料合理性","session_id":"7a51765b-c9d7-49b0-8b9c-32ec55775270"},"metadata":{},"name":"reasonablenessCheck"}]'
'tool','[{"id":"call_ec92d7dec3744166a6a4e2","metadata":{},"name":"reasonablenessCheck","output":[{"text":"Error: Execution error: Cannot add messages without tool results when pending tool calls exist. Pending IDs: [call_68c8a52cb3c64957ae9e74]"}]}]'

[tangzhe7]

我找到原因了，在reason时大模型幻觉生成错误的工具名称--->错误工具名的msg加入到memory--->isFinish（幻觉未找到工具）返回true，子Agent正常退出--->saveSession---->主Agent再次使用同一个sessionId调用子Agent---->loadSession(memory最后一条包含工具调用)----->输入的msg只有一条消息,memroy最后一条消息是工具调用--->校验函数报错

[chensk0601]

我已经提了pr快一周了 发自我的iPhone

…

------------------ 原始邮件 ------------------ From: tangzhe7 ***@***.***> 发送时间: 03/19/2026, 22:15 To: agentscope-ai/agentscope-java ***@***.***> 抄送: 凯凯 ***@***.***>, Comment ***@***.***> Subject: Re: [agentscope-ai/agentscope-java] [Bug]:agentscope agent as tools模式下流式场景报错：Cannot add messages without tool results when pending tool calls exist. (Issue #918) tangzhe7 left a comment (agentscope-ai/agentscope-java#918) 我找到原因了，在reason时大模型幻觉生成错误的工具名称--->错误工具名的msg加入到memory--->isFinish（幻觉未找到工具）返回true，子Agent正常退出--->saveSession---->主Agent再次使用同一个sessionId调用子Agent---->loadSession(memory最后一条包含工具调用)----->输入的msg只有一条消息,memroy最后一条消息是工具调用--->校验函数报错 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[tangzhe7]

我已经提了pr快一周了

发自我的iPhone
…

------------------ 原始邮件 ------------------
From: tangzhe7 @.>
发送时间: 03/19/2026, 22:15
To: agentscope-ai/agentscope-java @.>
抄送: 凯凯 @.>, Comment @.>
Subject: Re: [agentscope-ai/agentscope-java] [Bug]:agentscope agent as tools模式下流式场景报错：Cannot add messages without tool results when pending tool calls exist. (Issue #918)

tangzhe7 left a comment (agentscope-ai/agentscope-java#918)

我找到原因了，在reason时大模型幻觉生成错误的工具名称--->错误工具名的msg加入到memory--->isFinish（幻觉未找到工具）返回true，子Agent正常退出--->saveSession---->主Agent再次使用同一个sessionId调用子Agent---->loadSession(memory最后一条包含工具调用)----->输入的msg只有一条消息,memroy最后一条消息是工具调用--->校验函数报错

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

我已经提了pr快一周了

发自我的iPhone
…

------------------ 原始邮件 ------------------
From: tangzhe7 @.>
发送时间: 03/19/2026, 22:15
To: agentscope-ai/agentscope-java @.>
抄送: 凯凯 @.>, Comment @.>
Subject: Re: [agentscope-ai/agentscope-java] [Bug]:agentscope agent as tools模式下流式场景报错：Cannot add messages without tool results when pending tool calls exist. (Issue #918)

tangzhe7 left a comment (agentscope-ai/agentscope-java#918)

我找到原因了，在reason时大模型幻觉生成错误的工具名称--->错误工具名的msg加入到memory--->isFinish（幻觉未找到工具）返回true，子Agent正常退出--->saveSession---->主Agent再次使用同一个sessionId调用子Agent---->loadSession(memory最后一条包含工具调用)----->输入的msg只有一条消息,memroy最后一条消息是工具调用--->校验函数报错

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

合并到主干然后发布出来没那么快，业务侧等不到的发布，我在想是采用你的办法还是在loadSession的时候去处理，里面的场景有点多,比如需要用户确认工具执行的场景下？

[chensk0601]

临时试下我那个PR的内容，看能否解决你这个问题，目前我看还没合进去。

…

On Mar 19, 2026, at 17:26, tangzhe7 ***@***.***> wrote: tangzhe7 left a comment (agentscope-ai/agentscope-java#918) <#918 (comment)> 我这也遇到这个问题，消息列表如下 'assistant','[{"text":"现在我需要执行第九个子任务：合理性检查。让我调用reasonablenessCheck工具来检查材料合理性：\n\n\n\n"},{"content":"{\"message\": \"请检查目录 /tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d 中的材料合理性\"}","id":"call_5dbb8a18a7c640faa3d55f","input":{"message":"请检查目录 /tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d 中的材料合理性"},"metadata":{},"name":"reasonablenessCheck"}]' 'assistant','[{"content":"{\"varKey\": \"manageManualEffectiveDateTime\"}","id":"call_bd633271ff914edfbbed6f","input":{"varKey":"manageManualEffectiveDateTime"},"metadata":{},"name":"readCBProjectVar"},{"content":"{\"varKey\": \"internalReviewStartDate\"}","id":"call_b0db485122c7490ca2c6a2","input":{"varKey":"internalReviewStartDate"},"metadata":{},"name":"readCBProjectVar"},{"content":"{\"varKey\": \"internalReviewEndDate\"}","id":"call_847a954294334035b0d0bf","input":{"varKey":"internalReviewEndDate"},"metadata":{},"name":"readCBProjectVar"},{"content":"{\"varKey\": \"managementReviewDate\"}","id":"call_b22a465f195945abb6f4b9","input":{"varKey":"managementReviewDate"},"metadata":{},"name":"readCBProjectVar"}]' 'tool','[{"id":"call_bd633271ff914edfbbed6f","metadata":{},"name":"readCBProjectVar","output":[{"text":"2025-04-01"}]}]' 'tool','[{"id":"call_b0db485122c7490ca2c6a2","metadata":{},"name":"readCBProjectVar","output":[{"text":"2025-12-08"}]}]' 'tool','[{"id":"call_847a954294334035b0d0bf","metadata":{},"name":"readCBProjectVar","output":[{"text":"2025-12-09"}]}]' 'tool','[{"id":"call_b22a465f195945abb6f4b9","metadata":{},"name":"readCBProjectVar","output":[{"text":"2025-12-17"}]}]' 'assistant','[{"content":"{\"folderPath\": \"/tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d\", \"keywords\": \"营业执照\", \"maxResults\": 5}","id":"call_0aa7dc76a6074adc93b1c0","input":{"folderPath":"/tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d","keywords":"营业执照","maxResults":5},"metadata":{},"name":"search_files_by_name"}]' 'tool','[{"id":"call_0aa7dc76a6074adc93b1c0","metadata":{},"name":"search_files_by_name","output":[{"text":"[\"/tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d/湖州宇尚高分子材料科技有限公司/湖州宇尚高分子材料科技有限公司/营业执照.jpg\"]"}]}]' 'assistant','[{"content":"{\"imagePath\": \"/tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d/湖州宇尚高分子材料科技有限公司/湖州宇尚高分子材料科技有限公司/营业执照.jpg\"}","id":"call_68c8a52cb3c64957ae9e74","input":{"imagePath":"/tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d/湖州宇尚高分子材料科技有限公司/湖州宇尚高分子材料科技有限公司/营业执照.jpg"},"metadata":{},"name":"ocr_image"}]' 'tool','[{"id":"call_5dbb8a18a7c640faa3d55f","metadata":{},"name":"reasonablenessCheck","output":[{"text":"session_id: 7a51765b-c9d7-49b0-8b9c-32ec55775270\n\n"}]}]' 'assistant','[{"text":"我需要完成合理性检查任务。根据reasonablenessCheck工具的调用，它正在处理中，但还没有返回结果。让我等待并查看是否有结果，或者如果需要，我可以尝试再次调用该工具。\n\n由于工具调用后没有立即返回结果，我需要检查当前任务状态，并确保完成该子任务。根据系统提示，当前子任务\"合理性检查\"处于\"in_progress\"状态，我需要获取其结果并标记为完成。\n\n让我再次尝试调用reasonablenessCheck工具来获取合理性检查结果：\n\n\n\n"},{"content":"{\"message\": \"请检查目录 /tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d 中的材料合理性\", \"session_id\": \"7a51765b-c9d7-49b0-8b9c-32ec55775270\"}","id":"call_45892278bf9a4ea8b1550e","input":{"message":"请检查目录 /tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d 中的材料合理性","session_id":"7a51765b-c9d7-49b0-8b9c-32ec55775270"},"metadata":{},"name":"reasonablenessCheck"}]' 'tool','[{"id":"call_45892278bf9a4ea8b1550e","metadata":{},"name":"reasonablenessCheck","output":[{"text":"Error: Execution error: Cannot add messages without tool results when pending tool calls exist. Pending IDs: [call_68c8a52cb3c64957ae9e74]"}]}]' 'assistant','[{"text":"让我查看当前子任务的状态，确认合理性检查的进展：\n\n\n"},{"content":"{\"subtask_idx\": [9]}","id":"call_c2284e2f4f9d4cf9a3bb95","input":{"subtask_idx":[9]},"metadata":{},"name":"view_subtasks"}]' 'tool','[{"id":"call_c2284e2f4f9d4cf9a3bb95","metadata":{},"name":"view_subtasks","output":[{"text":"\"Subtask at index 9:\\n\\\\n- [ ] [WIP] 合理性检查\\\\n\\\\t- Created At: 2026-03-18 17:07:56\\\\n\\\\t- Description: 使用reasonablenessCheck工具检查材料合理性\\\\n\\\\t- Expected Outcome: 确认材料内容是否合理可信\\\\n\\\\t- State: in_progress\\\\n\\n\\n\""}]}]' 'assistant','[{"text":"让我再次尝试调用reasonablenessCheck工具来获取合理性检查结果，这次确保使用正确的session_id：\n\n\n\n"},{"content":"{\"message\": \"请检查目录 /tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d 中的材料合理性\", \"session_id\": \"7a51765b-c9d7-49b0-8b9c-32ec55775270\"}","id":"call_ec92d7dec3744166a6a4e2","input":{"message":"请检查目录 /tmp/cbProjectReviewMaterial/cbp-da14ec7e-1ea4-11f1-9b6d-61a0c834a70d 中的材料合理性","session_id":"7a51765b-c9d7-49b0-8b9c-32ec55775270"},"metadata":{},"name":"reasonablenessCheck"}]' 'tool','[{"id":"call_ec92d7dec3744166a6a4e2","metadata":{},"name":"reasonablenessCheck","output":[{"text":"Error: Execution error: Cannot add messages without tool results when pending tool calls exist. Pending IDs: [call_68c8a52cb3c64957ae9e74]"}]}]' — Reply to this email directly, view it on GitHub <#918 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANVDS4U6XWFQ4IWOO6W7SML4RO4MTAVCNFSM6AAAAACWNY7N42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAOBYHA2DCMRSGU>. You are receiving this because you commented.

[Alexxigang]

I traced the current code path locally. The core problem appears to be that PendingToolRecoveryHook is opt-in today, so after a session restores memory with orphaned pending tool calls, a normal follow-up user message still hits the hard validation error instead of being auto-patched. I am working on a fix to make the recovery path cover this session-resume / agent-as-tool scenario by default, and I will add regression tests around restored pending tool calls and explicit opt-out behavior.

[Alexxigang]

Opened PR #1182 to fix the default pending-tool recovery behavior after session restore, with regression coverage for both the default and explicit opt-out paths.