feat: making it possible to configure sub-agent conversation contents in multi-agent compositions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 420
- Forks
- 60
- Avg merge
- 9h 30m
- Merged PRs (30d)
- 4
Description
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.
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 comparing the listed multi-agent patterns: flows in flows composition, agent in flows, manager workers, and swarms. Determine how caller-to-callee conversations are currently passed and define what configurable sub-agent context should mean for each pattern. Done means the conversation or message contents can be controlled across all named compositions.
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
- 32/100