Agent Architecture

Droid (Factory)

Factory Droid is a broad agent-native development platform whose public architecture spans CLI, web, Slack, Teams, Linear, Jira, mobile, IDE extension, ACP, SDK, GitHub Action, and plugin marketplace surfaces. The connector row stays CLI-scoped while preserving that multi-channel product shape.

Source reviewed #12Checked 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

droid

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 Droid (Factory).

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, Commands, Skills, Subagents, Memory, Action affordances.
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. No visible host-native gap is currently tracked for this surface.

Verified Architecture

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

Sequence #12

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.

Factory presents Droid as part of an agent-native development platform across CLI, web, Slack/Teams, Linear/Jira, and mobile.
The repository installation path is a `droid` CLI, while the same ecosystem also advertises a VS Code extension and ACP support for JetBrains and Zed.
Factory exposes SDKs, a GitHub Action, and a plugins marketplace, so Droid's page needs host-only ecosystem notes beyond basic CLI configuration.

Runtime boundary

The adapter target is the local Droid CLI. Factory owns the hosted service, channels, model orchestration, and IDE/ACP clients; agent-connector installs only into the byte-addressable host surfaces that the CLI can read from local configuration and workspace files.

The public repository presents Factory as an agent-native development platform, not only a terminal wrapper.
Droid can be reached through CLI, web, Slack, Teams, Linear, Jira, mobile, IDE, and ACP surfaces.
The archive keeps Droid in the CLI band because the current adapter writes the local CLI contract.

MCP registration

Droid belongs in the MCP-capable CLI set, but Factory also exposes SDK and ACP integration paths. The page therefore treats MCP as one tool extension rail and keeps IDE/ACP connection setup separate from local MCP server registration.

MCP should remain a tool-server install target, not a proxy label for every Factory integration.
ACP support for JetBrains and Zed is an adjacent client protocol and should not be folded into the CLI file contract.

Hook bridge

agent-connector models Droid as a json-stdio hook host. Hook claims should stay tied to the local adapter bridge because Factory's public product surface is channel-heavy and does not make every channel a lifecycle interception point.

The host owns channel routing and cloud-side execution decisions.
The connector hook bridge should describe request and response normalization without implying control over Slack, Teams, Linear, Jira, or mobile clients.

Content surfaces

Factory advertises plugins, an IDE extension, SDKs, GitHub automation, and agent workflows. agent-connector should represent commands, skills, memory, and subagent-like content only where the local Droid CLI or workspace contract can discover them.

Plugin marketplace content is a distribution surface and should be modeled separately from local generated command files.
GitHub Action and ESLint plugin support are workflow integrations, not the local CLI runtime boundary.

Marketplace and host-only affordances

Factory's host-only affordances include a plugin marketplace, SDKs, ACP clients, mobile access, issue-tracker channels, and repository automation. Those features should be visible on the study page without being counted as implemented connector surfaces unless an adapter writes or invokes them.

The marketplace axis matters because plugin developers need to know whether distribution is host-native or connector-generated.
Channel support should appear as host orchestration context, not as MCP or hook support by default.

Host-specific shape

Factory Droid exposes the full CLI surface set: MCP, hooks, commands, skills, droids-as-subagents, memory, and action affordances.

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

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

A marketplace or plugin-driver path is wired, so install/update/uninstall can be driven rather than only emitted as files.

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

Known Limits

This page documents the Droid CLI adapter row, not every Factory hosted or mobile surface.
ACP and SDK claims need separate adapter work before they become connector install targets.
Channel integrations should stay host-only unless agent-connector has a concrete write or runtime contract.

Evidence checked

Factory repository Factory documentation Factory website

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: droid
json-stdio renderer at src/adapters/droid/index.ts.
4
Native host artifacts
Adapter writes MCP config + hook config + content files + memory/rules + actions + marketplace bundle 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 commands + skills + subagents + actions + memory surfaces after install; runtime-only surfaces stay behind the host boundary.
7
Coverage ceiling
7/7 native surfaces wired. No visible host-native gap in the current coverage matrix.

Component Diagram

Static parts of the Droid (Factory) integration and which side owns each one.

Droid (Factory) 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.
droid adapter
Implements the json-stdio translation layer in src/adapters/droid/index.ts.
Native artifacts
Adapter writes MCP config + hook config + content files + memory/rules + actions + marketplace bundle through this host's native file, package, or marketplace surface.
Runtime bridge
host launches JSON-stdio hook command
User-visible surface
Users see managed commands + skills + subagents + actions + 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 Droid (Factory); the selected surface is CLI.
2 · agent-connector
Resolve connector declaration
The package reads connector metadata and routes it to the droid adapter instead of exposing a generic host contract.
3 · droid adapter
Render host-native shape
Adapter writes MCP config + hook config + content files + memory/rules + actions + marketplace bundle through this host's native file, package, or marketplace surface.
4 · Droid (Factory)
Host loads artifacts
host launches JSON-stdio hook command
5 · Agent runtime
Run through host boundary
Users see managed commands + skills + subagents + actions + memory surfaces after install; runtime-only surfaces stay behind the host boundary.
6 · Coverage matrix
Expose remaining ceiling
7/7 native surfaces wired. No visible host-native gap in the current coverage matrix.

Architecture Archive

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

Host-specific shape

Factory Droid exposes the full CLI surface set: MCP, hooks, commands, skills, droids-as-subagents, memory, and action affordances.

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

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

A marketplace or plugin-driver path is wired, so install/update/uninstall can be driven rather than only emitted as files.

Runtime handlers: Action affordances.
User-visible affordances: Users see managed commands + skills + subagents + 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

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

Driver wired

A marketplace or plugin-driver path is wired, so install/update/uninstall can be driven rather than only emitted as files.

Host-only affordances

4/4 wired

Wired host affordances: Commands, Skills, Subagents, Action affordances. Host-native gaps: none. Not confirmed: 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

Factory-AI/factory repository

Factory presents Droid as part of an agent-native development platform across CLI, web, Slack/Teams, Linear/Jira, and mobile.
The repository installation path is a `droid` CLI, while the same ecosystem also advertises a VS Code extension and ACP support for JetBrains and Zed.
Factory exposes SDKs, a GitHub Action, and a plugins marketplace, so Droid's page needs host-only ecosystem notes beyond basic CLI configuration.

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

Marketplace driver registry

Shows this host has a drivable package/plugin install path beyond direct native-file writes.

local

src/core/marketplace-drivers/registry.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, Commands, Skills, Subagents, 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

agent-connector installs this surface today.

Wired

Commands

Static content

agent-connector installs this surface today.

Wired

Skills

Static content

agent-connector installs this surface today.

Wired

Subagents

Static content

agent-connector installs this surface today.

Wired

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