@devries-cameron20 / composio Mirror · read-only / commits / 1046b4a52
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.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 11:00 UTC

Reorganize session recommendation and logs note

Moved the recommendation for sessions to the end of the document and added a note about inspecting tools with the Logs API.

Brendan O'Leary committed Sep 22, 2026 at 14:32 UTC 1046b4a5257bdaf360cb8fdcd934c61de68d8240
1 file changed +1 -4
docs/content/docs/quickstart.mdx
+1 -4
@@ -6,9 +6,6 @@ keywords: [tutorial, setup, first agent, sessions, tool router]
6
7 Build an agent that chooses Composio tools at runtime. Type a task, connect an app if needed, and continue in the same conversation.
8
9 -Sessions are recommended for new integrations. If you maintain a legacy direct-execution integration, see [Sessions vs direct execution](/docs/sessions-vs-direct-execution) and the [migration guide](/docs/migration-guide/direct-to-sessions).
10 -
11 -
9 <div className="not-prose my-6 grid grid-cols-1 items-start gap-4 md:grid-cols-2">
10 <div>
11 <p className="mb-6">
@@ -484,7 +481,7 @@ Ask for any task that needs an app tool: `Summarize my unread emails from today`
481 `user_123` is only for this local example. Replace it with a stable ID from your database. Each ID gets separate connections and tool calls.
482 </Callout>
483
487 -You can inspect the selected tools, inputs, responses, and timing with the [Logs API](/reference/api-reference/logs).
484 +Note: Sessions are recommended for new integrations. If you maintain a legacy direct-execution integration, see [Sessions vs direct execution](/docs/sessions-vs-direct-execution) and the [migration guide](/docs/migration-guide/direct-to-sessions). You can inspect the selected tools, inputs, responses, and timing with the [Logs API](/reference/api-reference/logs).
485
486 ## Adapt the example
487