Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 23:30 UTC
docs(changelog): make the risk visible in why-this-change
Anshu Garg committed
Apr 21, 2026 at 01:56 UTC
828a8ee56a9e70d568ec6401a5610e0806412ba8
1 file changed
+3
-1
docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx
+3
-1
@@ -19,7 +19,9 @@ You can identify a Composio-managed connection by the `auth_config.is_composio_m
19
20
### Why this change
21
22
-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.
22
+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.
23
+
24
+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.
25
26
### Example
27