volcano-sh / volcano-sh/agentcube
[lfx-mentorship-2026-June-August] Support multi-AgentCube Capability
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 167
- Forks
- 88
- Avg merge
- 44m
- Merged PRs (30d)
- 1
Description
- Description: At present, AgentCube launches a single agent for both Code Interpretation and agent runtime. However, we have now entered the era of multi-agent collaboration. Consequently, AgentCube aims to support multi-AgentCube orchestration, enabling multiple agents to collaborate on a single task, with AgentCube providing unified management of the lifecycle of these agents.
- Expected Outcome:
- Proposal
- Code(Including Unit test and E2E test)
- User guide and another related docs.
- Recommended Skills:
- Go, Kubernetes, agent
- Mentor(s):
- Zhonghu xu(@hzxuzhonghu, zhhxu2011@gmail.com)
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
No files, tests, or entry points are named. Start by mapping how AgentCube currently launches and manages the single agent, then define the multi-agent orchestration proposal and lifecycle boundaries. Done means an accepted proposal, implementation with unit and E2E tests, and the requested user guide and related documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100