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 22, 08:15 UTC
docs: add execution flow diagram showing toolkit tools downstream
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sushmithamallesh committed
Feb 19, 2026 at 13:49 UTC
497861d4a3942e3deede9bba124c5f845790b388
1 file changed
+20
docs/content/docs/how-composio-works.mdx
+20
@@ -67,6 +67,26 @@ graph LR
67
68
Meta tool calls within a session share context through a `session_id`. The agent can search for a tool in one call and execute it in the next without losing state. Tools can also store information (IDs, relationships) in memory for subsequent calls.
69
70
+### How they work together
71
+
72
+The meta tools are how the agent reaches the actual toolkit tools:
73
+
74
+```mermaid
75
+graph TD
76
+ A["Agent: 'Create a GitHub issue for this bug'"] --> B["COMPOSIO_SEARCH_TOOLS"]
77
+ B --> C["GITHUB_CREATE_ISSUE"]
78
+ B --> C2["GITHUB_LIST_ISSUES"]
79
+ B --> C3["GITHUB_GET_REPO"]
80
+ B -.- B1["Returns matching tools with schemas"]:::annotation
81
+ C --> D["COMPOSIO_MULTI_EXECUTE_TOOL"]
82
+ D --> E["GitHub API"]
83
+ D -.- D1["Injects user's OAuth token, makes the call"]:::annotation
84
+
85
+ classDef annotation stroke-dasharray: 5 5
86
+```
87
+
88
+`SEARCH_TOOLS` discovers the right toolkit tools for the task. `MULTI_EXECUTE_TOOL` runs them against the external API with the user's credentials. If the user isn't authenticated yet, `MANAGE_CONNECTIONS` handles that in between.
89
+
90
For large responses or bulk operations (labeling hundreds of emails, processing CSVs), the agent uses `COMPOSIO_REMOTE_WORKBENCH` to run Python with helper functions like `invoke_llm` and `run_composio_tool`.
91
92
<Card icon={<BookOpen />} title="Tools and toolkits" href="/docs/tools-and-toolkits" description="Meta tools, context management, and execution" />