Skip to content

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

fix(docs): Convert Fern components to Fumadocs components in changelog

Sushmithamallesh3c0de2cead0f
diff --git a/docs/content/changelog/01-08-26-mcp-api-key-enforcement.mdx b/docs/content/changelog/01-08-26-mcp-api-key-enforcement.mdx
index c9632096b..b35fbc1ce 100644
--- a/docs/content/changelog/01-08-26-mcp-api-key-enforcement.mdx
+++ b/docs/content/changelog/01-08-26-mcp-api-key-enforcement.mdx
@@ -7,9 +7,9 @@ date: "2026-01-08"
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.
-<Note>
+<Callout type="info">
**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.
-</Note>
+</Callout>
## What's New
@@ -60,9 +60,7 @@ curl -X POST "https://mcp.composio.dev/{your_mcp_server_url}" \
3. Find the **"Require API Key for MCP"** toggle
4. Enable the toggle
-<Frame>
- <img src="/assets/images/mcp-api-key-toggle.png" alt="MCP API Key Toggle in Project Settings" />
-</Frame>
+![MCP API Key Toggle in Project Settings](/assets/images/mcp-api-key-toggle.png)
### Via API
@@ -87,8 +85,9 @@ curl -X PATCH "https://backend.composio.dev/api/v3/org/project/config" \
### Via Code
-<CodeGroup>
-```python title="Python"
+<Tabs groupId="language" items={['Python', 'TypeScript']}>
+<Tab value="Python">
+```python
import requests
response = requests.patch(
@@ -102,7 +101,9 @@ response = requests.patch(
print(response.json())
```
-```typescript title="TypeScript"
+</Tab>
+<Tab value="TypeScript">
+```typescript
const response = await fetch(
"https://backend.composio.dev/api/v3/org/project/config",
{
@@ -117,7 +118,8 @@ const response = await fetch(
console.log(await response.json());
```
-</CodeGroup>
+</Tab>
+</Tabs>
## When to Use This
diff --git a/docs/content/changelog/01-14-26-auth-config-patch-semantics.mdx b/docs/content/changelog/01-14-26-auth-config-patch-semantics.mdx
index ad5b4df3c..0b253be23 100644
--- a/docs/content/changelog/01-14-26-auth-config-patch-semantics.mdx
+++ b/docs/content/changelog/01-14-26-auth-config-patch-semantics.mdx
@@ -19,9 +19,9 @@ date: "2026-01-14"
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.
-<Warning>
+<Callout type="warn">
**Breaking Change**: If you relied on omitting fields to clear them, you must now explicitly send `null` or `[]`. See [Migration Guide](#migration-guide) below.
-</Warning>
+</Callout>
## What Changed
@@ -32,9 +32,9 @@ The `PATCH /api/v3/auth_configs/{id}` endpoint now implements proper partial upd
| `scopes` (type: default) | Cleared if omitted | Preserved if omitted |
| `restrict_to_following_tools` | Reset to `[]` if omitted | Preserved if omitted |
-<Note>
+<Callout type="info">
**Merge Behavior**: The `credentials` object is merged—send only the fields you want to change, and existing fields are preserved.
-</Note>
+</Callout>
## New Capabilities
@@ -42,8 +42,9 @@ The `PATCH /api/v3/auth_configs/{id}` endpoint now implements proper partial upd
Update just `client_secret` without resending `client_id` or other fields:
-<CodeBlocks>
-```python title="Python SDK"
+<Tabs groupId="language" items={['Python', 'TypeScript']}>
+<Tab value="Python">
+```python
from composio import Composio
composio = Composio()
@@ -51,18 +52,18 @@ composio = Composio()
# Only send the field you want to update - other credentials are preserved
composio.auth_configs.update(
-"ac_yourAuthConfigId",
-options={
-"type": "custom",
-"credentials": {
-"client_secret": "new_rotated_secret",
-},
-},
+ "ac_yourAuthConfigId",
+ options={
+ "type": "custom",
+ "credentials": {
+ "client_secret": "new_rotated_secret",
+ },
+ },
)
-
-````
-
-```typescript title="TypeScript SDK"
+```
+</Tab>
+<Tab value="TypeScript">
+```typescript
import { Composio } from "@composio/core";
const composio = new Composio();
@@ -74,16 +75,17 @@ await composio.authConfigs.update("ac_yourAuthConfigId", {
client_secret: "new_rotated_secret",
},
});
-````
-
-</CodeBlocks>
+```
+</Tab>
+</Tabs>
### Update Tool Restrictions Without Touching Credentials
Previously, this would fail because `credentials` was required. Now it works:
-<CodeBlocks>
-```python title="Python SDK"
+<Tabs groupId="language" items={['Python', 'TypeScript']}>
+<Tab value="Python">
+```python
from composio import Composio
composio = Composio()
@@ -91,18 +93,18 @@ composio = Composio()
# Update tool restrictions - credentials are automatically preserved
composio.auth_configs.update(
-"ac_yourAuthConfigId",
-options={
-"type": "custom",
-"tool_access_config": {
-"tools_available_for_execution": ["GMAIL_SEND_EMAIL", "GMAIL_READ_EMAIL"],
-},
-},
+ "ac_yourAuthConfigId",
+ options={
+ "type": "custom",
+ "tool_access_config": {
+ "tools_available_for_execution": ["GMAIL_SEND_EMAIL", "GMAIL_READ_EMAIL"],
+ },
+ },
)
-
-````
-
-```typescript title="TypeScript SDK"
+```
+</Tab>
+<Tab value="TypeScript">
+```typescript
import { Composio } from "@composio/core";
const composio = new Composio();
@@ -117,9 +119,9 @@ await composio.authConfigs.update("ac_yourAuthConfigId", {
toolsAvailableForExecution: ["GMAIL_SEND_EMAIL", "GMAIL_READ_EMAIL"],
},
});
-````
-
-</CodeBlocks>
+```
+</Tab>
+</Tabs>
## Migration Guide
@@ -136,8 +138,9 @@ await composio.authConfigs.update("ac_yourAuthConfigId", {
| `tool_access_config` | `"tool_access_config": {"tools_available_for_execution": []}` | `toolAccessConfig: { toolsAvailableForExecution: [] }` |
| `scopes` (default) | `"scopes": ""` | `scopes: ""` (via HTTP API) |
-<CodeBlocks>
-```python title="Python SDK - Clear tool restrictions"
+<Tabs groupId="language" items={['Python', 'TypeScript']}>
+<Tab value="Python">
+```python
from composio import Composio
composio = Composio()
@@ -145,18 +148,18 @@ composio = Composio()
# Explicitly clear tool restrictions with empty array
composio.auth_configs.update(
-"ac_yourAuthConfigId",
-options={
-"type": "custom",
-"tool_access_config": {
-"tools_available_for_execution": [],
-},
-},
+ "ac_yourAuthConfigId",
+ options={
+ "type": "custom",
+ "tool_access_config": {
+ "tools_available_for_execution": [],
+ },
+ },
)
-
-````
-
-```typescript title="TypeScript SDK - Clear tool restrictions"
+```
+</Tab>
+<Tab value="TypeScript">
+```typescript
import { Composio } from "@composio/core";
const composio = new Composio();
@@ -171,9 +174,9 @@ await composio.authConfigs.update("ac_yourAuthConfigId", {
toolsAvailableForExecution: [],
},
});
-````
-
-</CodeBlocks>
+```
+</Tab>
+</Tabs>
### Raw HTTP API
diff --git a/docs/content/changelog/01-20-26-file-modifier-anyof-support.mdx b/docs/content/changelog/01-20-26-file-modifier-anyof-support.mdx
index dbc0ab594..7dfe683e9 100644
--- a/docs/content/changelog/01-20-26-file-modifier-anyof-support.mdx
+++ b/docs/content/changelog/01-20-26-file-modifier-anyof-support.mdx
@@ -19,9 +19,9 @@ date: "2026-01-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.
-<Note>
+<Callout type="info">
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.
-</Note>
+</Callout>
## What Changed
@@ -90,35 +90,43 @@ inputParameters: {
### TypeScript/JavaScript
-<CodeBlocks>
-```bash title="npm"
+<Tabs items={['npm', 'pnpm', 'yarn']}>
+<Tab value="npm">
+```bash
npm update @composio/core@latest
```
-
-```bash title="pnpm"
+</Tab>
+<Tab value="pnpm">
+```bash
pnpm update @composio/core@latest
```
-
-```bash title="yarn"
+</Tab>
+<Tab value="yarn">
+```bash
yarn upgrade @composio/core@latest
```
-</CodeBlocks>
+</Tab>
+</Tabs>
### Python
-<CodeBlocks>
-```bash title="pip"
+<Tabs items={['pip', 'uv', 'poetry']}>
+<Tab value="pip">
+```bash
pip install --upgrade composio
```
-
-```bash title="uv"
+</Tab>
+<Tab value="uv">
+```bash
uv pip install --upgrade composio
```
-
-```bash title="poetry"
+</Tab>
+<Tab value="poetry">
+```bash
poetry update composio
```
-</CodeBlocks>
+</Tab>
+</Tabs>
## Backward Compatibility
diff --git a/docs/content/changelog/01-22-26-experimental-assistive-prompts.mdx b/docs/content/changelog/01-22-26-experimental-assistive-prompts.mdx
index 722451022..6fabd36b0 100644
--- a/docs/content/changelog/01-22-26-experimental-assistive-prompts.mdx
+++ b/docs/content/changelog/01-22-26-experimental-assistive-prompts.mdx
@@ -21,12 +21,13 @@ date: "2026-01-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.
-<Warning>
+<Callout type="warn">
This is an experimental feature. The API may change or be removed in future versions.
-</Warning>
+</Callout>
-<CodeBlocks>
-```python title="Python SDK"
+<Tabs groupId="language" items={['Python', 'TypeScript']}>
+<Tab value="Python">
+```python
from composio import Composio
composio = Composio()
@@ -45,8 +46,9 @@ session = composio.tool_router.create(
if session.experimental:
print(session.experimental.assistive_prompt)
```
-
-```typescript title="TypeScript SDK"
+</Tab>
+<Tab value="TypeScript">
+```typescript
import { Composio } from "@composio/core";
const composio = new Composio();
@@ -65,11 +67,12 @@ if (session.experimental) {
console.log(session.experimental.assistivePrompt);
}
```
-</CodeBlocks>
+</Tab>
+</Tabs>
-<Note>
+<Callout type="info">
The `experimental` field is only available on sessions created with `create()`. Sessions retrieved with `use()` do not include the experimental data.
-</Note>
+</Callout>
### Toolkit Endpoint Method
@@ -81,8 +84,9 @@ The toolkit retrieve response now includes `getCurrentUserEndpointMethod` (TypeS
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.
-<CodeBlocks>
-```python title="Python SDK"
+<Tabs groupId="language" items={['Python', 'TypeScript']}>
+<Tab value="Python">
+```python
# Before (deprecated)
triggers = composio.triggers.list_active(page=1, limit=10)
@@ -90,8 +94,9 @@ triggers = composio.triggers.list_active(page=1, limit=10)
triggers = composio.triggers.list_active(cursor="cursor_string", limit=10)
# Use response.next_cursor for the next page
```
-
-```typescript title="TypeScript SDK"
+</Tab>
+<Tab value="TypeScript">
+```typescript
// Before (deprecated)
const triggers = await composio.triggers.listActive({ page: 1, limit: 10 });
@@ -99,7 +104,8 @@ const triggers = await composio.triggers.listActive({ page: 1, limit: 10 });
const triggers = await composio.triggers.listActive({ cursor: "cursor_string", limit: 10 });
// Use response.nextCursor for the next page
```
-</CodeBlocks>
+</Tab>
+</Tabs>
## Impact Summary