v2026.3
Perforce Agentic Gateway v2026.3
Reviewing and applying registry-server updates from the dashboard, plus more
reliable catalog and registry syncing.
claude mcp add pag -- uvx perforce-agentic-gateway@latestNew features
- Staged server updates. Available server updates now surface on the
server list and detail panel and route to a staged re-pin on the Config
tab: the form re-renders against the target version's schema, carrying over
existing values and prompting for any new required inputs, and Save
commits the version and config together.
Improvements
- Update detection for semver-versioned servers. The dashboard's update
indicator andpag__status'supdate_availablefield now appear for
servers pinned to a semantic version (e.g.1.2.0→1.3.0). - Rate-limited registries sync reliably. Throttling responses (429, or 503
withRetry-After) are now honored and retried in place instead of aborting
the listing — including the official MCP registry.
Bug fixes
- Registries added while the gateway is stopped are now fetched at the next start
instead of sitting "Not yet checked" until a manual refresh. - Catalog registry filter no longer shows "No catalog entries" for
registries other than the first. - Re-enabling a registry-sourced server through
pag__enable_serverno
longer re-prompts for inputs the disabled configuration already retained. - Corrupt catalog cache recovery no longer races a concurrent refresh into
deleting a freshly written, valid cache. - Sidebar project path now always shows the folder name in full and
emphasized, fixing cross-browser clipping and a design-system font-weight
issue.