Agent Architecture

Warp

Warp is a terminal, local-agent, third-party-agent, and cloud-agent orchestration host. Its architecture includes MCP servers, skills, slash commands, rules, terminal use, codebase context, profiles, remote control, cloud agents, and multi-agent orchestration.

Source reviewed #8Checked 2026-07-06

Setup guide Source

Run type

Desktop

Adapter

mcp-only

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

warp

Run cohort

Desktop: 9

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 Warp.

1 surface entry

Desktop

desktop

Host entry: A desktop app or standalone editor owns window state, sign-in, project indexing, embedded terminal behavior, and local product storage.
Host owns: The desktop host owns orchestration UI, model routing, approval UX, background jobs, and any cloud or app-store managed extension points.
Connector role: agent-connector can write documented workspace/global config and content files, but it does not replace the desktop runtime or UI shell. Current wired connector surfaces: MCP server, Skills, Memory, Action affordances.
Implementation consequence: Desktop surfaces need source-review separation because product pages often document capabilities while runtime state lives in app-managed storage. Visible host-native gaps for this surface: Commands.

Verified Architecture

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

Sequence #8

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.

Warp describes itself as an agentic development environment born out of the terminal, so the row is a terminal-centered host with a product shell.
The repository explicitly supports built-in coding agents and bring-your-own CLI agents such as Claude Code, Codex, and Gemini CLI.
Warp's Oz workflows and web-compiled terminal sessions are host-only orchestration affordances, not simple MCP or hook surfaces.

Runtime boundary

The adapter target is the Warp desktop terminal host, not a conventional CLI binary. Warp owns terminal blocks, local agents, third-party CLI agent hosting, remote control, cloud agents, permissions, and app-level settings.

Warp separates Terminal and Agent modes and can host third-party CLI agents such as Claude Code, Codex, and OpenCode.
The cloud-agent layer includes Oz platform concepts, triggers, integrations, and handoff.
The connector row should remain desktop/terminal host scoped rather than claiming downstream agent internals.

MCP registration

Warp's MCP docs are explicit and unusually rich. Warp supports command-based servers, streamable HTTP or SSE servers, custom headers, environment variables, shared servers, OAuth, logs, and file-based project or global config.

Warp global config lives at `~/.warp/.mcp.json` and project config at `.warp/.mcp.json`.
Warp can also read Claude Code, Codex, and other-agent MCP files when third-party auto-spawn is enabled.
Project-scoped servers require explicit approval, which is a host security boundary.

Hook bridge

Warp is currently represented as MCP-only in agent-connector. Its local agents have many controls, but the connector should not describe PreToolUse or PostToolUse hooks unless Warp exposes a file or plugin lifecycle bridge for that purpose.

Rules, profiles, permissions, and prompt queueing are host UX controls.
Third-party hosted agents may have their own hook systems, but those hooks belong to the downstream agent runtime.

Content surfaces

Warp content surfaces include slash commands, skills, task lists, rules, codebase context, profiles, permissions, full terminal use, computer use, and cloud-synced conversations. These belong to the Warp app and cloud platform.

The built-in `/agent-add-mcp` skill can create or update file-based MCP definitions.
Session sharing and cloud-synced conversations are host memory/collaboration features.
Rules and skills should be displayed separately from MCP server registration.

Marketplace and host-only affordances

Warp's host-only affordances include shared MCP servers, cloud agents, Slack and Linear integrations, GitHub Actions, cloud handoff, hosted agents, self-hosted workers, and third-party CLI agent embedding inside the terminal app.

Warp is a layered host: it can run its own agents and host other agents.
The study page should distinguish local Warp Agent MCP from cloud-agent MCP workflows.

Host-specific shape

Warp is a desktop terminal-agent host with MCP, skills-as-slash-style prompts, memory, and generated actions; lifecycle hooks and true subagents are not confirmed native surfaces.

Form factor: Desktop.
Native surfaces: MCP server, Commands, Skills, Memory, Action affordances.
Wired surfaces: MCP server, Skills, Memory, Action affordances.
Visible gaps: Commands.

