@devries-cameron20 / composio Mirror · read-only / commits / c50413432
Fork 0

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

Anshu Garg committed Apr 21, 2026 at 02:02 UTC c5041343218f04f9449409e05a4db9416f705b3f
1 file changed +1 -3
docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx
+1 -3
@@ -19,9 +19,7 @@ You can identify a Composio-managed connection by the `auth_config.is_composio_m
19
20 ### Why this change
21
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.
22 +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.
23
24 ### Example
25