@devries-cameron20 / composio-1 / commits / 31c2c991f
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.

docs(changelog): tighten opening and why section

Anshu Garg committed Apr 21, 2026 at 01:42 UTC 31c2c991f79d20a7878326e19c790c5465e77be8
1 file changed +5 -7
docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx
+5 -7
@@ -1,10 +1,10 @@
1 ---
2 title: "Automatic Credential Masking for Composio-Managed Connections"
3 -description: "We've strengthened how credentials are protected for Composio-managed auth configs. Access and refresh tokens are now always masked in API responses for these connections, keeping the shared OAuth applications that back our default integrations reliable for every team using them."
3 +description: "Access and refresh tokens for connections on Composio-managed auth configs are now always masked in API responses, regardless of project-level masking. Connections on your own auth config are unchanged."
4 date: "2026-04-21"
5 ---
6
7 -We've strengthened how credentials are protected on Composio-managed auth configs. For connections that use one of Composio's default toolkit integrations, access tokens, refresh tokens, and the `Authorization` header are now always masked in `connected-accounts` API responses — independent of your project's `mask_secret_keys_in_connected_account` setting.
7 +For connections created through a Composio-managed auth config, access tokens, refresh tokens, and the `Authorization` header are now always masked in `connected-accounts` API responses — regardless of your project's `mask_secret_keys_in_connected_account` setting.
8
9 **Most integrations need no changes.**
10
@@ -13,15 +13,13 @@ We've strengthened how credentials are protected on Composio-managed auth config
13
14 ## What is a Composio-managed auth config?
15
16 -When you connect a user through a toolkit's default integration — for example, Gmail or Slack without registering your own OAuth application — the connection is authorized through an OAuth application that Composio maintains on behalf of every team using that default. The access and refresh tokens the provider issues for that connection are bound to Composio's shared OAuth client.
16 +When you connect a user through a toolkit's default integration — for example, Gmail or Slack without registering your own OAuth application — the connection runs through an OAuth application that Composio owns and operates on behalf of every team using that default. The access and refresh tokens the provider issues are bound to Composio's shared OAuth client.
17
18 You can tell a connection is Composio-managed by the `auth_config.is_composio_managed: true` field on the connected-account resource.
19
20 -## Why we're making this change
20 +## Why this change
21
22 -Because the OAuth application is shared across every team on that default, any action a provider takes on it — rate limits, scope adjustments, or in the extreme case, suspending the OAuth client — is felt by everyone using it. A shared application means shared outcomes.
23 -
24 -Keeping these credentials inside Composio removes an avenue of risk that no single customer can contain on their own, and lets us keep the default integrations healthy and available for every team that relies on them. Tool execution flows continue to work without any change; Composio uses the tokens server-side so your agents don't need to.
22 +Because the OAuth application is shared across every team on that default, any action a provider takes on it — rate limits, scope adjustments, or in the extreme case, suspending the OAuth client — affects everyone using it. Keeping the credentials inside Composio protects the reliability of the shared integrations, and tool execution continues to work without any change; Composio uses the tokens server-side.
23
24 ## What changes in the API
25