feat: making it possible to configure sub-agent conversation contents in multi-agent compositions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 188
- Forks
- 23
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 4
Description
WayFlow (and Agent Spec) currently supports several multi-agent patterns: flows in flows composition, agent in flows, manager workers, swarms.
For all of these, the way the conversation/messages are passed from the caller to the callee are currently pre-determined and non configurable.
The goal of this feature would be to make that more configurable so that sub-agent context can be more controlled.
That would make it easier to get good accuracies in those use-cases.
As something similar will be added in Agent Spec, the WayFlow implementation should be compatible with it (cf. https://github.com/oracle/agent-spec/issues/51 )
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing multi-agent composition entry points for flows in flows, agents in flows, manager-workers, and swarms to map how caller messages reach each callee. Compare the intended configuration with Agent Spec issue 51, then define completion as configurable sub-agent context across all listed patterns while remaining compatible with Agent Spec.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100