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): remove temporary per-project exception mention
The per-project override will be an internal-only operational toggle for specific customers we reach out to directly — not a documented customer-facing escape hatch. Reverting the paragraph so the changelog doesn't advertise it. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Anshu Garg committed
Apr 22, 2026 at 11:59 UTC
5ac5082cf31692bdd64fd9eec6da3b4c914ed799
1 file changed
-2
docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx
-2
@@ -117,8 +117,6 @@ Auth configs:
117
118
**Auth-config secrets** (`client_secret`, `developer_token`, etc.). Keep these alongside the code that created the auth config — for example, in your own secret manager at upload time. The auth-config GET endpoints will only return masked or redacted values going forward.
119
120
-**Temporary per-project exception.** If this change blocks an active production integration and you cannot complete the migration above immediately, contact support. We can toggle off forced redaction for Composio-managed connections on your project for a limited migration window, after which the project reverts to the default redacted behavior.
121
-
120
<Callout type="info">
121
If your integration relies on reading `access_token`, `refresh_token`, `client_secret`, or `developer_token` from Composio API responses, you will need to act. All other integrations continue to work as before.
122
</Callout>