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
docs: update documentation for new changelog entries
github-actions[bot] committed
Sep 21, 2026 at 19:05 UTC
2f7e364523df08a367d1b7e68251e471b413593a
4 files changed
+74
docs/content/docs/authentication/manually-authenticating.mdx
+8
@@ -50,6 +50,14 @@ Redirect the user to the `redirectUrl`. After they authenticate, they'll return
50
If the user closes the Connect Link without completing auth, the connection remains in `INITIATED` status until it expires.
51
</Callout>
52
53
+## Reusing an active connection
54
+
55
+In TypeScript, call `session.ensureConnected("gmail")` to reuse the session's active connection. If none exists, it starts an authorization flow and waits for the connection to become active. The optional `timeout` sets how long to wait in milliseconds (default: `60000`).
56
+
57
+The result includes `toolkit`, `wasConnected`, and `connectedAccount`. `wasConnected` is `true` when an active connection already exists. Toolkits that don't require authentication also return `wasConnected: true`, with no `connectedAccount`.
58
+
59
+Use `session.authorize()` and `waitForConnection()` when you need to display or redirect to the Connect Link. `ensureConnected()` waits internally and doesn't return the redirect URL. Calling `authorize()` always starts a new authorization flow, even if an active connection exists.
60
+
61
## Redirecting users after authentication
62
63
Pass a `callbackUrl` to control where users land after authenticating. You can include query parameters to carry context through the flow, for example to identify which `userID` or session triggered the connection.
docs/content/docs/configuring-sessions.mdx
+8
@@ -26,6 +26,14 @@ By default, a session has access to every toolkit in the Composio catalog. Your
26
27
You can also attach local custom tools and custom toolkits that run in-process alongside Composio tools. See [Custom tools and toolkits](/docs/extending-sessions/custom-tools-and-toolkits).
28
29
+## Reading and updating session configuration
30
+
31
+In TypeScript, `session.config` exposes the configuration returned by the server. Call `session.update()` to change selected fields. It preserves omitted fields, updates `session.config` in place, and returns the updated configuration. See [Updating a session](/docs/how-composio-works#how-sessions-behave) for an example.
32
+
33
+<Callout>
34
+If you implement the TypeScript `Session` interface yourself, include the required `config` member. Sessions created by the SDK provide it automatically.
35
+</Callout>
36
+
37
## Enabling toolkits
38
39
To limit a session to specific toolkits, pass an array of toolkit slugs. The agent can only discover and use tools from these toolkits.
docs/content/docs/providers/index.mdx
+56
@@ -45,6 +45,62 @@ Use these when you call a model SDK directly.
45
/>
46
</ProviderGrid>
47
48
+## TypeSafe
49
+
50
+Use TypeSafe's Jev model to select a Composio tool with a confidence score. The provider compiles tools into typed questions and returns a complete `call`, a `partial` call with missing arguments, or an `abstain` decision.
51
+
52
+Set `COMPOSIO_API_KEY` and `TYPESAFE_API_KEY` in your environment before running decisions.
53
+
54
+<Tabs groupId="language" items={['Python', 'TypeScript']} persist>
55
+<Tab value="Python">
56
+
57
+```bash
58
+pip install composio composio-typesafe typesafe-sdk==0.6.0
59
+```
60
+
61
+```python
62
+from composio import Composio
63
+from composio_typesafe import TypesafeProvider
64
+
65
+provider = TypesafeProvider()
66
+composio = Composio(provider=provider)
67
+tool_set = composio.tools.get(
68
+ user_id="user_123",
69
+ tools=["GITHUB_LIST_REPOSITORY_ISSUES"],
70
+)
71
+decision = provider.decide(tool_set, "List the closed issues of ComposioHQ/composio")
72
+
73
+if decision["kind"] != "abstain":
74
+ result = provider.execute(
75
+ "user_123",
76
+ decision,
77
+ arguments={"owner": "ComposioHQ", "repo": "composio"},
78
+ )
79
+ print(result["data"])
80
+```
81
+
82
+Use `provider.shortlist_tools()` to narrow the tools before deciding, or `provider.confidence_gate()` to apply a minimum judgement score before execution. Destructive tools require explicit confirmation through `provider.execute(..., confirm=True)`.
83
+
84
+</Tab>
85
+<Tab value="TypeScript">
86
+
87
+```bash
88
+npm install @composio/core @composio/typesafe @typesafe-ai/sdk@0.6.0 zod
89
+```
90
+
91
+Import `TypesafeProvider` from `@composio/typesafe` and pass an instance as the `provider` option to `new Composio()`. Fetch tools with `composio.tools.get()`, then call `await provider.decide(toolSet, request)` and `await provider.execute(userId, decision, { arguments })`.
92
+
93
+Use `provider.shortlistTools()` to narrow the tools before deciding, or `provider.confidenceGate()` to apply a minimum judgement score before execution. Destructive tools require explicit confirmation through `provider.execute(userId, decision, { confirm: true })`.
94
+
95
+This provider requires Node.js 24.17 or newer. Root schema composition that can hide required arguments is rejected. Supply prototype-named arguments explicitly; `__proto__` is preserved as caller data during execution.
96
+
97
+</Tab>
98
+</Tabs>
99
+
100
+Jev binds closed-set arguments such as enums and booleans. You supply open-ended values such as text, IDs, and numbers through `arguments` when executing. Handle `abstain` without executing a tool, and supply the missing arguments for a `partial` call.
101
+
102
+The confidence score is the least certain judgement the call depends on, not the probability that the whole call is correct. Only pass confirmation after you've approved a destructive action.
103
+
104
## Agent frameworks
105
106
Use these when an agent framework orchestrates the tool calls for you.
docs/content/docs/tools-direct/executing-tools.mdx
+2
@@ -540,6 +540,8 @@ Automatic S3 downloads stop at 100 MiB, even when the server omits or reports an
540
automatic S3 downloads return `file_downloaded: false`. `RemoteFile` connection failures and
541
streamed-body failures raise `RemoteFileDownloadError`.
542
543
+URL-based file fetches validate the resolved address at each redirect and reject internal, reserved, and transition-network address ranges. Both SDKs follow standard HTTP redirect method and body rules and strip credentials on cross-origin redirects.
544
+
545
## Security for local file paths
546
547
Automatic upload reads local paths (or uses them in `files.upload`) and sends file content to Composio storage. To reduce the chance of **accidentally uploading secrets** (SSH keys, cloud credentials, `.env` files, or assistant project folders), the SDK checks local paths against a **default denylist** of path segments and file-name patterns. **HTTP/HTTPS URLs and `File` objects are not matched like local path strings**; only local string paths go through this check.