Agent Architecture

CodeBuddy

CodeBuddy is a Tencent Cloud source-light host row spanning IDE, plugin, and CLI product surfaces. Public text points to an end-to-end product/design/code/deploy workflow, but local connector claims must stay tied to adapter evidence.

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

codebuddy

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

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.
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: Statusline handler.

Verified Architecture

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

Sequence #1

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 official page identifies Tencent Cloud Code Assistant CodeBuddy as an AI code editor, so the row stays product-homepage evidence rather than open-source code evidence.
Because the rendered public page exposes little inspectable architecture text, this page should remain conservative about hooks, MCP, memory, and CLI internals.
The adapter still models CodeBuddy as a json-stdio host from local registry data, but source review should call out that public architecture details are thin.

Runtime boundary

The adapter target is the local CLI-style CodeBuddy surface, while the public product spans plugin, standalone IDE, and CLI channels. The architecture page should mark this as source-light because the website does not expose full local internals in text.

Public descriptions tie CodeBuddy to Tencent Cloud, Hunyuan, DeepSeek, and product-to-deploy workflows.
The CLI channel is relevant to DevOps and terminal users, but exact storage paths need adapter evidence.

MCP registration

MCP support should be described only through the current connector adapter and verified local files. Cloud ecosystem integration and deployment automation are not the same as an MCP server registry.

Tencent Cloud integration may involve cloud credentials and deployment APIs.
The page should avoid inferring local MCP semantics from broad product workflow claims.

Hook bridge

agent-connector tracks CodeBuddy as a json-stdio host, so hook support should be framed as an adapter bridge. Product agents such as planning, design, coding, and deploy roles should not be treated as lifecycle hook events.

Multi-agent product roles are orchestration concepts.
Hook payloads and decisions need local runtime tests before event-level claims expand.

Content surfaces

CodeBuddy content surfaces are likely split across product requirements, design artifacts, code generation, deployment plans, and CLI prompts. The archive should distinguish those cloud/product artifacts from local commands, skills, and memory.

The product-to-deploy flow is useful for workflow architecture study.
Source-light status means concrete file locations should remain conservative.

Marketplace and host-only affordances

The host-only affordance is Tencent Cloud's end-to-end agent workflow across idea, design, implementation, and deployment. That should be visible without overstating unsupported local connector surfaces.

Cloud deployment and design-to-code features are host product capabilities.
The page should show CodeBuddy as a multi-surface product host, not just a terminal process.

Host-specific shape

CodeBuddy follows the Claude Code family: MCP, hooks, commands, skills, agents, and CODEBUDDY.md memory are file-driven, while its native statusLine key is still a visible adapter gap.

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

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 commands + skills + subagents + memory surfaces after install; runtime-only surfaces stay behind the host boundary..

Known Limits

Source-light official pages require cautious internals language.
Cloud workflow claims are not local MCP or hook contracts.
Exact CLI config paths should remain adapter-backed.

Evidence checked

CodeBuddy website CodeBuddy overview CodeBuddy official site

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: codebuddy
json-stdio renderer at src/adapters/codebuddy/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 commands + skills + subagents + memory surfaces after install; runtime-only surfaces stay behind the host boundary.
7
Coverage ceiling
6/7 native surfaces wired. Statusline handler are host-native but not wired yet.

Component Diagram

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

CodeBuddy 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.
codebuddy adapter
Implements the json-stdio translation layer in src/adapters/codebuddy/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 commands + skills + 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 CodeBuddy; the selected surface is CLI.
2 · agent-connector
Resolve connector declaration
The package reads connector metadata and routes it to the codebuddy adapter instead of exposing a generic host contract.
3 · codebuddy 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 · CodeBuddy
Host loads artifacts
host launches JSON-stdio hook command
5 · Agent runtime
Run through host boundary
Users see managed commands + skills + subagents + memory surfaces after install; runtime-only surfaces stay behind the host boundary.
6 · Coverage matrix
Expose remaining ceiling
6/7 native surfaces wired. Statusline handler 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

CodeBuddy follows the Claude Code family: MCP, hooks, commands, skills, agents, and CODEBUDDY.md memory are file-driven, while its native statusLine key is still a visible adapter gap.

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

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 commands + skills + 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

3/4 wired

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

CodeBuddy official site

The official page identifies Tencent Cloud Code Assistant CodeBuddy as an AI code editor, so the row stays product-homepage evidence rather than open-source code evidence.
Because the rendered public page exposes little inspectable architecture text, this page should remain conservative about hooks, MCP, memory, and CLI internals.
The adapter still models CodeBuddy as a json-stdio host from local registry data, but source review should call out that public architecture details are thin.

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/codebuddy/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, Commands, Skills, 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