Agent Architecture

Goose

goose is now under the Agentic AI Foundation and presents itself as a native open-source AI agent with desktop app, CLI, API, provider support, ACP, MCP extensions, and custom distributions across code and non-code workflows.

Source reviewed #29Checked 2026-07-06

Setup guide Source

Run type

CLI

Adapter

json-stdio

Source

OSS · aaif-goose/goose

Stars

★ 54k

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

goose

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

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. 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 #29

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.

Goose has moved under the Agentic AI Foundation and is documented as a native open source AI agent with desktop app, CLI, and API surfaces.
The host supports many model providers and connects to a large extension ecosystem through MCP, so the row is broader than a simple CLI wrapper.
Because Goose spans desktop, terminal, and embeddable API usage, its page should emphasize multi-surface architecture and extension routing.

Runtime boundary

The adapter target is the local goose agent runtime, which can appear as a desktop app, CLI, or API. goose owns provider selection, local execution, extension loading, and app state; agent-connector writes only verified host-native surfaces.

The repository says the project moved from Block to the Agentic AI Foundation.
goose is described as desktop app, CLI, and API for code, workflows, and other tasks.
The implementation is Rust-based and cross-platform.

MCP registration

MCP is central to goose: the README says it connects to many extensions through the Model Context Protocol. Extension loading should be treated as a first-class host architecture axis.

goose also supports ACP for using existing Claude, ChatGPT, or Gemini subscriptions.
MCP extensions should be distinguished from model providers.
Custom distributions can preconfigure providers, extensions, and branding.

Hook bridge

agent-connector currently models goose as a json-stdio host, but public goose docs foreground extensions and providers more than lifecycle hooks. Hook claims should therefore remain adapter-backed and source-checked.

MCP extension support does not automatically imply connector lifecycle hooks.
The API surface may allow embedding, but embedding APIs are not the same as hook files.

Content surfaces

goose content surfaces include hints, AGENTS.md-style files in the repository, workflow recipes, custom distributions, provider settings, and extension configuration. These are broader than coding-only command prompts.

The repository contains `.goosehints`, AGENTS.md, workflow_recipes, and custom distro documentation.
The agent is explicitly positioned for research, writing, automation, data analysis, and coding.

Marketplace and host-only affordances

goose's host-only affordance is open extensibility under AAIF: desktop, CLI, API, custom distributions, many providers, ACP, and MCP extensions. It is a major open-source reference for multi-surface local agents.

AAIF transition status should remain visible in the source review ledger.
Custom distributions are packaging architecture, not ordinary connector config.

Host-specific shape

Goose is a json-stdio CLI host where skills depend on the Summon path; MCP, hooks, skills, and memory are wired, while commands and subagents are not.

Form factor: CLI.
Native surfaces: MCP server, Hooks, Skills, Memory.
Wired surfaces: MCP server, Hooks, Skills, Memory.
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

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

Desktop, CLI, and API surfaces should remain distinct when claiming adapter support.
MCP extension support should not be described as lifecycle hook support without evidence.
AAIF transition may change docs URLs and source ownership over time.

Evidence checked

goose repository goose docs Agentic AI Foundation

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: goose
json-stdio renderer at src/adapters/goose/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/4 native surfaces wired. No visible host-native gap in the current coverage matrix.

Component Diagram

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

Goose 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.
goose adapter
Implements the json-stdio translation layer in src/adapters/goose/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 Goose; the selected surface is CLI.
2 · agent-connector
Resolve connector declaration
The package reads connector metadata and routes it to the goose adapter instead of exposing a generic host contract.
3 · goose 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 · Goose
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/4 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

Goose is a json-stdio CLI host where skills depend on the Summon path; MCP, hooks, skills, and memory are wired, while commands and subagents are not.

Form factor: CLI.
Native surfaces: MCP server, Hooks, Skills, Memory.
Wired surfaces: MCP server, Hooks, Skills, Memory.
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

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/1 wired

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

aaif-goose/goose repository

Goose has moved under the Agentic AI Foundation and is documented as a native open source AI agent with desktop app, CLI, and API surfaces.
The host supports many model providers and connects to a large extension ecosystem through MCP, so the row is broader than a simple CLI wrapper.
Because Goose spans desktop, terminal, and embeddable API usage, its page should emphasize multi-surface architecture and extension routing.

Evidence Map

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

Public source: aaif-goose/goose

Primary public repository or product source used for current host status and source links.

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

No confirmed host-native surface.

N/A

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

No confirmed host-native surface.

N/A