Skip to content

The operation process of the intelligent agent #1399

Closed

Description

@Farewell-CK

For instance, I employed multi-agent technology. Agent A is responsible for task distribution, Agent B is responsible for data preprocessing, Agent C is responsible for other tasks, and so on. Finally, there is an intelligent agent responsible for organizing the work of all the previous intelligent agents. Then I would like to know which specific agent is ultimately responsible for the delivery? Is it A or the last one? If someone could tell me, I would be extremely grateful. I am looking forward to receiving your notification regarding this process.

Activity

  1. added
    core[Component] This issue is related to the core interface and implementation
    on Jun 14, 2025
  2. Farewell-CK commented on Jun 14, 2025

    @Farewell-CK
    Author

    第一种情况:

    graph TD
        subgraph 多智能体协作流程
            A[A 智能体: 任务分发] --> B[B 智能体: 数据预处理];
            A --> C[C 智能体: 其他工作];
            A --> D[...]
            
            subgraph 工作执行
                B -- 处理完成 --> E{汇总};
                C -- 处理完成 --> E;
                D -- 处理完成 --> E;
            end
    
            E -- 所有结果 --> A;
            A -- 整合后 --> F[🏆 最终交付];
        end
    
    Loading

    第二种情况:

    graph TD
        subgraph 多智能体协作流程
            A[A 智能体: 任务分发] --> B[B 智能体: 数据预处理];
            B -- 预处理数据 --> C[C 智能体: 其他工作];
            C -- 处理结果 --> D[D 智能体: 整合与整理];
            D -- 整合所有工作 --> E[🏆 最终交付];
        end
    
    Loading
  3. Farewell-CK commented on Jun 14, 2025

    @Farewell-CK
    Author

    Sorry, now I have understood this principle. However, I encountered a rather strange problem. When I used ADK to build a customer service system, a pre-sales agent, a post-sales agent, and a quotation agent. During the final execution, I would receive one or more similar responses - that is, multiple agents replied to me. But I only wanted one answer, yet I received three answers.

  4. added
    models[Component] This issue is related to model support
    on Jun 14, 2025
  5. DeanChensj commented on Jun 17, 2025

    @DeanChensj
    Collaborator

    Hi @Farewell-CK , for your 1st question, ADK use the handoff pattern so the last agent will return the result.

    For your 2nd question, how is your agent tree look like? Do you have a minimal example to reproduce the issue?

  6. added
    question[Component] This issue is asking a question or clarification
    and removed
    models[Component] This issue is related to model support
    on Jun 17, 2025
  7. self-assigned this
    on Jun 17, 2025
  8. Farewell-CK commented on Jun 18, 2025

    @Farewell-CK
    Author

    Image
    I am glad to receive your reply. The handoff you just mentioned is shown in the green box. When using these agents, does the handoff exist by default? I understand that the handoff will be done by default. You also mentioned mode switching. Can you tell me in detail how to do this mode switching? Or where can I see the relevant content of mode switching in the document?

  9. DeanChensj commented on Jun 18, 2025

    @DeanChensj
    Collaborator

    Hi @Farewell-CK , I'm not sure what do you mean by mode switching.

  10. Farewell-CK commented on Jun 18, 2025

    @Farewell-CK
    Author

    Image
    Hi @DeanChensj Look at the red box. Thanks!

  11. DeanChensj commented on Jun 22, 2025

    @DeanChensj
    Collaborator

    You might take a look at https://google.github.io/adk-docs/agents/multi-agents/ for multi-agent system

  12. added theissue type on Jul 2, 2025
  13. locked and limited conversation to collaborators on Jul 2, 2025
  14. converted this issue into a discussion #1753 on Jul 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

core[Component] This issue is related to the core interface and implementationquestion[Component] This issue is asking a question or clarification

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions