Devin AI Changelog: Latest Features, Releases, and Product Updates
The Devin AI changelog is Cognition's official chronological record of feature updates, CLI improvements, security patches, and enterprise capabilities released for Devin. Tracking updates across web, desktop, and CLI channels helps engineering teams evaluate new capabilities like self-hosted Devin Outposts and automated code scanning. Pairing these agent upgrades with persistent workspaces ensures developer artifacts, audit histories, and generated code remain versioned and secure.
How to Track Devin AI Releases Across Web, Desktop, and Terminal Channels
When software engineering teams deploy autonomous coding agents into daily development cycles, silent runtime updates can break CI pipelines, alter sandbox execution boundaries, and invalidate local configurations without warning. The fix is not to freeze developer tooling, but to track Cognition's official Devin AI changelog and map version updates against your team's operational environment.
The Devin AI changelog is Cognition's official chronological record of feature updates, CLI improvements, security patches, and enterprise capabilities released for Devin. Because Devin operates across multiple distinct runtimes, updates roll out through three coordinated surfaces: the cloud web application, the Devin Desktop editor, and the Devin command-line interface (CLI). Understanding how these surfaces diverge prevents unexpected workflow interruptions and ensures engineering teams adopt new capabilities safely.
Release Cadence and Distribution Channels
Cognition delivers product updates on a bi-weekly release cadence across web, desktop, and CLI channels. In addition to regular bi-weekly feature cycles, Cognition ships point releases and targeted hotfixes as needed to address protocol stability, terminal rendering bottlenecks, and sandbox permissions.
The release pipeline divides updates into distinct channels:
- Devin Cloud Webapp: Cloud updates apply continuously to active sessions in the browser. These updates include visual interface improvements, sidebar navigation changes, automated code scans, and organization settings.
- Devin Desktop: The native desktop application receives scheduled desktop builds incorporating updated language server configurations, local terminal integrations, and editor window splits.
- Devin CLI: The terminal client operates on two channels: a stable track (such as the
v3000.6.xseries) and an insiders preview channel. The stable track prioritizes backward-compatible shell execution, Model Context Protocol (MCP) transport stability, and subagent orchestration.
Where Engineering Teams Access Official Release Notes
Tracking official documentation ensures that developers and DevOps engineers do not rely on third-party aggregators or outdated summaries. Cognition publishes release information across four primary destinations:
- Devin 2026 Release Notes: The official Devin 2026 Release Notes document platform-level updates, covering the web interface, enterprise security controls, automation triggers, and major infrastructure milestones.
- Devin CLI Stable Changelog: The Devin CLI Stable Changelog catalogs exact version changes for the command-line client, detailing command flags, slash commands, shell execution changes, and MCP client updates.
- The Devin Web Console: In-app notification sheets and release banners at app.devin.ai highlight newly released features directly within active workspaces.
- Cognition Engineering Blog: The official Devin Blog provides long-form technical architectural essays, benchmark analyses, and detailed walk-throughs of major milestone releases.
Major 2026 Platform Milestones: Devin Outposts and Automated Code Scans
The 2026 product updates for Devin reflect a deliberate evolution from single-turn code generation toward autonomous enterprise workflows. Rather than functioning solely as an interactive pair programmer, Devin has expanded into scheduled code audits, multi-repository maintenance, and private enterprise compute infrastructure. These capabilities allow development organizations to embed autonomous agents directly into production build pipelines and continuous compliance routines.
Tracking these platform updates helps engineering leaders identify when experimental features graduate into enterprise-ready tools. Two major 2026 milestones define this expansion: the launch of self-hosted Devin Outposts and the release of deep automated code scanning. Both capabilities address the strict isolation and security requirements of complex software architectures.
Orchestrating Self-Hosted Workers with Devin Outposts
Introduced in the July 22, 2026 platform release, Devin Outposts allows organizations to execute Devin workloads directly within their own self-hosted environments. Historically, running Devin required executing all shell commands, compilations, and tests inside Cognition's multi-tenant cloud Devboxes. While cloud Devboxes offer rapid provisioning, regulated industries and security-conscious enterprises frequently require source code and build pipelines to remain behind corporate firewalls.
Devin Outposts establishes a hybrid execution architecture:
- Centralized Cloud Brain: Devin's reasoning engine, planning heuristics, and high-level task decomposition remain in Cognition's managed cloud.
- Private Worker Nodes: Code checkout, terminal commands, compilation, and unit test execution occur on local infrastructure inside your corporate network.
- Outpost CLI Bootstrapping: Engineers can initialize and manage local workers using the
devin worker startcommand, connecting private nodes to the central coordinator without opening inbound network ports.
This architecture enables Devin to interact with internal database replicas, private package registries, and staging environments without requiring enterprise teams to route sensitive repositories through external execution environments.
Continuous Vulnerability and Dead Code Scanning in Automations
Automated code scanning represents another major platform capability introduced across the August and September 2026 releases. Instead of waiting for developer prompts, Devin can now run continuous repository audits as scheduled background automations or on every new commit.
Key scanning capabilities documented in the 2026 changelog include:
- The
/scanComposer Command: Developers can trigger repository audits on demand from the web composer by entering/scanfollowed by the target scope. - Cleanup Scans for Dead Code: Introduced in September 2026, cleanup scans detect unused functions, stale imports, orphan test fixtures, and deprecated API calls across the codebase.
- Scan Validation Severities: Security profiles allow administrators to specify which finding severities require validation before alerting developers, reducing false positives.
- Batch Remediation via v3 API: Enterprise teams can programmatically trigger scans across multiple repositories and dispatch batch remediation requests to resolve identified flaws automatically.
Sidebar Grouping and Multi-Select Metadata Filters
Managing dozens of concurrent agent sessions requires structured navigation. In late August and early September 2026, Cognition rolled out major improvements to session organization in the web console.
The session sidebar now supports multi-select metadata tag filters with real-time per-tag session counts, alongside machine-type filters. Sessions can also be grouped dynamically by pull request status or by target repository. In addition, the session workspace introduced VS Code-style split editor groups, allowing developers to inspect file diffs and review terminal execution side by side without toggling between tabs.
Devin CLI Changelog: Terminal Capabilities, Subagents, and MCP Enhancements
While web updates focus on enterprise governance and team dashboards, the Devin CLI changelog details the technical mechanics of local developer interaction. The command-line interface serves as the primary operational surface for engineers who integrate Devin into automated scripts, local shell sessions, and headless build runners. Recent stable releases from v3000.3.x through v3000.6.x illustrate rapid development across terminal control, subagent task distribution, and Model Context Protocol integrations.
Tracking these CLI changes ensures that developers take advantage of updated command syntax, improved signal handling, and responsive permission controls during active coding turns. Understanding the underlying configuration paths prevents local setup drift across team development environments.
Terminal Command Architecture and Session Governance
Recent stable releases of the Devin CLI have refined how developers interact with local execution loops. The v3000.5.20 release in late August 2026 introduced substantial operational commands:
- Session Management (
devin rm): Developers can delete old or abandoned sessions directly from the terminal. Deletion requires user confirmation by default and includes safety checks that refuse deletion if another active Devin process holds the session open. - Session Diagnostics (
devin doctor): A diagnostic tool that verifies local environment health, file path permissions, and subagent frontmatter definitions. - Context Summarization (
/recap): Generates an on-demand summary of recent turn decisions, terminal actions, and code modifications within the active session. - Session Renaming (
/rename): Assigns descriptive titles to ongoing tasks, making session histories easier to search and resume viadevin -rordevin ls. - Parallel Querying (
/btw): Opens a non-blocking side-chat panel that answers developer questions using session context while the primary agent continues working.
Process control has also been hardened. On Unix systems, cancelling or timing out a terminal command now sends a SIGTERM signal to the process group first, followed by a five-second grace period before dispatching SIGKILL. This prevents half-written database migrations and corrupted local state when developers interrupt long-running scripts.
Smart Permission Modes and Subagent Isolation
Permission models in early coding agents often forced a frustrating choice: either prompt the developer for every single command, or grant unrestricted shell execution.
The CLI changelog introduced the smart permission mode (v3000.3.22), which balances safety and developer velocity. Under smart mode, routine read actions, lint checks, and unit tests auto-approve, while high-risk actions always prompt for human confirmation. High-risk actions include package installations, destructive file operations (rm), system privilege escalation (sudo), git mutations, and access to sensitive files such as environment credentials or private keys.
Subagent management has also matured. When a primary Devin agent spawns subagents to inspect secondary modules, the terminal tray displays the active model for each child process. In v3000.5.20, killing an individual subagent by pressing x in the Subagents tab halts only that specific worker, preserving the parent session turn and state.
Model Context Protocol Configuration and Transport Updates
Cognition has steadily enhanced Devin's support for the Model Context Protocol (MCP). In release v3000.3.22, MCP server declarations were separated from the main user preferences file and moved into dedicated configuration paths:
~/.config/devin/mcp_config.json(or%APPDATA%\devin\mcp_config.jsonon Windows) for global user servers..devin/mcp_config.jsonfor repository-scoped servers..devin/mcp_config.local.jsonfor uncommitted, machine-specific overrides.
Subsequent updates refined network protocol stability. Release v3000.6.11 added connection timeouts to prevent stalled MCP servers from blocking the turn loop. Release v3000.6.12 resolved a transport regression connecting to MCP servers via Streamable HTTP, ensuring that remote HTTP endpoints function reliably alongside legacy stdio transports. MCP prompts also map directly to interactive slash commands using the format /mcp__<server>__<prompt>, allowing developers to invoke custom agent skills with positional arguments.
Capture and version Devin AI artifacts in shared workspaces
Give your team a central, persistent workspace where autonomous agents store build logs, code diffs, and generated assets alongside human collaborators. Every organization starts with a 14-day free trial.
Comparing Devin AI Release Channels and Enterprise Governance Models
As enterprises expand autonomous agent deployments from pilot projects to engineering-wide rollouts, governance becomes the critical factor determining success. The 2026 Devin release notes document key administrative controls designed to enforce security boundaries, manage identity, and maintain team audit trails across distributed developer teams.
Without centralized controls, individual developers might connect untested plugins or route internal source code to unvetted remote endpoints. Cognition has responded to these operational challenges by shipping enterprise-level MCP distribution, private network isolation, and granular permission scoping. Evaluating these administrative features helps infrastructure architects design secure agent environments.
By establishing clear organizational boundaries between personal developer experimentation and shared infrastructure pipelines, security teams can prevent data leakage while maintaining rapid development velocity across active coding sessions.
Enterprise MCP Server Distribution and Private Tunnels
Managing dozens of distinct developer machines creates configuration drift. Enterprise administrators can now configure approved MCP servers once at the enterprise root level within the web console. These servers automatically propagate to child organizations, while allowing individual teams to define local overrides where necessary.
For dedicated enterprise deployments, Devin supports private network MCP servers. In this architecture, OAuth authentication handshakes and tool-call payloads travel entirely through private network tunnels rather than crossing the public internet. Enterprise administrators can also upload custom private Certificate Authority (CA) bundles, allowing Devin workers to communicate securely with internal corporate services using private TLS certificates.
Short-Lived OIDC Authentication and Role-Based Permissions
Security policies often prohibit providing static, long-lived API tokens to autonomous agents. In mid-2026, Cognition introduced OpenID Connect (OIDC) identity tokens for Devin. Devin sessions can now generate short-lived cryptographic tokens to authenticate directly with major cloud providers (such as AWS, Google Cloud, and Azure). This allows Devin to deploy staging infrastructure or run remote integration tests without storing permanent credentials inside repo secrets.
Administrative permissions have also become more granular. The August 28, 2026 update split automation permissions so that organization administrators can manage personal automations independently from system user automations. This ensures that routine developer automation jobs do not interfere with production-critical security scan triggers.
Release Matrix Across Devin AI Environments
Understanding where changes land helps teams focus their monitoring efforts. The table below outlines how Devin release channels operate across different engineering environments:
Why Autonomous Agents Require Persistent Workspaces for Artifact Storage
When autonomous coding agents complete complex development tasks, they produce valuable intermediate and final deliverables: code patch files, test logs, architectural diagrams, dependency analysis reports, and security findings. In conventional setups, these files remain trapped inside ephemeral cloud Devboxes or scattered across individual developer workstations. If a cloud container terminates or a developer switches machines, the agent's work context is lost.
Traditional cloud drives like Google Drive or Dropbox were built for manual human sync and lack the programmatic access patterns required by autonomous AI agents. Simple object storage buckets like AWS S3 provide programmatic access, but they lack human-friendly collaboration views, built-in search intelligence, and structured document extraction.
Fast.io provides an intelligent workspace platform designed specifically for agentic teams. By pairing Devin with Fast.io, engineering organizations create a shared, persistent substrate where autonomous agents and human developers collaborate on the same files. Review the Fast.io Storage for Agents overview and Agent Onboarding Documentation for integration guidance.
Connecting Devin to Fast.io via Model Context Protocol
Fast.io exposes a consolidated MCP toolset accessible over Streamable HTTP at https://mcp.fast.io/mcp (or https://mcp.fast.io/mcp/key with Bearer authentication) as well as legacy SSE at https://mcp.fast.io/sse. Developers can configure Devin to connect directly to Fast.io by adding the server to their .devin/mcp_config.json:
{
"mcpServers": {
"fastio": {
"url": "https://mcp.fast.io/mcp/key",
"headers": {
"Authorization": "Bearer YOUR_FASTIO_API_KEY"
}
}
}
}
Once connected, Devin can read repository specifications, reference architectural diagrams, and write build artifacts directly into organization-owned workspaces. Files uploaded to Fast.io are never lost when a terminal turn ends or a cloud sandbox reboots.
Persistent Version History and Intelligence Mode
Fast.io provides per-file version history for every asset stored in a workspace. When Devin iteratively refactors a code module or updates an architectural draft, Fast.io automatically preserves previous versions. If an agent execution loop introduces a breaking regression, human developers can review the changes and restore earlier versions with complete audit transparency.
When Intelligence Mode is enabled on a workspace, Fast.io automatically indexes uploaded documents, code files, and specifications for hybrid search (combining full-text keyword matching and semantic search). Human engineers and autonomous agents can query the workspace context using natural language chat, receiving answers grounded in verified project documentation with source citations.
In addition, Fast.io features Metadata Views, turning workspace files into a live, queryable database. Teams can extract structured data such as ticket numbers, author metadata, and dependency licenses across hundreds of files without writing manual extraction scripts.
For client and external handoffs, Fast.io provides purpose-built branded shares (Send, Receive, and Exchange) that can be durable or expiring, featuring granular per-recipient access controls. Fast.io also supports ownership transfer, allowing an autonomous agent to initialize an organization and build workspaces before transferring administrative ownership to a human team lead.
Every organization starts with a 14-day free trial, which requires a credit card. | Plans are Starter at $29/mo, Business at $99/mo, and Growth at $299/mo on Fast.io pricing.
Frequently Asked Questions
Where can I find the Devin AI changelog?
You can find official Devin release notes on the Devin documentation website. Platform and enterprise updates are published at docs.devin.ai/release-notes/2026.md, while command-line interface updates are tracked at docs.devin.ai/cli/changelog/stable.md. Cognition also posts release announcements and product research on the official Devin blog at devin.ai/blog and through in-app notifications in the web console.
What are the latest features released for Devin AI?
Recent 2026 releases introduce Devin Outposts for self-hosted worker compute, automated code scanning with the /scan composer command and dead code cleanup, session sidebar grouping by pull request status and repository, multi-select metadata tag filters, and dedicated Model Context Protocol configuration files supporting Streamable HTTP transports.
How often does Cognition update Devin AI?
Cognition releases product updates on a bi-weekly cadence across web, desktop, and CLI channels. In addition to bi-weekly feature releases, urgent stability fixes, MCP transport improvements, and security patches are released as continuous point updates.
What is Devin Outposts and how does it work?
Devin Outposts is a hybrid deployment capability introduced in July 2026 that allows organizations to run code execution, testing, and compilation on their own self-hosted worker nodes. The centralized reasoning engine remains in Cognition's cloud, but sensitive repositories and execution commands stay within corporate network perimeters.
How does the Devin CLI configure Model Context Protocol servers?
The Devin CLI configures MCP servers using dedicated JSON configuration files located at ~/.config/devin/mcp_config.json on macOS and Linux or %APPDATA%\devin\mcp_config.json on Windows. Project-specific servers can be placed in .devin/mcp_config.json, supporting Streamable HTTP transports, custom CA bundles, and corporate proxy settings.
How can teams store and share files generated by Devin AI across sessions?
Teams can connect Devin to persistent Fast.io workspaces using the remote MCP endpoint detailed in the storage for agents guide at /storage-for-agents/. This allows Devin to write build artifacts, diff logs, and documentation into a shared workspace with automatic version history, semantic search indexing, and real-time collaboration.
Related Resources
Capture and version Devin AI artifacts in shared workspaces
Give your team a central, persistent workspace where autonomous agents store build logs, code diffs, and generated assets alongside human collaborators. Every organization starts with a 14-day free trial.