$ show agentscope-ai/AgentTeams
AgentTeams is a production-grade multi-agent orchestration platform that manages teams of LLM-powered worker agents on Kubernetes. It uses a central Manager controller that reconciles Custom Resource Definitions (Worker, Team, Human, Manager) with container backends (Docker, K8s), a Matrix chat layer for all agent communication, and an AI Gateway (Higress) for credential isolation. The system supports multiple worker runtimes (OpenClaw, QwenPaw, Hermes, DeepSeek Harness) through a plugin architecture, provides a CLI tool (`agt`) for resource management, and includes human-in-the-loop oversight via Matrix rooms. Key features include STS token-based credential management, role-based authorization, audit logging, file synchronization via MinIO/OSS, and a skill discovery and distribution system. The codebase is heavily tested with unit, integration, and end-to-end tests, but shows moderate technical drift due to legacy runtime coexistence (CoPaw EOL migration) and some duplicated shell scripts across runtimes.
The LLM identified 4 files worth highlighting for reuse:
In-memory implementation of the OSS client interface used for unit tests. Simulates ETag conflicts, conditional writes, and object listing without external dependencies. Reusable as a generic test fake for any blob storage abstraction.
Dual-layer audit logger that writes events to both structured logs and daily JSONL files in MinIO/OSS. Uses ETag-based optimistic concurrency to safely append entries to existing files. The pattern is portable to any object storage and provides a foundation for audit systems.
Abstract interface for AI Gateway operations (consumer management, route configuration, MCP server setup) with implementations for self-hosted Higress and Alibaba Cloud APIG. Demonstrates a clean adapter pattern that can be extracted to support any AI gateway.
Handles STS credential refresh via a credential provider sidecar (Unix domain socket) and serves temporary credentials to workers. The token refresh and caching logic is decoupled from the storage backend, making it reusable for any service needing short-lived cloud credentials.