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 auth-config section
Three problems with the prior revision of the auth-config section: 1. Enumerated every masked field. Customers don't need the list; the rule is fail-closed (anything not client_id/consumer_key is obfuscated), and any enumeration rots when new fields ship. 2. Described the mask format (<first-4>...<last-4>, 8-char fallback). That's an internal implementation detail — useful to attackers, not actionable for customers, and brittle if we change the format. 3. Separate "previously returned in plaintext" bullet list duplicated the migration guidance without clarifying what action to take. New version states the contract in two bullets (managed = redacted, customer-owned = public IDs pass through, everything else obfuscated) and folds the plaintext-regression note into the migration sentence itself, naming only the two fields (client_secret, developer_token) that actually drive migration action. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>