Skip to content

Devin (Cognition) ​

Produced by the ACP product case-study pass (2026-07-30), then adversarially verified; corrections below override the body where they conflict.

Devin (Cognition) as an ACP peer for trogonai ​

Devin is Cognition's cloud-hosted autonomous coding agent, historically exposed only through a session-based REST API (POST /v3/organizations/{org_id}/sessions), a web app, Slack, and an internal MCP server. As of mid-2026 this changed: Cognition rebranded its acquired Windsurf editor as Devin Desktop and shipped native support for the Agent Client Protocol (ACP), the Zed Industries-authored, Apache-licensed, JSON-RPC-2.0-over-stdio standard for editor-agent communication (https://zed.dev/acp). This gives Devin a genuine dual role.

As an ACP client/host: Devin Desktop runs third-party ACP agents (Codex, Claude Agent, OpenCode, and in-house agents) side by side with its own Devin and Devin Local agents inside a shared Kanban/Spaces UI (https://devin.ai/blog/windsurf-is-now-devin-desktop). This is Devin absorbing ACP the way Zed itself does: as the "editor" half of the protocol.

As an ACP agent: the official Devin CLI ships an devin acp [--agent-type <TYPE>] [--model <MODEL>] subcommand that runs Devin "as an ACP server over stdio for editor integration," documented explicitly for Zed (zed: acp registry then search "Devin") and implicitly for Windsurf/Devin Desktop (https://docs.devin.ai/cli/acp/zed, https://docs.devin.ai/cli/reference/commands). This is the mechanism directly relevant to trogonai: it is a local subprocess speaking the same wire protocol trogonai's acp-nats-stdio crate already expects.

Authentication for devin acp reads a WINDSURF_API_KEY env var (a naming artifact of the Windsurf acquisition) or a stored browser-login credential file; the CLI's general auth surface is devin auth login/logout/status. MCP passthrough is native and rich: devin mcp add/list/login/logout/enable/disable, supporting stdio and http transports, env var and header injection, OAuth scopes, and RFC 8707 resource overrides. Headless/non-interactive operation is supported through -p/--print combined with --permission-mode dangerous or autonomous, which auto-approves tool calls instead of blocking on permission prompts; CI use requires --respect-workspace-trust false since print mode cannot render trust prompts.

The catch for trogonai: devin acp is not a self-contained local agent, it is a thin ACP-shaped bridge onto Cognition's cloud session backend. Spawning it as a subprocess gets you JSON-RPC-over-stdio framing, but every prompt still round-trips to Devin's VM-backed cloud session, consuming ACUs and requiring live Cognition Cloud credentials. Devin Desktop's own docs note its Zed-hosted terminal rendering is a reduced view compared to the native CLI's terminal UI, hinting the ACP fs/terminal RPC surface may not be feature-complete relative to the SDK's capability negotiation. No public source states the exact ACP protocol version devin acp targets, so compatibility with trogonai's pinned agent-client-protocol=2.0.0 (wire protocol v1) needs direct testing, not assumption.

Design lessons for trogonai: (1) Devin proves a cloud-session product can retrofit ACP as a thin process-shaped facade over a remote API, exactly the "remote agent behind a local stdio mask" pattern trogonai's acp-nats bridge already generalizes over NATS, validating that architecture. (2) Devin's --permission-mode ladder (normal, accept-edits, smart, dangerous, autonomous) is a clean, copyable vocabulary for trogonai's own ACP permission-RPC policy layer; see permission decision point. (3) Avoid Devin's inconsistency of exposing a richer native UI/CLI experience alongside a strictly worse ACP-mediated experience, trogonai should treat ACP as the primary contract, not a degraded secondary channel. (4) Devin's channel story (Slack @mention, schedules, GitHub/Linear/Jira triggers) sits entirely outside ACP, on its own session-creation API, confirming ACP is scoped to editor/IDE-shaped clients only, and trogonai should not expect ACP to carry chat-channel traffic; see channel mapping.

Sources ​

Adversarial verification ​

  • confirmed: 1. ACP status 'native': devin acp CLI subcommand is agent-side native stdio JSON-RPC; Devin Desktop (renamed from Windsurf) acts as ACP client/host running Devin plus third-party ACP agents side by side (devin.ai/blog/windsurf-is-now-devin-desktop states Devin Desktop launches with ACP support letting any compatible agent run inside it, listing Codex, Claude Agent, OpenCode, and in-house agents as launch agents alongside Devin; docs.devin.ai/cli/reference/commands documents 'devin acp' as running Devin as an ACP server over stdio for an ACP-aware editor to invoke as a subprocess, matching the native agent-side description (exact June 2026 rebrand month not present in fetched text but not contradicted).)
  • refuted: 2. Callability verdict 'partial': trogonai's acp-nats-stdio crate already knows how to spawn a local stdio ACP agent subprocess and bridge it onto NATS, so it could in principle spawn devin acp under acp-nats-stdio today (Read acp-nats-stdio's src/main.rs in the trogonai repo (origin/main): it wires the process's own stdin/stdout directly into the bridge (async_compat::Compat::new(tokio::io::stdin()/stdout())); grepped all of the acp crates for Command::new, tokio::process, std::process::Command and found zero matches; ADR 0020 (docs/adr/0020-acp-sdk-1x-boundary-and-bridge-traits.md) explicitly states trogonai's AgentHandler/ClientHandler traits were named to avoid colliding with 'the 1.x SDK's own AcpAgent subprocess helper', implying that helper is not what trogonai uses. acp-nats-stdio is itself an ACP stdio peer bridged onto NATS, not a subprocess-spawning host, so the premise behind the 'partial' verdict is factually inverted for the current codebase.)
  • confirmed: 3a. Devin Desktop (renamed Windsurf) supports ACP allowing any ACP-compatible agent to run inside it alongside built-in agents (devin.ai/blog/windsurf-is-now-devin-desktop) (Fetched page text: 'Devin Desktop launches today with support for the Agent Client Protocol (ACP), an open-source protocol that lets any compatible agent run inside any ACP-compatible editor.')
  • confirmed: 3b. At launch Devin Desktop supports Devin (native), Codex, Claude Agent, OpenCode, and custom in-house agents as ACP agents in Kanban/Spaces view (devin.ai/blog/windsurf-is-now-devin-desktop) (Fetched page text: 'At launch, Devin Desktop supports Codex, Claude Agent, OpenCode, and any other ACP-compatible agents - including agents built by your team in-house,' with third-party agents appearing in the Kanban view and Spaces alongside Devin.)
  • confirmed: 3c. Devin CLI can run as an ACP agent inside Zed via 'zed: acp registry' command from the Zed ACP registry (docs.devin.ai/cli/acp/zed) (Fetched page text: 'Open the ACP registry with zed: acp registry from the command palette... Search for Devin and install it.')
  • confirmed: 3d. devin acp [--agent-type <TYPE>] [--model <MODEL>] runs Devin as ACP server over stdio; reads WINDSURF_API_KEY or stored login; advertises slash commands /ask, /plan, /workspace, /mcp, /model, /mode (docs.devin.ai/cli/reference/commands) (Fetched page confirms the stdio ACP server description, --agent-type/--model flags, and WINDSURF_API_KEY/devin auth login credential fallback; a follow-up web search of the same doc plus a Devin CLI usage summary confirmed /mode, /model, /workspace among in-session slash commands, corroborating the full list including /mode which the first fetch pass had not explicitly echoed.)
  • confirmed: 3e. Devin CLI terminal/shell output under Zed's ACP rendering differs from native Devin CLI terminal UI; some richer interactions only available in standalone CLI (docs.devin.ai/cli/acp/zed) (Fetched page's Notes and limitations section states verbatim: 'Devin CLI's terminal/shell output is surfaced through Zed's ACP rendering, which differs from the native Devin CLI terminal UI,' and 'Some richer interactions are only available in the standalone CLI.')

Corrections (authoritative where they conflict with the body) ​

Claim 2 should read: trogonai's acp-nats-stdio crate is itself an ACP stdio peer that bridges its own process stdin/stdout onto NATS (via acp_nats::agent::Bridge and connect_agent_boundary); it does not spawn subprocesses. There is no Command::new or tokio::process usage anywhere under the acp crates in the current trogonai codebase (checked against the repo on branch main, remote TrogonStack/trogonai). ADR 0020 explicitly distinguishes trogonai's own AgentHandler/ClientHandler bridge traits from "the 1.x SDK's own AcpAgent subprocess helper," which trogonai's traits were named to avoid colliding with, not to wrap. Therefore trogonai cannot today spawn devin acp (or any other local ACP agent CLI) as a subprocess without first building a host-side process-spawning component; the version pin fact (agent-client-protocol = "=2.0.0" in the workspace Cargo.toml) is accurate, but the callability verdict should be "not yet possible without new code" rather than "partial: could spawn today."

Released under the Apache License 2.0.