본문으로 건너뛰기

ACP Integration

The client boundary uses the Agent Client Protocol for shared agent interactions and negotiated extensions for additional behavior. A host adapter translates that protocol into the component contracts. The master owns strategy and product policy. Clients own their presentation of the resulting content and state.

ACP adoption does not select a provider or delegate the native agent's strategy to another agent. Consuming an external whole-agent backend is a separate integration choice.

Version and scope​

The reviewed specification labels v1 Latest and v2 Draft. Implementations name their supported version and negotiate optional features. Supporting a version does not imply supporting every experiment. ACP versions.

The client protocol stays outside the neutral component vocabulary. Provider streams, internal history, and durable journals may have different shapes. The adapter performs an authorized projection of their meaning.

Custom presentation​

Standard messages carry streamed text and thoughts, media and resource content, tool progress, and plans. Clients choose layout, grouping, tool cards, preview styles, and reveal behavior. Specialized views keep usable ordinary content for clients without their renderer. Content, tool calls.

Optional display hints can use schema-supported metadata. Additional operations require negotiated extension methods and explicit results. An ignored display hint cannot establish execution, permission, or successful presentation. Incoming content and metadata remain untrusted. Extensibility.

Capability matrix​

Capabilities declare supported exchanges. Advertise an optional interaction only when its complete behavior is available through the selected host.

SurfaceContract
Conversation and toolsStandard content and progress, with client-owned presentation.
Plans and slash commandsStandard updates, with master-owned meaning and invocation behavior.
Session optionsStandard selectors where applicable. Persistent defaults keep their separate scope and activation rules.
Questions and permissionsSupported request/response forms, correlated with retained engine interactions.
Reusable subagentsStandard observation where supported. Additional child controls require their own advertised semantics.
Durable workExplicit acceptance, control, retention, and recovery guarantees beyond baseline protocol delivery.
Client filesystem and editor actionsSupported callbacks plus host-granted access to a specific resource and operation.

ACP's subagent draft permits child cancellation and restricts direct child prompt, steering, configuration, and resume. Richer child controls are therefore negotiated extensions, each with its own advertised semantics, until an upstream revision defines them. Subagent draft.

Tool kind mapping​

Tool kind is a presentation classification. Map the actual operation to the nearest standard category, such as read, edit, search, execute, or fetch. Use the general category when no narrower kind fits. A kind, title, or tool name confers no authority. The operation's declared scope and host grants determine whether execution is permitted.

Filesystem authority​

A host may execute filesystem tools itself or delegate supported operations to its client. The session selects that binding explicitly. A client's advertised filesystem support alone does not select it or grant arbitrary access. Both bindings preserve resource identity, conflict checks, and the host's authority rules. Filesystem protocol.

Stream resume semantics​

Loading or resuming a protocol session, reconnecting an observer, and resuming paused execution are distinct operations. The selected ACP version determines its history replay and prompt lifecycle. A durable implementation states its additional retention, identity, acceptance, and execution guarantees explicitly.

V1 prompt responses report the finished prompt turn. The v2 draft separates prompt acceptance from foreground state and permits messages without durable retention. Neither contract substitutes for verified engine suspension or settlement. V1 prompt lifecycle, v2 session semantics.

An adapter can retain an open protocol interaction while releasing the engine worker. Reconnection redelivers retained interactions under a supported recovery contract. It cannot replay an old connection's request identifier as new authority. Standard cancellation and resumable pause retain separate meanings.

Naming seam​

ACP owns wire names. Internal records keep the component vocabulary. Extensions use their reserved names and a namespace controlled by their author. Adapters validate the translation and reject unsupported operations explicitly.

Transport​

ACP standardizes a bidirectional JSON-RPC exchange over stdio. A custom binding must preserve protocol semantics and document connection establishment. The reviewed remote transport remains under specification. Transport selection adds no access rights. Transports.

A host may also offer an authenticated local shared-service binding that carries the same vocabulary to independent clients. The native host's baseline, negotiated extensions, client compatibility checks, and shared-service binding are defined in its client protocol binding.