Field noteOct 28, 20265 min read1 source

Devin Desktop 3.11.228 fixes Remote-SSH/WSL Agent Window folders and Devin Local sessions failing with 'Failed to list sessions'

In one minute

Devin Desktop 3.11.228, released October 26, 2026, fixes failures that could block local sessions after an update and corrects remote-folder behavior in Remote-SSH and Remote-WSL Agent Windows. For teams running coding agents across local and remote environments, the release is a reminder that session continuity and correct workspace boundaries are operational dependencies, not interface details.

What changed: Devin Desktop 3.11.228 adds fixes for Remote-SSH/WSL folder selection and remote file links, plus restores Devin Local sessions failing to list—distinct from the 3.11.216 fixes.

What happened

Cognition released Devin Desktop v3.11.228 on October 26, 2026. The release is primarily a corrective update to the desktop application rather than a new agent capability. Its most consequential fix restores Devin Local sessions that had failed to load after an update with the message “Failed to list sessions.” The changelog says those sessions load again in 3.11.228.

The update also changes how the Agent Window behaves in remote development contexts. In Remote-SSH and Remote-WSL windows, the folder picker now sets a session’s working directory correctly. It lists folders from the remote window and no longer presents local folders. This matters because a coding-agent session needs an unambiguous working directory: presenting a local path while the editor is connected to a remote machine can create confusion about where an agent will inspect or change files.

File links inside the Agent Window are also corrected for Remote-SSH and Remote-WSL. Citations, diffs, settings, and plugins now open from the remote machine rather than the local one. The source does not describe the prior failure mode in detail, but the stated fix establishes that these links had not consistently followed the remote execution context.

Several smaller fixes address desktop continuity and interface behavior. The status bar no longer disappears after a user moves from Agent mode to IDE mode. On macOS, top-of-window banners no longer interfere with window controls. During sign-in, a dropped connection no longer signs the user out; Devin Desktop retries instead. The GitHub-account callout adds a “Don’t notify me again” option.

The release also simplifies Cloud availability in IDE mode. IDE mode now offers Devin Cloud whenever the account has Cloud access, matching the Agent Window. The separate “Devin for Cloud” team setting has been removed. The changelog provides downloads for macOS on Apple Silicon and Intel, Windows on arm64 and x64, and Linux x64, including Debian packages. It does not state changes to pricing, account tiers, model availability, or usage limits.

What the archive adds

This is a new maintenance event in an ongoing Devin Desktop release sequence. The immediately related Field Note, Devin Desktop 3.11.216 fixes Devin Local access, CLI install and sixel crash after 3.11.212 Agent Window rebuild, covered access, sign-in, CLI, and local-session stability fixes after the 3.11.212 Agent Window rebuild. Version 3.11.228 adds a distinct set of repairs around failed session listing and remote workspace routing.

Trend signal

The release modestly supports the assumption that scheduled, resumable, and subagent-based runs will occupy a growing share of coding-agent use, recorded in Delegated agent identity. A session that cannot reload after an update, or resolves files against the wrong machine, undermines continuity before any model-level capability matters. This is maintenance evidence rather than proof of a broad adoption shift.

Why it matters

Coding-agent workflows become fragile when their visible chat or editor interface is detached from the environment in which work actually happens. A remote project may have different files, credentials, dependencies, and repository state from the developer’s local machine. By making the folder picker and Agent Window links follow the Remote-SSH or Remote-WSL machine, Devin Desktop reduces an important source of ambiguity for teams that work across hosts.

The restored loading of Devin Local sessions is equally practical. Teams using persistent agent sessions need to be able to resume work after client updates; otherwise a desktop release can interrupt active tasks or make their history temporarily inaccessible. The update does not claim to improve agent quality or execution reliability, but it improves the conditions under which existing sessions and remote workspaces can be used predictably.

Limits and uncertainty

The changelog is a vendor release note and gives no incident scope, affected-user count, root cause, or independent validation. It does not establish how often “Failed to list sessions” occurred, whether any session data was at risk, or whether remote-path issues could have caused changes in an unintended location. It also does not describe migration steps, compatibility constraints, or whether users must manually update to receive the fixes. The source supports only that Cognition lists these fixes in version 3.11.228.

Skill to build now

Test the environment boundary of one agent workflow this week. Open a remote development workspace, start a small disposable task, and verify three things: the agent’s selected working directory is on the intended host, file and diff links open against that host, and a restarted client can still find the session. Record the expected host and workspace path in the team’s runbook so reviewers can distinguish a local task from a remote one before approving changes.

Reader takeaway

Devin Desktop 3.11.228 is not a capability launch; it is a reliability release for users of Devin Local and Remote-SSH or Remote-WSL workflows. Its practical value is restoring session access and ensuring that Agent Window paths and links point to the remote workspace where the work is meant to occur.

Evidence / sources

  1. 1windsurf.com/changelog
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicAgent LoopsExplore the agent-loops topic hub.
  2. 02topicAutomationExplore the automation topic hub.
  3. 03archiveField NotesOpen the latest editorial analysis.
  4. 04source ledgerSource LedgerInspect the public source evidence graph.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract