Hub page labels the GAIA agent a "Python package" though it ships as a native binary #4854

Activity

1. github-actions

   added

   bugSomething isn't workingSomething isn't working

   p3

   on Oct 6, 2026
2. github-actions commented on Oct 6, 2026

   

   github-actionsbot

   on Oct 6, 2026 – with GitHub Actions

   Contributor

   More actions

   Looks like the page logic is already right and the live catalog is just stale. The GAIA manifest started declaring its npm package (@amd-gaia/gaia) on Sept 24, but the hub only updates that field when the agent is published again. The live entry still has no npm package, so the page falls back to "Python package".

   Next step: republish the gaia agent to the hub (or include it in the v0.25 publish), then check that hub.amd-gaia.ai/index.json lists npm_package for gaia. That should fix both the install card and the "no Python needed" note, with no website change.

   🔍 Technical details

   • hub/agents/gaia/python/gaia-agent.yaml:7 has had npm_package: "@amd-gaia/gaia" since fix(hub): advertise declared agent distribution packages #3866 (bee77fc, 2026-09-24).
   • The live index.json entry for gaia currently has npm_package: null and language: "python".
   • workers/agent-hub/src/catalog.ts:110 copies npm_package from the manifest only on a new publish (useNew). Until then the old entry's value stays.
   • isNpmSidecar (website/src/data/catalog.ts:494) is true only when the npm install method exists, so both InstallCard.astro:26 and [id].astro:113 will switch over once the field is present.
   • One caveat after republish: the card will read "npm client + frozen sidecar". That's accurate, but if the page should say "native binary" outright, that's a copy change in InstallCard.astro. The schema drift in fix(hub): both published catalog schemas are stale #3542 is a separate problem; this fix doesn't depend on it.