Devin Bots
Intro
Devin Bots is the new name Cognition introduced on 17 November 2026 for persistent engineering teammates that own a longer-running goal and lead a team of Devin agents to get the work done. The official @cognition post at 17:03 UTC said “Meet Devin Bots,” and that a bot can go from writing firmware to merging thousands of PRs a week. The blog opens with “Today, we’re introducing Devin Bots,” and the product page is devin.ai/bots.
The name is distinct from the existing coding agent Devin. Devin is a single agent; a Devin Bot is a layer on top of it: the bot keeps the goal, splits the work across parallel Devins, and brings a person in only when a decision needs human judgment. Same-day coverage, including Fortune, used that distinction.
This entry records the new product name rather than re-filing Devin itself. The first-party sources are the official blog and product page; the official X post is the original announcement link.
Advertisement
Explain
Cognition describes a Devin Bot as a persistent agent with its own memory, identity, and permissions. It breaks down an ongoing goal, coordinates multiple Devins to plan, test, and prepare pull requests, and operates inside the repository access, budgets, and human-review rules a team sets. The public pitch stresses that a bot retains context across sessions, rather than ending when a single task is done.
The official examples span a wide range of software work, from firmware to merging large volumes of PRs. Public discussion of the launch also described hand-offs such as a QA bot finding a bug and passing it to a developer bot. The underlying claim is the same: the unit of productivity is shifting from a single agent in one session to a bot that owns an outcome and leads a team of agents.
Availability and pricing follow Cognition’s product and plan pages. Public materials place the capability on Max and Team plans (Max has been listed at $200 per month); the exact inclusion, permission model, and “what a bot may merge without a human reading it” are configured in the product. Do not confuse Devin Bots with unrelated bot or avatar experiments that appeared in the same news cycle.
Usage
Start with the official post Introducing Devin Bots, then use devin.ai/bots for setup. The intended use is to give a bot an ongoing goal, let it split work across Devins in parallel, and have it contact a person only for approvals or key decisions. Teams should set repository access, budgets, and clear rules for which changes can merge automatically.
Cognition has also said a bot can be reached over Slack, text, or a call, not only inside a single chat session. Channels, permissions, and plan limits should be checked on the product page at the time you sign up.
If you only need a single coding agent for one task, that is the existing Devin, not this new name. When evaluating a bot, the practical questions are whether it really keeps context across sessions, what it is allowed to merge on its own, and whether the review rules match the team’s release risk.