Skip to content

Stability and compatibility

Choose a verified integration boundary and make upgrades without silently changing behavior.

What support means

Ghost supports a shared React view contract plus optional native bindings and format projections. A protocol route can support several server frameworks without a new Ghost package for each. Support does not mean every native feature becomes a ChatController method.

Examples compile against the public packed package and the versions below. Native SDK classes and maintained stream clients are exercised with deterministic local fixtures. These checks do not certify your deployed server, credentials, network policy or every upstream feature. No paid model call is required for the checks.

Checked versions

The @ghost-ui/core public subpaths in these guides are shipped with the local artifact. Optional SDKs are not core dependencies. Install only the selected path plus its native peers and view dependencies. The private verification fixture pins SDKs; it is not a production dependency bundle.

Upgrade by contract

Keep the previous working lockfile, update one integration and compile the actual native hook/client against its Ghost adapter. Exercise streaming replacement, stable IDs, cancellation, failed sends, unsupported parts and any approval or file workflow you use. Check the SDK's own migration guide for wire and server changes.

Vercel v7 is the current executable recipe. v6/v5 retain the parts-based UI-message family but are not claimed as checked hook versions here. v4's legacy data stream has a separate maintained decoder route; do not feed its bytes to the current transport. A2A v0.3 has a separate native compatibility API; the Ghost examples target v1. Eve RC and Managed Agents beta may change outside stable-release expectations.

When to use a lower level

Use native SDK APIs for new capabilities before adding a Ghost abstraction. Project known content and retain an explicit unknown/data representation for the rest. Add a Ghost command only when its identity, lifecycle and failure meaning can be stated without losing native behavior. See adapters and threads.