This detailed breakdown of Cloudflare's approach to integrating AI in their development workflow is quite comprehensive and showcases multiple layers of sophistication. Let’s break down each act to understand how they’ve structured this system:
Act 1: The Infrastructure Layer
Backstage Integration:
- Backstage: Used as the internal developer portal, it tracks services, APIs, systems, databases, teams, and ownership mappings.
- MCP Servers: These servers are available through an MCP Portal, enabling agents to look up service owners, dependencies, API specs, etc.
AGENTS.md Generation:
- Purpose: To provide structured context about repositories to coding agents.
- Content: Includes repository details (runtime, test commands), navigation tips, conventions, boundaries, and dependencies.
- Process:
- Metadata is pulled from Backstage.
- Repository structure is analyzed for language, build system, etc.
- A capable model generates the AGENTS.md file.
- Merge requests are opened for team review.
AI Code Reviewer:
- Integration: Added as a GitLab CI component to automatically review merge requests (MRs).
- Process:
- MRs trigger the CI job which runs OpenCode with agents
Read the full article at The Cloudflare Blog
Want to create content about this topic? Use Nemati AI tools to generate articles, social posts, and more.





