Background
While implementing SOP support in AgentScope, we identified strong structural similarities between pipelines and SOPs — both require unified input interfaces, human-in-the-loop (HITL) handling, and orchestration of multi-agent operations. The key distinction is that pipelines operate on fixed, predefined logic, making them a natural and solid foundation for building SOPs.
Changes
- Introduce a
pipeline module in AgentScope
- Support a variety of pipeline types
Note
Unlike AgentScope 1.0, the goal of this new pipeline module is to provide more mature, well-encapsulated functionality, rather than limiting it to simple primitives like fanout or sequential. We aim to cover richer, more practical orchestration patterns.
If you have proposals for new pipeline types or designs, feel free to open a discussion and submit a proposal — contributions and ideas are welcome!
Background
While implementing SOP support in AgentScope, we identified strong structural similarities between pipelines and SOPs — both require unified input interfaces, human-in-the-loop (HITL) handling, and orchestration of multi-agent operations. The key distinction is that pipelines operate on fixed, predefined logic, making them a natural and solid foundation for building SOPs.
Changes
pipelinemodule in AgentScopeNote
Unlike AgentScope 1.0, the goal of this new pipeline module is to provide more mature, well-encapsulated functionality, rather than limiting it to simple primitives like
fanoutorsequential. We aim to cover richer, more practical orchestration patterns.If you have proposals for new pipeline types or designs, feel free to open a discussion and submit a proposal — contributions and ideas are welcome!