We’re introducing Devin Plugins, which give enterprises a way to manage the context and capabilities their agents use at scale. Plugins bundle skills, rules, MCP servers, hooks, and subagents, with consistent configuration and governance across local and cloud agents. Devin Plugins are compliant with the open standard for Agent Plugins.
We worked closely with BlackRock, whose engineering team had already been working on context management through their “bread-kit” framework (BlackRock Enterprise Agentic Development Kit), to shape Devin Plugins for the governance needs of large enterprises.
Working with BlackRock
BlackRock’s engineering team came to context management early. Bread-kit is BlackRock’s enterprise context layer for AI-assisted development, providing engineers and other builder personas with trusted standards, architectural guidance, domain knowledge, and skills directly within their workflows across multiple tools. It enables teams to create context once and distribute it consistently, helping both people and AI agents operate against the same approved knowledge base and patterns.
Context and skills are governed through Git-based ownership and versioning. By combining global standards with locally owned domain expertise, bread-kit improves quality, consistency, and productivity while maintaining the controls required for enterprise software development.
Working with BlackRock helped inform our work on governance in Devin Plugins.
“We didn’t see any great solutions for scaling context management and delivery across thousands of engineers and many different domains and tech stacks. We didn’t want a choose-your-own-adventure approach for each team, but also recognized the need for team and repo-specific context to coexist with vetted, global context in a unified approach. The framework evolved somewhat organically, initially, but has now been adopted across every team that is coding and every new engineer starts using it as part of their onboarding. We’re excited about the potential for leveraging Devin Plugins in bread-kit to take it to the next level.”
— Matt Sahn, Managing Director, Head of Aladdin Wealth Tech Engineering
“Enterprises need consistent governance for agent context and capabilities across local and cloud environments. With input from BlackRock, we designed Devin Plugins to provide that governance at scale using the open Agent Plugins standard.”
— Jared Palmer, VP of Engineering, Cognition
Plugins for enterprise context management
A plugin is a versioned bundle of agent configuration: skills the agent can invoke, rules that set standards and conventions, MCP servers that connect it to internal tools, hooks that automate actions and enforce policies at runtime, and subagents it can delegate to.
With Devin Plugins, teams can:
- Granularly govern context & capabilities. Organizations can centrally manage plugins and apply them at the enterprise, org, repo, or individual level, and they can declare plugins as required, endorsed, or forbidden at those levels. For example, an organization might have hooks that prevent agents from accessing production infrastructure and data, but make an exception for the SRE team.
- Track versions & review changes. Plugins can be backed by Git repositories, so changes are versioned, attributable to an author, and reviewed like any other code.
- Use the same configuration across local and cloud agents. Teams can carry the context, capabilities, and controls they’ve built across environments rather than maintaining separate configurations as more engineering work moves to the cloud.
- Bring in skills & plugins from other tools. Devin plugins are compliant with the emerging Agent Plugins standard for agent configuration, so teams are not locked into a single ecosystem.
Read more about how Plugins work in Devin’s docs. Organizations interested in Devin can learn more by talking to sales.