Availability & boundaries
A product map is not a promise that every feature is enabled in every account.
How to interpret a feature
| State | Meaning |
|---|---|
| Documented setup path | The app includes guidance; provisioning and permissions still apply |
| Draft-ready | The agent has enough context to prepare a reviewable output |
| Automation-ready | Additional readiness checks pass; action-specific approvals still apply |
| Connected | Authorization exists; inspect the resource and actual sync or job |
| Plan / brief | A proposal, not verified connected execution |
| Local preview | Implemented and tested locally; not yet a production capability |
Current preview boundary
The 29-tool workspace library, saved run history and shared agent tool access are local-preview features. Public tool generation and inspection remain separate from that release. Check the live application before instructing a team to use Tools in production.
Provider and role limits
Connections may be blocked by a provider’s app approval, quota or account eligibility. A plan upgrade does not fix an unauthorized provider account. Likewise, an integration grant does not override your workspace role or approve content.
Not a public API reference
These are product operating guides. Internal endpoint paths and implementation details are not a supported public API contract. Contact the team about an integration requirement rather than building against an undocumented route.
Something unclear or out of date?
Suggest a correction