Agent Architecture

Devin CLI (Cognition)

Devin is a cloud, CLI, and desktop software-engineering agent platform. Its architecture includes long-running planning/execution, PR review, visual QA, docs, migrations, issue triage, knowledge, skills, automations, MCP Marketplace, shell, browser, and IDE surfaces.

Source reviewed #39Checked 2026-07-06

Setup guide Source

Run type

CLI

Adapter

json-stdio

Source

Closed / product homepage

Stars

Frontier

Archive Context

This page is one host entry inside the full architecture archive and keeps multi-surface products visible instead of collapsing them into a single run type.

42 host archive

Host page

devin

Run cohort

CLI: 30

Archive route

/agents

Host Surface Perspectives

The host is the primary architecture boundary. Each runnable surface below separates what the host owns from what agent-connector can safely install for Devin CLI (Cognition).

1 surface entry

CLI

cli

Host entry: A terminal command owns the process, current working directory, stdin/stdout, shell environment, and project file discovery.
Host owns: The CLI host owns agent loop timing, approval prompts, tool execution, session files, and how hook or MCP subprocesses are launched.
Connector role: agent-connector can only write the host's documented CLI config, prompt, memory, hook, MCP, or package files and point them at the home binary. Current wired connector surfaces: MCP server, Hooks, Skills, Memory.
Implementation consequence: A CLI surface is byte-addressable and smoke-testable from a temporary HOME, but terminal UI behavior still belongs to the host process. Visible host-native gaps for this surface: Commands, Subagents.

Verified Architecture

Source-checked on 2026-07-06. These notes are intentionally separate from the generated surface matrix below.

Sequence #39

Source pass

Current source review findings are kept as the first architecture section so readers can separate external evidence from the generated local coverage model.

Devin is documented as an autonomous AI software engineer that can write, run, and test code across engineering tasks and team workflows.
The docs include Devin CLI, MCP Marketplace, knowledge, skills, automations, playbooks, computer use, and handoff to cloud Devins as first-party surfaces.
This row should highlight cloud/team orchestration and CLI handoff behavior, not just local json-stdio installation mechanics.

Runtime boundary

Devin should be modeled as a platform host, not a simple CLI. The cloud service, CLI handoff, desktop IDE, embedded shell, browser, and workspace state are all part of the product architecture, while the connector row must name the concrete surface it installs into.

Devin can plan and execute complex engineering tasks, review PRs, run visual QA, update docs, migrate code, and triage issues.
The docs describe Cloud, CLI, and Desktop surfaces.
CLI handoff can move local context to cloud execution, creating a cross-surface boundary.

MCP registration

Devin exposes an MCP Marketplace, so MCP is not just a local JSON setting. agent-connector should represent MCP as a platform marketplace and tool-extension surface, with separate treatment for local CLI, desktop, and cloud session attachment.

Marketplace MCP servers may be installed through Devin platform UX rather than local file writes.
Cloud sessions can have different authority and network reach than a local terminal adapter.

Hook bridge

agent-connector classifies Devin as a json-stdio host in the current matrix, but the product architecture is broader. Hook documentation should distinguish local CLI bridge behavior from cloud automations, scheduled work, and PR review triggers.

Automations and scheduled chores are host workflow triggers.
The CLI can hand off to cloud, so a hook event observed locally may not cover the whole task lifecycle after handoff.

Content surfaces

Devin's docs call out Knowledge, Skills, Automations, MCP Marketplace, shell, browser, and IDE state. These surfaces make it a major reference for plugin developers because content may be persistent platform knowledge rather than only repository files.

Skills and Knowledge should be treated as platform memory/content surfaces.
Embedded browser and shell are host execution affordances that affect test and QA workflows.

Marketplace and host-only affordances

Devin's host-only affordances include multi-week multi-repo execution, learning from past sessions, Slack/Linear/GitHub integrations, MCP Marketplace, cloud compute, local CLI, and desktop command-center UX. The archive should show these as platform capabilities beside connector coverage chips.

