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, 13:15 UTC
fix(docs): Convert Fern components to Fumadocs components in changelog
- Replace <CodeBlocks>/<CodeGroup> with <Tabs>/<Tab> - Replace <Note> with <Callout type="info"> - Replace <Warning> with <Callout type="warn"> - Replace <Frame> with standard markdown image Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sushmithamallesh committed
Jan 24, 2026 at 02:03 UTC
3c0de2cead0f3e189be3a39d5803edc508d0b9a1
4 files changed
+110
-91
docs/content/changelog/01-08-26-mcp-api-key-enforcement.mdx
+11
-9
@@ -7,9 +7,9 @@ date: "2026-01-08"
7
8
We've introduced a new project-level security setting that allows you to require API key authentication for all MCP server requests. This opt-in feature gives you fine-grained control over who can access your MCP endpoints.
9
10
-<Note>
10
+<Callout type="info">
11
**Opt-in today, default soon**: This feature is currently opt-in. Starting **March 1, 2026**, it will be enabled by default for new organizations. We recommend enabling it now to prepare your integrations.
12
-</Note>
12
+</Callout>
13
14
## What's New
15
@@ -60,9 +60,7 @@ curl -X POST "https://mcp.composio.dev/{your_mcp_server_url}" \
60
3. Find the **"Require API Key for MCP"** toggle
61
4. Enable the toggle
62
63
-<Frame>
64
- <img src="/assets/images/mcp-api-key-toggle.png" alt="MCP API Key Toggle in Project Settings" />
65
-</Frame>
63
+
64
65
### Via API
66
@@ -87,8 +85,9 @@ curl -X PATCH "https://backend.composio.dev/api/v3/org/project/config" \
85
86
### Via Code
87
90
-<CodeGroup>
91
-```python title="Python"
88
+<Tabs groupId="language" items={['Python', 'TypeScript']}>
89
+<Tab value="Python">
90
+```python
91
import requests
92
93
response = requests.patch(
@@ -102,7 +101,9 @@ response = requests.patch(
101
102
print(response.json())
103
```
105
-```typescript title="TypeScript"
104
+</Tab>
105
+<Tab value="TypeScript">
106
+```typescript
107
const response = await fetch(
108
"https://backend.composio.dev/api/v3/org/project/config",
109
{
@@ -117,7 +118,8 @@ const response = await fetch(
118
119
console.log(await response.json());
120
```
120
-</CodeGroup>
121
+</Tab>
122
+</Tabs>
123
124
## When to Use This
125
docs/content/changelog/01-14-26-auth-config-patch-semantics.mdx
+55
-52
@@ -19,9 +19,9 @@ date: "2026-01-14"
19
20
The `PATCH /api/v3/auth_configs/{id}` endpoint now implements proper partial update semantics. Previously, omitting fields would clear them (behaving like PUT). Now, omitted fields are preserved—only explicitly provided fields are modified.
21
22
-<Warning>
22
+<Callout type="warn">
23
**Breaking Change**: If you relied on omitting fields to clear them, you must now explicitly send `null` or `[]`. See [Migration Guide](#migration-guide) below.
24
-</Warning>
24
+</Callout>
25
26
## What Changed
27
@@ -32,9 +32,9 @@ The `PATCH /api/v3/auth_configs/{id}` endpoint now implements proper partial upd
32
| `scopes` (type: default) | Cleared if omitted | Preserved if omitted |
33
| `restrict_to_following_tools` | Reset to `[]` if omitted | Preserved if omitted |
34
35
-<Note>
35
+<Callout type="info">
36
**Merge Behavior**: The `credentials` object is merged—send only the fields you want to change, and existing fields are preserved.
37
-</Note>
37
+</Callout>
38
39
## New Capabilities
40
@@ -42,8 +42,9 @@ The `PATCH /api/v3/auth_configs/{id}` endpoint now implements proper partial upd
42
43
Update just `client_secret` without resending `client_id` or other fields:
44
45
-<CodeBlocks>
46
-```python title="Python SDK"
45
+<Tabs groupId="language" items={['Python', 'TypeScript']}>
46
+<Tab value="Python">
47
+```python
48
from composio import Composio
49
50
composio = Composio()
@@ -51,18 +52,18 @@ composio = Composio()
52
# Only send the field you want to update - other credentials are preserved
53
54
composio.auth_configs.update(
54
-"ac_yourAuthConfigId",
55
-options={
56
-"type": "custom",
57
-"credentials": {
58
-"client_secret": "new_rotated_secret",
59
-},
60
-},
55
+ "ac_yourAuthConfigId",
56
+ options={
57
+ "type": "custom",
58
+ "credentials": {
59
+ "client_secret": "new_rotated_secret",
60
+ },
61
+ },
62
)
62
-
63
-````
64
-
65
-```typescript title="TypeScript SDK"
63
+```
64
+</Tab>
65
+<Tab value="TypeScript">
66
+```typescript
67
import { Composio } from "@composio/core";
68
69
const composio = new Composio();
@@ -74,16 +75,17 @@ await composio.authConfigs.update("ac_yourAuthConfigId", {
75
client_secret: "new_rotated_secret",
76
},
77
});
77
-````
78
-
79
-</CodeBlocks>
78
+```
79
+</Tab>
80
+</Tabs>
81
82
### Update Tool Restrictions Without Touching Credentials
83
84
Previously, this would fail because `credentials` was required. Now it works:
85
85
-<CodeBlocks>
86
-```python title="Python SDK"
86
+<Tabs groupId="language" items={['Python', 'TypeScript']}>
87
+<Tab value="Python">
88
+```python
89
from composio import Composio
90
91
composio = Composio()
@@ -91,18 +93,18 @@ composio = Composio()
93
# Update tool restrictions - credentials are automatically preserved
94
95
composio.auth_configs.update(
94
-"ac_yourAuthConfigId",
95
-options={
96
-"type": "custom",
97
-"tool_access_config": {
98
-"tools_available_for_execution": ["GMAIL_SEND_EMAIL", "GMAIL_READ_EMAIL"],
99
-},
100
-},
96
+ "ac_yourAuthConfigId",
97
+ options={
98
+ "type": "custom",
99
+ "tool_access_config": {
100
+ "tools_available_for_execution": ["GMAIL_SEND_EMAIL", "GMAIL_READ_EMAIL"],
101
+ },
102
+ },
103
)
102
-
103
-````
104
-
105
-```typescript title="TypeScript SDK"
104
+```
105
+</Tab>
106
+<Tab value="TypeScript">
107
+```typescript
108
import { Composio } from "@composio/core";
109
110
const composio = new Composio();
@@ -117,9 +119,9 @@ await composio.authConfigs.update("ac_yourAuthConfigId", {
119
toolsAvailableForExecution: ["GMAIL_SEND_EMAIL", "GMAIL_READ_EMAIL"],
120
},
121
});
120
-````
121
-
122
-</CodeBlocks>
122
+```
123
+</Tab>
124
+</Tabs>
125
126
## Migration Guide
127
@@ -136,8 +138,9 @@ await composio.authConfigs.update("ac_yourAuthConfigId", {
138
| `tool_access_config` | `"tool_access_config": {"tools_available_for_execution": []}` | `toolAccessConfig: { toolsAvailableForExecution: [] }` |
139
| `scopes` (default) | `"scopes": ""` | `scopes: ""` (via HTTP API) |
140
139
-<CodeBlocks>
140
-```python title="Python SDK - Clear tool restrictions"
141
+<Tabs groupId="language" items={['Python', 'TypeScript']}>
142
+<Tab value="Python">
143
+```python
144
from composio import Composio
145
146
composio = Composio()
@@ -145,18 +148,18 @@ composio = Composio()
148
# Explicitly clear tool restrictions with empty array
149
150
composio.auth_configs.update(
148
-"ac_yourAuthConfigId",
149
-options={
150
-"type": "custom",
151
-"tool_access_config": {
152
-"tools_available_for_execution": [],
153
-},
154
-},
151
+ "ac_yourAuthConfigId",
152
+ options={
153
+ "type": "custom",
154
+ "tool_access_config": {
155
+ "tools_available_for_execution": [],
156
+ },
157
+ },
158
)
156
-
157
-````
158
-
159
-```typescript title="TypeScript SDK - Clear tool restrictions"
159
+```
160
+</Tab>
161
+<Tab value="TypeScript">
162
+```typescript
163
import { Composio } from "@composio/core";
164
165
const composio = new Composio();
@@ -171,9 +174,9 @@ await composio.authConfigs.update("ac_yourAuthConfigId", {
174
toolsAvailableForExecution: [],
175
},
176
});
174
-````
175
-
176
-</CodeBlocks>
177
+```
178
+</Tab>
179
+</Tabs>
180
181
### Raw HTTP API
182
docs/content/changelog/01-20-26-file-modifier-anyof-support.mdx
+24
-16
@@ -19,9 +19,9 @@ date: "2026-01-20"
19
20
The file handling modifiers now properly handle `file_uploadable` and `file_downloadable` properties nested within `anyOf`, `oneOf`, and `allOf` JSON Schema declarations. Previously, only direct child properties (and partial `allOf` support) were detected for file upload/download transformations.
21
22
-<Note>
22
+<Callout type="info">
23
We recommend updating to version `0.5.3` (TypeScript) or `0.10.8` (Python) or later to ensure file uploads and downloads work correctly with tools that use union or intersection types in their schemas.
24
-</Note>
24
+</Callout>
25
26
## What Changed
27
@@ -90,35 +90,43 @@ inputParameters: {
90
91
### TypeScript/JavaScript
92
93
-<CodeBlocks>
94
-```bash title="npm"
93
+<Tabs items={['npm', 'pnpm', 'yarn']}>
94
+<Tab value="npm">
95
+```bash
96
npm update @composio/core@latest
97
```
97
-
98
-```bash title="pnpm"
98
+</Tab>
99
+<Tab value="pnpm">
100
+```bash
101
pnpm update @composio/core@latest
102
```
101
-
102
-```bash title="yarn"
103
+</Tab>
104
+<Tab value="yarn">
105
+```bash
106
yarn upgrade @composio/core@latest
107
```
105
-</CodeBlocks>
108
+</Tab>
109
+</Tabs>
110
111
### Python
112
109
-<CodeBlocks>
110
-```bash title="pip"
113
+<Tabs items={['pip', 'uv', 'poetry']}>
114
+<Tab value="pip">
115
+```bash
116
pip install --upgrade composio
117
```
113
-
114
-```bash title="uv"
118
+</Tab>
119
+<Tab value="uv">
120
+```bash
121
uv pip install --upgrade composio
122
```
117
-
118
-```bash title="poetry"
123
+</Tab>
124
+<Tab value="poetry">
125
+```bash
126
poetry update composio
127
```
121
-</CodeBlocks>
128
+</Tab>
129
+</Tabs>
130
131
## Backward Compatibility
132
docs/content/changelog/01-22-26-experimental-assistive-prompts.mdx
+20
-14
@@ -21,12 +21,13 @@ date: "2026-01-22"
21
22
Tool Router sessions now support experimental configuration for timezone-aware assistive prompts. When you provide a user's timezone, the session returns a contextual assistive prompt that includes timezone-specific guidance.
23
24
-<Warning>
24
+<Callout type="warn">
25
This is an experimental feature. The API may change or be removed in future versions.
26
-</Warning>
26
+</Callout>
27
28
-<CodeBlocks>
29
-```python title="Python SDK"
28
+<Tabs groupId="language" items={['Python', 'TypeScript']}>
29
+<Tab value="Python">
30
+```python
31
from composio import Composio
32
33
composio = Composio()
@@ -45,8 +46,9 @@ session = composio.tool_router.create(
46
if session.experimental:
47
print(session.experimental.assistive_prompt)
48
```
48
-
49
-```typescript title="TypeScript SDK"
49
+</Tab>
50
+<Tab value="TypeScript">
51
+```typescript
52
import { Composio } from "@composio/core";
53
54
const composio = new Composio();
@@ -65,11 +67,12 @@ if (session.experimental) {
67
console.log(session.experimental.assistivePrompt);
68
}
69
```
68
-</CodeBlocks>
70
+</Tab>
71
+</Tabs>
72
70
-<Note>
73
+<Callout type="info">
74
The `experimental` field is only available on sessions created with `create()`. Sessions retrieved with `use()` do not include the experimental data.
72
-</Note>
75
+</Callout>
76
77
### Toolkit Endpoint Method
78
@@ -81,8 +84,9 @@ The toolkit retrieve response now includes `getCurrentUserEndpointMethod` (TypeS
84
85
The `page` parameter in `listActive` / `list_active` for trigger instances has been replaced with `cursor` for cursor-based pagination. There was a bug in earlier APIs which caused `page` param to be ignored, going ahead for pagination please use `cursor` instead.
86
84
-<CodeBlocks>
85
-```python title="Python SDK"
87
+<Tabs groupId="language" items={['Python', 'TypeScript']}>
88
+<Tab value="Python">
89
+```python
90
# Before (deprecated)
91
triggers = composio.triggers.list_active(page=1, limit=10)
92
@@ -90,8 +94,9 @@ triggers = composio.triggers.list_active(page=1, limit=10)
94
triggers = composio.triggers.list_active(cursor="cursor_string", limit=10)
95
# Use response.next_cursor for the next page
96
```
93
-
94
-```typescript title="TypeScript SDK"
97
+</Tab>
98
+<Tab value="TypeScript">
99
+```typescript
100
// Before (deprecated)
101
const triggers = await composio.triggers.listActive({ page: 1, limit: 10 });
102
@@ -99,7 +104,8 @@ const triggers = await composio.triggers.listActive({ page: 1, limit: 10 });
104
const triggers = await composio.triggers.listActive({ cursor: "cursor_string", limit: 10 });
105
// Use response.nextCursor for the next page
106
```
102
-</CodeBlocks>
107
+</Tab>
108
+</Tabs>
109
110
## Impact Summary
111