Hooks

No user-installable lifecycle hook boundary is confirmed for this host.

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: Action affordances.
User-visible affordances: Users see managed skills + actions + memory surfaces after install; runtime-only surfaces stay behind the host boundary..

Known Limits

MCP support should not be treated as a lifecycle hook bridge.
Downstream Claude Code, Codex, or OpenCode features should not be promoted into Warp coverage without layer-specific evidence.
Cloud-agent features may require Warp account state and should not be represented as local file writes.

Evidence checked

Warp MCP documentation Warp agents documentation Warp website warpdotdev/warp repository

Architecture Diagram

Host-specific flow for the Desktop surface.

mcp-only

1
Entry point: Desktop
Desktop or standalone editor app reads global/product storage plus workspace files before handing control to its embedded agent runtime.
2
Connector package
defineConnector package declares server, hooks, content, memory, and actions.
3
Adapter module: warp
mcp-only renderer at src/adapters/warp/index.ts.
4
Native host artifacts
Adapter writes MCP config + content files + memory/rules + actions through this host's native file, package, or marketplace surface.
5
Runtime boundary
host calls MCP tools through its client
6
User-visible surface
Users see managed skills + actions + memory surfaces after install; runtime-only surfaces stay behind the host boundary.
7
Coverage ceiling
4/5 native surfaces wired. Commands are host-native but not wired yet.

Component Diagram

Static parts of the Warp integration and which side owns each one.

Warp host
Desktop 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.
warp adapter
Implements the mcp-only translation layer in src/adapters/warp/index.ts.
Native artifacts
Adapter writes MCP config + content files + memory/rules + actions through this host's native file, package, or marketplace surface.
Runtime bridge
host calls MCP tools through its client
User-visible surface
Users see managed skills + actions + memory surfaces after install; runtime-only surfaces stay behind the host boundary.

Runtime Sequence Flow

Message order from install to runtime for the Desktop surface.

1 · User / project
Choose host adapter
Install or update starts against Warp; the selected surface is Desktop.
2 · agent-connector
Resolve connector declaration
The package reads connector metadata and routes it to the warp adapter instead of exposing a generic host contract.
3 · warp adapter
Render host-native shape
Adapter writes MCP config + content files + memory/rules + actions through this host's native file, package, or marketplace surface.
4 · Warp
Host loads artifacts
host calls MCP tools through its client
5 · Agent runtime
Run through host boundary
Users see managed skills + actions + memory surfaces after install; runtime-only surfaces stay behind the host boundary.
6 · Coverage matrix
Expose remaining ceiling
4/5 native surfaces wired. Commands 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

Warp is a desktop terminal-agent host with MCP, skills-as-slash-style prompts, memory, and generated actions; lifecycle hooks and true subagents are not confirmed native surfaces.

Form factor: Desktop.
Native surfaces: MCP server, Commands, Skills, Memory, Action affordances.
Wired surfaces: MCP server, Skills, Memory, Action affordances.
Visible gaps: Commands.

Hooks

No user-installable lifecycle hook boundary is confirmed for this host.

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: Action affordances.
User-visible affordances: Users see managed skills + actions + 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

Not confirmed

No user-installable lifecycle hook boundary is confirmed for this host.

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

2/3 wired

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

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

warpdotdev/warp repository

Warp describes itself as an agentic development environment born out of the terminal, so the row is a terminal-centered host with a product shell.
The repository explicitly supports built-in coding agents and bring-your-own CLI agents such as Claude Code, Codex, and Gemini CLI.
Warp's Oz workflows and web-compiled terminal sessions are host-only orchestration affordances, not simple MCP or hook surfaces.

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/warp/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

The host accepts MCP registration, but has no confirmed hook bridge for agent-connector to call.

MCP registration: Wired through this adapter
Hook bridge: No confirmed hook surface

Connector Surfaces

Static content

MCP server, Skills, Memory

Runtime handlers

Action affordances

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

No confirmed host-native surface.

N/A

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

No confirmed host-native surface.

N/A

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

agent-connector installs this surface today.

Wired