Back to directory

Meta-Team

The reference implementation of a research paper on collaborative self-evolution for LLM-based multi-agent systems, where a team of agents reflects together after each task at the level of individual agents, their interactions, and the team's own organization.

Meta-Team

Meta-Team is built around the idea that a multi-agent system should evolve as a team, not only execute as one. After each task, the system reflects at three levels: an agent level, where prompt patches and new skills are added to an individual agent's scaffold; an interaction level, where teammate profiles and collaboration notes update how agents communicate; and a team level, where the shared constitution, organization and coordination rules themselves change. Preserving each agent's execution context and coordinating post-task communication lets agents exchange distributed evidence that drives this multi-scale evolution.

The repository is configured to run against any OpenAI-compatible LLM API, with published experiments using Claude Sonnet 4.6, and evaluates on coding and agentic benchmarks including SWE-bench Pro, BeyondSWE, LOCA-Bench, GAIA and LoCoBench, some of which require Docker images for the benchmark tasks.

It is a Python research implementation for the paper 'Evolve as a Team: Collaborative Self-Evolution for LLM-based Multi-Agent Systems,' requiring Python 3.10 or later.

More in Agent frameworks

See all 902
  • Recurse

    recurse.run

    A serverless harness that lets a coding agent design, test, and deploy its own specialist sub-agents as tools, MCP servers, or bots, defined by a schema-validated manifest.

  • ProofForge

    shulgin.is-a.dev

    An AI-agent pipeline that decomposes a mathematics problem, proves each piece, and formalizes the result in Lean 4 and Mathlib until the Lean kernel accepts it, with six of its proofs already merged into Google DeepMind's formal-conjectures repository.

  • local-coder

    github.com

    Builds a local coding-agent team on top of Ollama and OpenCode by detecting the machine's hardware, recommending models for seven specialist roles, and testing whether each assigned model can actually use tools, edit a repository and pass verification.