Red Hat connects Developer Hub catalogs to AI coding agents for governance-aware scaffolding

Red Hat has published an engineering demonstration that connects an AI coding agent to Red Hat Developer Hub, allowing the agent to query a Backstage software catalog, read TechDocs and inspect software templates before proposing an application architecture.

The Sept. 15 post describes the open source RHDH Agentic project and a simulated insurance-company environment. In the demonstration, Claude Code uses Backstage CLI actions to explore more than 500 catalog entities across 14 fictional business domains. The same project can expose catalog actions through the Model Context Protocol.

Catalog data becomes agent context

The exercise starts with a developer asking for help building a payment-reconciliation service. Rather than immediately generating code, the agent first maps the catalog's domains, systems and components. It finds an existing reconciliation service, but catalog ownership and dependency metadata show that service handles a different payment flow.

The agent then reads organization-wide and domain-level handbooks stored in TechDocs. The fictional Claims domain prefers Kafka for asynchronous events, while the Billing and Payments handbook requires IBM MQ for payment-critical messaging. Red Hat's walkthrough shows the agent identifying that conflict and proposing a boundary pattern: consume the payment feed through IBM MQ, then publish internal reconciliation events to Kafka where the documented exception allows it.

The important point is not the specific architecture, which belongs to a fabricated scenario. It is the retrieval path. The agent's recommendations are grounded in maintained portal records instead of model memory or a general-purpose codebase search.

From discovery to scaffolding

The demonstration continues through API discovery and software-template selection. Catalog relations and embedded OpenAPI definitions provide integration endpoints and schemas. The agent then selects a Quarkus template that matches the simulated domain's golden-path tag and supplies parameters derived from the catalog research.

Its final output is a technology decision summary that links architectural choices back to their catalog sources. Red Hat positions that traceability as a way for technical leads and auditors to verify why an agent selected a framework, messaging system or service dependency.

What changes for platform teams

This is an engineering pattern, not a new Developer Hub product release. Teams still need accurate ownership metadata, current TechDocs, usable templates and governance rules in their internal developer portal. An incomplete catalog will give the agent incomplete organizational context.

For platform-engineering teams already investing in Backstage or Developer Hub, however, the example gives that work a second consumer. The catalog can act not only as a developer discovery surface but also as a structured context layer for coding agents. The RHDH Agentic repository includes setup instructions, recorded demo runs and the catalog-exploration tooling used in the walkthrough.