Platform Features
Canopy Host and Cortex each publish a Platform Features manifest. A resolver combines a feature’s platform-wide state with its dependencies. This is one availability gate, not the authorization system: API routes still enforce authentication, team permissions, subscription or usage limits, and other resource-specific rules. The Host dashboard and CLI use the resolved manifest for UI visibility and early feedback, while the server remains authoritative. Cortex has its own resolver and authorization layer.
Checking what’s enabled
Section titled “Checking what’s enabled”GET https://api.canopy.pm/platform-features/resolvedNo authentication required, but the response shape depends on who’s asking:
- Anonymous or non-staff caller:
{"features": {"<key>": true, ...}}- only keys that are both enabled and public are listed. A disabled
key is simply absent (never
false); an internal key is always absent regardless of its state, so its existence isn’t disclosed.
- only keys that are both enabled and public are listed. A disabled
key is simply absent (never
- Canopy staff: the full picture for every key -
{enabled, reason, blockedBy, lifecycle, visibility}- including internal-only features.
Via the SDK:
const resolved = await sdk.platformFeatures.resolved();reason is one of enabled, disabled, dependency_disabled,
unknown_feature, or cycle_detected - a feature that depends on a
disabled feature resolves disabled with blockedBy naming the
dependency, even if its own state is enabled.
Launch states (lifecycle)
Section titled “Launch states (lifecycle)”Every feature has a lifecycle, separate from whether it is currently
enabled - a feature can be ga and disabled, or preview and enabled.
Treat lifecycle as the maturity signal and the resolved enabled value
as the availability signal.
| Lifecycle | Meaning |
|---|---|
planned |
Planned work, not a statement that the capability is currently available to customers. Some implementation groundwork may exist. |
experimental |
Early-stage capability with no compatibility promise. Visibility and whether it is enabled are separate fields, so experimental features may be internal or public and may be on or off. |
preview |
Unstable customer or staff surface; preview routes may change and are marked PREVIEW (unstable) in the API reference. A public preview feature additionally requires a team opt-in. No shipped feature is a preview today. |
ga |
Stable and relied upon: the live production path, documented and tested. A customer-facing API is additive-only under the API versioning policy. |
deprecated |
Being removed. |
Every feature that is built is generally available and enabled by default, so no
team has to opt in: Spaces, the Engineering Graph, security findings, MCP
hosting, multi-repository environments, Canopy Source, incidents, suggested Systems, groups, System notification routing, the
sandbox and the pipeline VM isolation tier among them. Blueprint, environment services, native machines,
environment backups, preview deployments and language settings are GA
and enabled by default. Compute jobs are also generally available when
the team’s Grove and compute budget allow them. If a guarded route returns
feature_disabled, check /platform-features/resolved for the public
platform state; other permissions may still need to be checked separately. Internal feature state is not disclosed to customer
accounts.
For CLI/SDK users
Section titled “For CLI/SDK users”For routes guarded by the platform-feature middleware, a disabled public
feature returns 403; a disabled internal feature returns 404,
indistinguishable from an unknown route. The CLI also checks the resolver
for mapped command groups and can fail fast with:
The ‘X’ command is currently unavailable - the “Y” platform feature is disabled on this Canopy environment.
This check is fail-open: if the CLI can’t reach the resolver at all (network blip, cache miss), it lets the command through and relies on the server’s own gate as the real authority - a transient client-side failure never blocks you from a feature that’s actually enabled.
Global feature state is managed by Canopy staff. The protected internal feature-administration guide describes those privileged workflows.