Monzo engineers discuss in-house AI coding agent: from Slack emoji to 1,800 daily tasks
In an AIE CODE podcast episode, Monzo engineers Felipe Felisola Caso and Francesco Galletta share the evolution of their in-house AI coding agent. The tool has expanded from a simple Slack interaction to authoring over 10% of all merged pull requests across the company and executing more than 1,800 tasks daily. The discussion highlights the 'multiplier' architecture enabling this scale, including an MCP gateway for internal tools, a sandboxed orchestration system compliant with banking regulations, and a platform strategy that treats the agent as a fundamental building block.
ImportanceMaterialEvidenceE2 unreplicatedWrite-upQuick
Felipe Felisola Caso and Francesco Galletta, technology leads at UK digital bank Monzo, recently detailed the development and operational impact of their internal AI coding agent on the AIE CODE podcast. According to the episode description, the agent originated as a simple feature triggered by emoji reactions in Slack but has since evolved into critical infrastructure capable of authoring over 10% of all merged pull requests (PRs) across the company and executing more than 1,800 automated tasks per day.
The guests attribute this rapid scaling not merely to model improvements but to Monzo's pre-existing 'lots of little multipliers' tech stack. Key architectural components include an MCP (Model Context Protocol) gateway connecting internal tools and knowledge bases, and a sandboxed agent orchestration system specifically designed for a regulated banking environment. These elements ensure security and control when AI processes sensitive financial code.
Furthermore, the interview explores how the agent functions as a platform-level 'building block,' extending beyond engineering support to handle incident responses, on-call data quality checks, and change requests from non-engineers. For readers interested in enterprise AI adoption, particularly within high-compliance industries seeking engineering efficiency breakthroughs, this episode offers specific insights into architectural choices and organizational adaptation.