Skip to content

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

docs(changelog): make the risk visible in why-this-change

Anshu Garg828a8ee56a9e
diff --git a/docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx b/docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx
index d952788db..f3febc4a9 100644
--- a/docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx
+++ b/docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx
@@ -19,7 +19,9 @@ You can identify a Composio-managed connection by the `auth_config.is_composio_m
### Why this change
-Because the OAuth application is shared, any action a provider takes on it — rate limits, scope adjustments, or in the extreme case, suspending the OAuth client — affects everyone using that default. Keeping the credentials server-side protects the reliability of the shared integrations without changing how tool execution works.
+These default integrations run on OAuth applications that Composio maintains and that every team on the default shares. If a provider takes enforcement action on one — rate limits, scope restrictions, or suspending the client outright — the integration goes down for every team on it at the same time.
+
+Raw tokens from `connected-accounts` responses carry that shared OAuth application's identity, which meant a single misuse anywhere could affect every other team relying on the same default. Keeping the tokens inside Composio — where your tools already execute them — removes that exposure without changing how anything works for you.
### Example