Compatibility and upgrades
Keep module, schema, and wire protocol versions distinct.
Three versions, three meanings
Section titled “Three versions, three meanings”| Identity | This documentation |
|---|---|
| Go module release | v1.4.0 |
| ACP v1 source schema | schema-v1.23.0 |
| Negotiated wire protocol | ACP v1 |
A module upgrade is not the same as negotiating a different protocol. Check optional capabilities during initialization instead of assuming every agent supports every generated method.
Upgrading to v1.4
Section titled “Upgrading to v1.4”Read the version-specific upgrade guide and review your handlers, generated types, and subprocess lifecycle against the published API.
Interoperability evidence
Section titled “Interoperability evidence”The project maintains an interoperability matrix against the official TypeScript and Rust SDKs. That evidence is scoped to the tested revisions and paths; your own application’s permission and process policies still need validation.
See API reference and Releases.
Based on the public project documentationacp-go-sdk · ed838d7 ↗