Long-running autonomy and session memory are host-owned behaviors.
PR review, visual QA, migrations, and issue triage are workflow products, not a generic hook API.

Host-specific shape

Devin CLI wires MCP, hooks, skills, and rules in first-party config paths; native commands and subagents are documented but remain path-unconfirmed adapter gaps.

Form factor: CLI.
Native surfaces: MCP server, Hooks, Commands, Skills, Subagents, Memory.
Wired surfaces: MCP server, Hooks, Skills, Memory.
Visible gaps: Commands, Subagents.

Hooks

Hooks enter through a host-launched command that exchanges event JSON over stdio.

MCP

The adapter writes this host's native MCP registration dialect, including its root key, scope, transport fields, and environment syntax.

Memory

Managed memory text is written into the rules or memory file this host actually reads, with ownership markers for reversible uninstall.

Marketplace and affordances

Current install is a direct native-file write path; any package artifact is manual unless a driver is added.

Runtime handlers: none.
User-visible affordances: Users see managed skills + memory surfaces after install; runtime-only surfaces stay behind the host boundary..

Known Limits

Keep Cloud, CLI, and Desktop surfaces separate when claiming connector support.
Do not count platform automations as local lifecycle hooks without adapter evidence.
Marketplace and knowledge features may require authenticated platform state that agent-connector cannot write directly.

Evidence checked

Devin website Devin introduction docs Devin CLI docs Devin Desktop Devin official site and docs

Architecture Diagram

Host-specific flow for the CLI surface.

json-stdio

1
Entry point: CLI
Terminal agent process reads user/project config and invokes the connector home binary for runtime callbacks.
2
Connector package
defineConnector package declares server, hooks, content, memory, and actions.
3
Adapter module: devin
json-stdio renderer at src/adapters/devin/index.ts.
4
Native host artifacts
Adapter writes MCP config + hook config + content files + memory/rules through this host's native file, package, or marketplace surface.
5
Runtime boundary
host launches JSON-stdio hook command
6
User-visible surface
Users see managed skills + memory surfaces after install; runtime-only surfaces stay behind the host boundary.
7
Coverage ceiling
4/6 native surfaces wired. Commands, Subagents are host-native but not wired yet.

Component Diagram

Static parts of the Devin CLI (Cognition) integration and which side owns each one.

Devin CLI (Cognition) host
CLI surface owns the model loop, UI shell, config discovery, and native lifecycle for this integration.
agent-connector package
Normalizes connector declarations into MCP, hook, memory, content, and action payloads before delegating to a host adapter.
devin adapter
Implements the json-stdio translation layer in src/adapters/devin/index.ts.
Native artifacts
Adapter writes MCP config + hook config + content files + memory/rules through this host's native file, package, or marketplace surface.
Runtime bridge
host launches JSON-stdio hook command
User-visible surface
Users see managed skills + memory surfaces after install; runtime-only surfaces stay behind the host boundary.

Runtime Sequence Flow

Message order from install to runtime for the CLI surface.

1 · User / project
Choose host adapter
Install or update starts against Devin CLI (Cognition); the selected surface is CLI.
2 · agent-connector
Resolve connector declaration
The package reads connector metadata and routes it to the devin adapter instead of exposing a generic host contract.
3 · devin adapter
Render host-native shape
Adapter writes MCP config + hook config + content files + memory/rules through this host's native file, package, or marketplace surface.
4 · Devin CLI (Cognition)
Host loads artifacts
host launches JSON-stdio hook command
5 · Agent runtime
Run through host boundary
Users see managed skills + memory surfaces after install; runtime-only surfaces stay behind the host boundary.
6 · Coverage matrix
Expose remaining ceiling
4/6 native surfaces wired. Commands, Subagents are host-native but not wired yet.

Architecture Archive

The same five study axes are rendered for every host: runtime shape, hooks, MCP, memory, and host-only affordances.

Host-specific shape

