GAIA Agents Hub
Target: Q2 2026 | Status: Planning | Priority: High
Overview
The GAIA Agents Hub is a platform for publishing, discovering, and running AI agents built on the GAIA SDK. It provides:- A searchable agent registry for browsing and installing agents
- An Agent Arena backed by AMD Strix Halo cloud hardware for remote testing
- A CI/CD pipeline for validating, packaging, and deploying agent submissions
- CLI integration via
gaia agentcommands for local install and publish workflows
Agents Hub
agents-hub.html - Browse and search published agentsAgent Arena
arena.html - Test agents live on Strix Halo hardwareSeed Agents
The Hub launches with existing GAIA agents as initial content:
Additional seeds expected when the underlying work lands:
- ComputerUseAgent (CUA) — planned for v0.21.0; see the CUA plan.
Core Components
1. Agent Registry
The central repository for discovering and installing agents.View Mockup
Open
docs/plans/mockups/agents-hub.html in browser- Browse and search agents by category, tags, and use case
- View ratings, download counts, and version history
- One-click “Try in Arena” or
gaia agent install <name> - AMD-maintained agents alongside community submissions
- Official agents maintained in
github.com/amd/gaia - Community agents submitted to
github.com/amd/gaia-agents
2. Agent Arena
Remote agent testing environment running on AMD Strix Halo hardware. Users can interact with any published agent without local installation.View Mockup
Open
docs/plans/mockups/arena.html in browser- Chat interface for testing any Hub agent
- Runs on AMD Strix Halo Developer Cloud infrastructure (NPU-enabled)
- Isolated sessions per user with usage limits
- Hardware and model info displayed for transparency
- No account required to try agents
- Each agent runs in a Docker container on Strix Halo hardware
- Sessions are isolated via container-level separation
- The Arena exposes a chat UI that proxies to the running agent’s API endpoint
- Session timeout and concurrency limits are enforced at the orchestration layer
3. Developer Profiles and Badges
A system for tracking contributions and recognizing active developers.View Mockup
Open
docs/plans/mockups/profile.html in browser
Profile Features:
- Public or private profile visibility (developer’s choice)
- Contribution history: published agents, versions, download stats
- Badge display based on contribution tiers above
4. Agent Quality Gates
Automated validation that every submitted agent must pass before it appears in the Hub.
Agents that fail these gates are not published. Authors receive detailed failure logs.
Agent Manifest Format
See also: Agent Manifest (#462)agent.yaml manifest is validated during the CI/CD pipeline. Required fields: name, version, author, description, category, model, min_gaia_version.
CLI Commands
Distribution Methods
Agent Lifecycle Commands
Technical Architecture
Agent Submission Pipeline
System Components
Arena Infrastructure
Arena sessions run on AMD Strix Halo Developer Cloud, a separate infrastructure initiative. Integration points:
Assumptions:
- Developer Cloud provides API for session management
- Developer Cloud supports Docker container execution
- Developer Cloud exposes Strix Halo NPU to containers
Access Model
Authentication uses AMD AI Developer Program SSO. Membership is free and open to all.
Implementation Phases
Phase 1: Foundation (Feb 2026)
Objective: Core infrastructure and MVP submission pipeline
Exit Criteria:
- AMD team can publish 3+ seed agents
- External contributor can submit a PR and see their agent published
- Agents are accessible via
gaia agent install <name>
Phase 2: Agent Arena (Mar 2026)
Objective: Live agent testing on AMD hardware
Exit Criteria:
- Anyone can try 10+ agents in Arena without signup
- Arena handles 50+ concurrent users
- Average response time < 3 seconds
Phase 3: Profiles and Ratings (Apr 2026)
Objective: Developer profiles, badges, and community ratings
Exit Criteria:
- Profiles display accurate badge tiers and stats
- Ratings are reflected in Hub search ranking
Phase 4: Public Launch (May-Jun 2026)
Objective: Public availability with documentation
Exit Criteria:
- 20+ agents in Hub (AMD + community)
- End-to-end publish and install workflow documented and tested
Quality Metrics
Open Questions
Technical
Operational
Risks and Mitigations
UI Mockups
Interactive HTML mockups are available indocs/plans/mockups/: