Agent Architecture

Amazon Q Developer CLI

Amazon Q Developer CLI is now a legacy/open-source reference row because the public repository says it is no longer actively maintained and points users toward the closed-source Kiro CLI. The architecture page should preserve the terminal-agent design while clearly marking the maintenance transition.

Source reviewed #34Checked 2026-07-06

Setup guide Source

Run type

CLI

Adapter

json-stdio

Source

OSS · aws/amazon-q-developer-cli

Stars

★ 2k

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

amazon-q

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 Amazon Q Developer CLI.

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, Subagents, 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 #34

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.

The Amazon Q Developer CLI repository states it is no longer actively maintained except for critical security fixes and points latest usage to Kiro CLI.
The project layout identifies `chat_cli` as the `q` CLI entry point, with Rust crates and technical docs as the implementation structure.
Because the upstream is effectively superseded, adapter coverage should preserve current paths while making future feature claims conservative.

Runtime boundary

The adapter row targets the local terminal CLI that historically shipped as Amazon Q Developer CLI. The repository now marks the project as not actively maintained and redirects general availability attention to Kiro CLI, so status must appear in the architecture page.

The open-source repository contains the `chat_cli` terminal application and project layout.
The current maintenance note limits future compatibility expectations for this adapter row.
Kiro CLI is a related successor path but is not open-source-equivalent evidence.

MCP registration

Amazon Q belongs in the MCP-capable CLI family in the local matrix, but the maintenance transition means new MCP claims should be checked against current AWS or Kiro documentation before expansion.

Historical Amazon Q CLI behavior should not be projected into Kiro without Kiro-specific source or docs.
AWS account, identity, and region configuration can affect tool authority beyond local file installation.

Hook bridge

agent-connector classifies Amazon Q as a json-stdio host, so local hook support should be described through the adapter contract. The page should avoid implying active upstream hook evolution from a repository that is now security-fix-only.

Legacy status makes regression tests more important than roadmap inference.
Hook event vocabulary should stay adapter-backed and should not be borrowed from Kiro by analogy.

Content surfaces

Amazon Q's CLI content surfaces include terminal chat, project context, and AWS-oriented developer assistance. Because the repository is in maintenance mode, the archive should show current connector support while steering future feature study toward Kiro as a separate host.

Project context and AWS identity are part of the terminal-agent operating environment.
Do not merge Kiro specs, steering files, or IDE behavior into this row without adapter separation.

Marketplace and host-only affordances

The host-only story is the AWS developer ecosystem and the Kiro transition. Amazon Q Developer CLI remains valuable as an open-source reference, but plugin marketplace and new agent-host affordances should be studied on Kiro or AWS docs separately.

Maintenance status should appear beside any flagship or frontier badges.
AWS ecosystem integration is a host affordance, not a connector implementation guarantee.

Host-specific shape

Amazon Q Developer CLI is a json-stdio host with MCP, agent-format hooks, JSON-file subagents, and project rules memory; prompt commands and skills remain unwired.

Form factor: CLI.
Native surfaces: MCP server, Hooks, Subagents, Memory.
Wired surfaces: MCP server, Hooks, Subagents, 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 subagents + memory surfaces after install; runtime-only surfaces stay behind the host boundary..

Known Limits

Treat the open-source Amazon Q Developer CLI as legacy unless current AWS docs say otherwise.
Do not transfer Kiro CLI behavior back into Amazon Q without direct evidence.
Security-fix-only maintenance means compatibility should be verified by tests before claims expand.

Evidence checked

Amazon Q Developer CLI repository Amazon Q Developer CLI docs Kiro

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: amazon-q
json-stdio renderer at src/adapters/amazon-q/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 subagents + 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 Amazon Q Developer CLI integration and which side owns each one.

Amazon Q Developer CLI 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.
amazon-q adapter
Implements the json-stdio translation layer in src/adapters/amazon-q/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 subagents + 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 Amazon Q Developer CLI; the selected surface is CLI.
2 · agent-connector
Resolve connector declaration
The package reads connector metadata and routes it to the amazon-q adapter instead of exposing a generic host contract.
3 · amazon-q 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 · Amazon Q Developer CLI
Host loads artifacts
host launches JSON-stdio hook command
5 · Agent runtime
Run through host boundary
Users see managed subagents + 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

Amazon Q Developer CLI is a json-stdio host with MCP, agent-format hooks, JSON-file subagents, and project rules memory; prompt commands and skills remain unwired.

Form factor: CLI.
Native surfaces: MCP server, Hooks, Subagents, Memory.
Wired surfaces: MCP server, Hooks, Subagents, 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 subagents + 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: Subagents. Host-native gaps: none. Not confirmed: Commands, Skills, 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

aws/amazon-q-developer-cli repository

The Amazon Q Developer CLI repository states it is no longer actively maintained except for critical security fixes and points latest usage to Kiro CLI.
The project layout identifies `chat_cli` as the `q` CLI entry point, with Rust crates and technical docs as the implementation structure.
Because the upstream is effectively superseded, adapter coverage should preserve current paths while making future feature claims conservative.

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: aws/amazon-q-developer-cli

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/amazon-q/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, Subagents, 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

No confirmed host-native surface.

N/A

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

No confirmed host-native surface.

N/A