Devin CLI wires MCP, hooks, skills, and rules in first-party config paths; native commands and subagents are documented but remain path-unconfirmed adapter gaps.

Form factor: CLI.
Native surfaces: MCP server, Hooks, Commands, Skills, Subagents, Memory.
Wired surfaces: MCP server, Hooks, Skills, Memory.
Visible gaps: Commands, Subagents.

Hooks

Hooks enter through a host-launched command that exchanges event JSON over stdio.

MCP

The adapter writes this host's native MCP registration dialect, including its root key, scope, transport fields, and environment syntax.

Memory

Managed memory text is written into the rules or memory file this host actually reads, with ownership markers for reversible uninstall.

Marketplace and affordances

Current install is a direct native-file write path; any package artifact is manual unless a driver is added.

Runtime handlers: none.
User-visible affordances: Users see managed skills + memory surfaces after install; runtime-only surfaces stay behind the host boundary..

Special Feature Inventory

Host-specific capabilities separated from the generic surface matrix: lifecycle hooks, MCP registration, memory/rules, marketplace delivery, and UI or content affordances owned by the host.

Lifecycle hooks

Wired

Hooks enter through a host-launched command that exchanges event JSON over stdio.

MCP registration

Wired

The adapter writes this host's native MCP registration dialect, including its root key, scope, transport fields, and environment syntax.

Memory and rules

Wired

Managed memory text is written into the rules or memory file this host actually reads, with ownership markers for reversible uninstall.

Marketplace delivery

Direct files

Current install is a direct native-file write path; any package artifact is manual unless a driver is added.

Host-only affordances

1/3 wired

Wired host affordances: Skills. Host-native gaps: Commands, Subagents. Not confirmed: Statusline handler, Action affordances.

Source Review Notes

Latest source pass for host-specific architecture details. This is separate from generated adapter coverage and local drift guards.

Checked 2026-07-06Open review source

Devin official site and docs

Devin is documented as an autonomous AI software engineer that can write, run, and test code across engineering tasks and team workflows.
The docs include Devin CLI, MCP Marketplace, knowledge, skills, automations, playbooks, computer use, and handoff to cloud Devins as first-party surfaces.
This row should highlight cloud/team orchestration and CLI handoff behavior, not just local json-stdio installation mechanics.

Evidence Map

Each host page ties public source evidence to the local adapter and drift guards that keep the rendered archive aligned with code.

Product source

Official product homepage or public tracker used when no open product repository is confirmed.

external

Open source

Local adapter implementation

Defines the install/uninstall behavior, native config rendering, capability flags, and any runtime parse/format bridge for this host.

local

src/adapters/devin/index.ts

Platform metadata and host-native matrix

Records the form factor, public source target, ranking source, native host surfaces, and current agent-connector coverage cells.

local

site/src/platform-data.ts

Architecture drift guard

Asserts that every registered host has a page, diagram, host-specific brief, source link, form-factor band, and adapter-aligned surface data.

local

tests/docs/platform-drift.test.ts

Runtime Shape

Hooks are dispatched through a host-launched command. The adapter parses host JSON, calls the connector handler, and formats the reply back to the host contract.

MCP registration: Wired through this adapter
Hook bridge: Wired

Connector Surfaces

Static content

MCP server, Hooks, Skills, Memory

Runtime handlers

No runtime handler surfaces wired

Surface Matrix

Wired means agent-connector installs it now. Host native marks support we know about but have not wired yet.

SurfaceStatus

MCP server

Static content

agent-connector installs this surface today.

Wired

Hooks

Static content

agent-connector installs this surface today.

Wired

Commands

Static content

The host appears to offer this, but this adapter has not wired it yet.

Host native

Skills

Static content

agent-connector installs this surface today.

Wired

Subagents

Static content

The host appears to offer this, but this adapter has not wired it yet.

Host native

Memory

Static content

agent-connector installs this surface today.

Wired

Statusline handler

Runtime handler

No confirmed host-native surface.

N/A

Action affordances

Runtime handler

No confirmed host-native surface.

N/A