Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

next
ts 25 lines 1.37 KB
Raw
1 /**
2 * Shared terminology migration table appended to all guardrail sets.
3 * Maps old v1/v2 terms to current v3 equivalents so AI agents
4 * can translate outdated references in error messages, docs, or user prompts.
5 */
6 export const TERMINOLOGY_MIGRATION = `
7
8 ---
9
10 ## Terminology Migration (old → current)
11
12 If you encounter these terms in error messages, old documentation, or user prompts, translate them to the current equivalents. **Do not use the old terms in generated code or explanations.**
13
14 | Old term (v1/v2) | Current term (v3) | In code |
15 |---|---|---|
16 | entity ID | user ID | \`user_id\` parameter |
17 | actions | tools | e.g., \`GITHUB_CREATE_AN_ISSUE\` is a *tool* |
18 | apps / appType (legacy v1/v2 API field) | toolkits | e.g., \`github\` is a *toolkit*. The current word **App** is *not* legacy: it names a catalog grouping of sibling toolkits (the Notion app groups \`notion\` and \`notion_mcp\`); do not translate it |
19 | integration / integration ID | auth config / auth config ID | \`auth_config_id\` parameter |
20 | connection | connected account | \`connected_accounts\` namespace |
21 | ComposioToolSet / OpenAIToolSet | \`Composio\` class with a provider | \`Composio(provider=...)\` |
22 | toolset | provider | e.g., \`OpenAIProvider\` |
23
24 If a user says "entity ID", they mean \`user_id\`. If they say "integration", they mean "auth config". Always respond using the current terminology.
25 `;