Agent Hub: Restructure — move production agents to hub/agents/

[kovtcharov-amd]

Context

Phase 0 of the Agent Hub platform. Production agents must be standalone packages that depend on the published amd-gaia PyPI package, not the source tree. This enables third-party contributors to follow the identical pattern.

Scope

Create hub/agents/ directory:

• hub/agents/python/{chat,doc,file,data,web,email,jira,blender,docker,summarize,sd,emr,routing}/
• hub/agents/cpp/{bash,health,wifi}/
• Each agent gets: gaia-agent.yaml (v0.1.0), pyproject.toml (depends on amd-gaia), proper package structure, tests, README

Strip src/gaia/agents/ to framework only:

• Keep: base/, tools/, registry.py, builder/
• Move everything else to hub/agents/python/

Update core packaging:

• setup.py removes agent packages from core wheel
• Add amd-gaia[agents] extras that installs all AMD production agent wheels
• KNOWN_TOOLS paths stay (tool mixins are framework code)

Update registry:

• _register_builtin_agents() keeps only builder
• All other agents discovered via gaia-agent.yaml scan at ~/.gaia/agents/ + installed wheel entry points
• Each agent starts at version 0.1.0, independently versioned

Dev workflow:

• pip install -e hub/agents/python/chat/ for editable development
• pip install -e ".[dev]" for framework development

Ref: Agent Hub plan Phase 0

[github-actions]

Scope looks right and lines up with the Phase 0 work in docs/plans/agent-hub.mdx. A few notes from a pass over the current tree before someone picks this up:

Agent list is stale. The issue lists 13 Python agents, but src/gaia/agents/ currently has 19 (incl. analyst, browser, code_index, connectors_demo, docqa, email, fileio). Decide per-agent: move to hub/agents/python/, keep in framework, or delete. The code agent in the issue is actually code_index in the tree.

Discovery primitive already exists. gaia-agent.yaml + ~/.gaia/agents/ scanning is wired up in src/gaia/agents/registry.py:291 (_register_builtin_agents) and used end-to-end by custom agents (see docs/guides/custom-agent.mdx and the builder agent). The restructure should reuse this — not invent a parallel mechanism — and add the entry-point side for installed wheels.

Open questions worth pinning down in the issue before coding:

• Will KNOWN_TOOLS mixins (rag, file_io, shell, vlm, sd, …) stay importable from gaia.agents.tools.* once non-framework agents move? Several extracted agents will need from gaia.agents.chat.tools.rag_tools import RAGToolsMixin to keep working.
• Does amd-gaia[agents] install all hub agents from PyPI or from local wheels at build time? Has implications for CI.
• C++ agents (bash, health, wifi) — are these existing or to-be-built? I don't see them in the tree.

Good candidate for the gaia-agent-builder Claude agent to scaffold the per-agent layout once the above are settled. Tagging @kovtcharov-amd for the open questions.