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): tighten why-this-change to single paragraph

Anshu Gargc5041343218f
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 f3febc4a9..fa6334ba6 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,9 +19,7 @@ You can identify a Composio-managed connection by the `auth_config.is_composio_m
### Why this change
-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.
+A single OAuth application backs every team on a default integration, and the tokens we return are bound to it. If a provider throttles, restricts, or suspends that app in response to misuse of one of its tokens, the integration becomes unavailable for every team on the default at once. Masking the tokens keeps that exposure out of API responses; Composio still uses them server-side, so tool execution is unchanged.
### Example