@devries-cameron20 / composio-1 / commits / 6aac077b1
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.

docs: rename Custom Tools and Toolkits to Local Tools and Toolkits (#5213)

## Summary Asked for: rename "Custom Tools and Toolkits" to "Local Tools and Toolkits" in the docs, change its URL to match, redirect the old URL, and move that page and Custom MCP into the Tools & Toolkits section. - **Rename.** The page title is now **Local Tools and Toolkits**. Prose on the page and link text across the docs now say "local tools/toolkits", which matches the `LOCAL_` slug prefix the SDK already adds. A new line says these were previously called custom tools. SDK option names (`customTools` / `custom_tools`, `customToolkits` / `custom_toolkits`) and code samples are unchanged. - **Sidebar.** Under Build → **Toolkits & Tools**, the Platform sidebar now lists Toolkits, Tool tags, Instant tools, **Local Tools and Toolkits**, and **Custom MCP**. Customize → **Extend sessions** keeps Proxy execute and Shared connections. It's now an explicit group, so the two moved pages don't show up twice. - **New URL.** The page moved from `/docs/extending-sessions/custom-tools-and-toolkits` to `/docs/extending-sessions/local-tools-and-toolkits`. The old URL and its `.md`/`.mdx` variants permanently redirect to the new page. Existing redirects (`/docs/custom-tools`, `/custom-tools/*`, and others) now point straight to the new URL, so there are no redirect chains. All in-repo links, including two older changelog entries, are updated. Custom MCP keeps its URL. - **Anchor.** The `#preloading-custom-tools` section link became `#preloading-local-tools`. The one in-repo link to it is updated. - **Other pages.** Examples (custom-tools, iMessage), the eve provider page, how-composio-works, configuring-sessions, the migration guide, and the glossary (now a **Local Tool** entry) say "local tools" too. - **Still says "custom" on purpose:** - The SDK option names: `customTools` / `custom_tools`, `customToolkits` / `custom_toolkits`, `session.customTools()`. Renaming them is an SDK change. - The generated SDK reference. - Custom MCP, whose server-side toolkits really are "custom toolkits" (`CUSTOM_*` slugs, `?type=custom`). - The KB guides imported from support-knowledge. - The `/examples/custom-tools` and `managed-auth-for-custom-tools` URLs. - Search keywords. - **Not updated:** `docs/kb/semantic-index.json` still lists the old URL. The KB refresh job regenerates that file, and the redirect covers it until then. ## Verification - `bun test tests/static/`: 825 pass. 1 fail, an unrelated support-knowledge git-remote check that fails in this environment. - `bun run lint:links`: 0 errors. `oxlint lib/home-navigation.ts`: clean. - On the local dev server, the old URL and `/docs/custom-tools` return 308 to the new URL, which returns 200. `custom-tools-and-toolkits.md` redirects to `local-tools-and-toolkits.md`. - On the local dev server, the sidebar shows Local Tools and Toolkits and Custom MCP under Toolkits & Tools, and the page breadcrumb reads "Toolkits & Tools". 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Palash Kala [zen] <palash@composio.dev> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: jkomyno <alberto@composio.dev>

composio-zen[bot] committed Nov 9, 2026 at 15:06 UTC 6aac077b1ef4243f111ddb2c670267f5f21440d9
24 files changed +121 -95
docs/agent/instructions/context.md
+2 -2
@@ -14,7 +14,7 @@ This is your always-on map of Composio's concepts and the canonical page for eac
14 - **Toolkit** — a collection of related tools for a service (e.g. `github`, `gmail`). A **tool** is one action, named `{TOOLKIT}_{ACTION}` (e.g. `GITHUB_CREATE_ISSUE`). Every toolkit is discoverable by default; restrict with the `toolkits` config. → [Configuring sessions](/docs/configuring-sessions)
15 - **Meta tools** — the fixed set every session exposes (`COMPOSIO_SEARCH_TOOLS`, `COMPOSIO_GET_TOOL_SCHEMAS`, `COMPOSIO_MANAGE_CONNECTIONS`, `COMPOSIO_MULTI_EXECUTE_TOOL`, `COMPOSIO_REMOTE_WORKBENCH`, `COMPOSIO_REMOTE_BASH_TOOL`). → [Meta tools reference](/toolkits/meta-tools)
16 - **Providers** — adapter packages that format Composio tools for a framework (OpenAI, Anthropic, Vercel AI SDK, LangChain, Mastra, Pi, …). → [Providers](/docs/providers)
17 -- **Is a toolkit / integration supported?** Composio has 1000+ toolkits, and `search_docs` indexes the catalog. A matching `/toolkits/<slug>` result means **yes, it's supported** — answer from the returned content when sufficient, call `read_doc` only for more details, and point the user at [the toolkits directory](/toolkits). If nothing matches, it isn't a built-in toolkit; suggest [proxy execute](/docs/extending-sessions/proxy-execute) or a [custom tool](/docs/extending-sessions/custom-tools-and-toolkits) for an API you already have.
17 +- **Is a toolkit / integration supported?** Composio has 1000+ toolkits, and `search_docs` indexes the catalog. A matching `/toolkits/<slug>` result means **yes, it's supported** — answer from the returned content when sufficient, call `read_doc` only for more details, and point the user at [the toolkits directory](/toolkits). If nothing matches, it isn't a built-in toolkit; suggest [proxy execute](/docs/extending-sessions/proxy-execute) or a [local tool](/docs/extending-sessions/local-tools-and-toolkits) for an API you already have.
18
19 ## Authentication
20
@@ -38,7 +38,7 @@ This is your always-on map of Composio's concepts and the canonical page for eac
38 ## Extending sessions
39
40 - **Sandbox** (previously "workbench") — a persistent Python environment at `/mnt/files/` for bulk operations and large responses; files via `session.experimental.files`. → [Sandbox](/docs/sandbox)
41 -- **Custom tools and toolkits** — define in-process tools that run alongside Composio tools. → [Custom tools and toolkits](/docs/extending-sessions/custom-tools-and-toolkits)
41 +- **Local tools and toolkits** — define in-process tools that run alongside Composio tools. → [Local tools and toolkits](/docs/extending-sessions/local-tools-and-toolkits)
42 - **Proxy execute** — call any toolkit HTTP endpoint with `session.proxyExecute(...)` and let Composio inject auth. → [Proxy execute](/docs/extending-sessions/proxy-execute)
43
44 ## Platform API (reference only)
docs/content/changelog/05-07-26-toolrouter-preload-direct-tools.mdx
+1 -1
@@ -210,5 +210,5 @@ console.log(tools.map((tool) => tool.name));
210
211 See [Preloading tools](/docs/configuring-sessions#preloading-tools),
212 [Direct tools preset](/docs/configuring-sessions#direct-tools-preset), and
213 -[Preloading custom tools](/docs/extending-sessions/custom-tools-and-toolkits#preloading-custom-tools)
213 +[Preloading custom tools](/docs/extending-sessions/local-tools-and-toolkits#preloading-local-tools)
214 for Python examples and full guidance.
docs/content/changelog/05-08-26-session-use-update-connected-accounts.mdx
+1 -1
@@ -41,7 +41,7 @@ const tools = await session.tools();
41 </Tab>
42 </Tabs>
43
44 -Custom tools can also be attached when reusing a session. See [Reusing a session](/docs/how-composio-works#how-sessions-behave) and [Custom tools](/docs/extending-sessions/custom-tools-and-toolkits#reusing-a-session-with-custom-tools).
44 +Custom tools can also be attached when reusing a session. See [Reusing a session](/docs/how-composio-works#how-sessions-behave) and [Custom tools](/docs/extending-sessions/local-tools-and-toolkits#reusing-a-session-with-local-tools).
45
46 ### Update session config with `session.update()`
47
docs/content/docs/auth-configuration/connected-accounts.mdx
+1 -1
@@ -101,7 +101,7 @@ curl -X GET https://backend.composio.dev/api/v3.1/connected_accounts/ca_123 \
101
102 Connected-account responses describe the authentication state. Sensitive credential fields in `account.state.val` are [redacted by default](#credential-masking), for both Composio-managed and custom auth configs. This object is not a source of usable provider tokens for your own tools.
103
104 -To call a provider API, use [Proxy Execute](/docs/extending-sessions/proxy-execute), which injects credentials server-side. For custom business logic, use [session extension tools](/docs/extending-sessions/custom-tools-and-toolkits). See [Token custody architecture](/docs/security/token-custody) for the boundaries between your application, Composio, and the provider.
104 +To call a provider API, use [Proxy Execute](/docs/extending-sessions/proxy-execute), which injects credentials server-side. For custom business logic, use [session extension tools](/docs/extending-sessions/local-tools-and-toolkits). See [Token custody architecture](/docs/security/token-custody) for the boundaries between your application, Composio, and the provider.
105
106 ## Refresh credentials
107
docs/content/docs/authentication/managed-auth-for-custom-tools.mdx
+1 -1
@@ -153,6 +153,6 @@ This is managed authentication for your own tools, not a token-export service. C
153
154 <Cards>
155 <Card title="Proxy Execute" href="/docs/extending-sessions/proxy-execute" description="Call provider endpoints from a session and understand proxy restrictions." />
156 - <Card title="Custom tools and toolkits" href="/docs/extending-sessions/custom-tools-and-toolkits" description="Optionally expose your custom business logic through experimental session extension tools." />
156 + <Card title="Local tools and toolkits" href="/docs/extending-sessions/local-tools-and-toolkits" description="Optionally expose your custom business logic through experimental session extension tools." />
157 <Card title="Token custody architecture" href="/docs/security/token-custody" description="Review credential redaction, OAuth app ownership, and deployment boundaries." />
158 </Cards>
docs/content/docs/configuring-sessions.mdx
+6 -6
@@ -32,7 +32,7 @@ curl -X POST https://backend.composio.dev/api/v3.1/tool_router/session \
32
33 By default, a session has access to every toolkit in the Composio catalog. Your agent can discover and use any of them through `COMPOSIO_SEARCH_TOOLS`. Use the options below to restrict or customize what's available.
34
35 -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).
35 +You can also attach local tools and local toolkits that run in-process alongside Composio tools. See [Local tools and toolkits](/docs/extending-sessions/local-tools-and-toolkits).
36
37 <Callout type="warn">
38 Both SDKs pass product and runtime identity through the API client's `identity` option. If you configure custom default or request headers, remove identity headers such as `x-source`, `x-framework`, `x-sdk-version`, and `x-client-*`. The client rejects attempts to override them.
@@ -170,7 +170,7 @@ An explicit empty allowlist means no app toolkits at all. Omitting `toolkits` ke
170 | `{ enable: [] }` | No app toolkit is listed, searchable, executable, or served over MCP |
171 | `{ disable: [] }` | Every toolkit in the catalog is available |
172
173 -Use an empty allowlist when a session should only run [custom tools](/docs/extending-sessions/custom-tools-and-toolkits) or session helpers. Meta tools such as `COMPOSIO_SEARCH_TOOLS`, connection management, and the sandbox keep their own enablement, so `session.tools()` can still return them.
173 +Use an empty allowlist when a session should only run [local tools](/docs/extending-sessions/local-tools-and-toolkits) or session helpers. Meta tools such as `COMPOSIO_SEARCH_TOOLS`, connection management, and the sandbox keep their own enablement, so `session.tools()` can still return them.
174
175 <Tabs groupId="language" items={['Python', 'TypeScript', 'API']} persist>
176 <Tab value="Python">
@@ -638,7 +638,7 @@ Keep the preloaded set small, generally fewer than 20 tools, to avoid context bl
638 <Callout type="info">
639 Requires `@composio/core` ≥ `0.9.0` (TypeScript) or `composio` ≥ `0.13.0`
640 (Python). Older SDKs do not support `preload.tools`,
641 -`sessionPreset` / `session_preset`, or custom-tool `preload`.
641 +`sessionPreset` / `session_preset`, or local-tool `preload`.
642 </Callout>
643
644 <Callout type="info">
@@ -718,7 +718,7 @@ curl -s -X GET https://backend.composio.dev/api/v3.1/tool_router/session/$SESSIO
718 </Tab>
719 </Tabs>
720
721 -For SDK custom tools, set `preload: true` on the custom tool or custom toolkit. See [Preloading custom tools](/docs/extending-sessions/custom-tools-and-toolkits#preloading-custom-tools).
721 +For SDK local tools, set `preload: true` on the local tool or local toolkit. See [Preloading local tools](/docs/extending-sessions/local-tools-and-toolkits#preloading-local-tools).
722
723 To preload every tool allowed by the session filters, use the `preload.tools = "all"` shortcut (`preload={"tools": "all"}` in Python, `preload: { tools: "all" }` in TypeScript). The `all` shorthand works for both Composio tools and SDK custom tools.
724
@@ -1161,7 +1161,7 @@ curl -X PATCH https://backend.composio.dev/api/v3.1/tool_router/session/$SESSION
1161
1162 Both blocks are on by default. `search` controls the session's search helper, so disabling it leaves the agent with the tools you preloaded. `execute.enableMultiExecute` controls whether the agent can run several tool calls in one request. `manageConnections.enableConnectionRemoval` is update-only as well, and controls whether the session exposes the connection-removal tool.
1163
1164 -The `experimental` block on update holds server-side session settings: `permissions`, `linkUrlOverwrite`, `fastMode`, `submitFeedback`, and `sessionConfigId`. `sessionConfigId` applies a [saved Session config](/docs/session-configs#applying-a-config-to-an-existing-session) and can't be combined with `toolkits`, `tools`, or `tags`. The `experimental` block on update is a different field from the `experimental` option on `create()`, which holds [custom tools and toolkits](/docs/extending-sessions/custom-tools-and-toolkits) that run in your process, so `experimental: null` on an update leaves those alone.
1164 +The `experimental` block on update holds server-side session settings: `permissions`, `linkUrlOverwrite`, `fastMode`, `submitFeedback`, and `sessionConfigId`. `sessionConfigId` applies a [saved Session config](/docs/session-configs#applying-a-config-to-an-existing-session) and can't be combined with `toolkits`, `tools`, or `tags`. The `experimental` block on update is a different field from the `experimental` option on `create()`, which holds [local tools and toolkits](/docs/extending-sessions/local-tools-and-toolkits) that run in your process, so `experimental: null` on an update leaves those alone.
1165
1166 ### Multi-account mode after an update
1167
@@ -1359,7 +1359,7 @@ The exported `ToolRouterSessionMetaToolSlug` type lists the accepted slugs. The
1359
1360 In TypeScript, the third argument holds input-response options: `session.executeMeta(slug, args, { inputResponses, requestState })`. Request options belong in the fourth argument. To pass only request options, use `session.executeMeta(slug, args, undefined, requestOptions)`.
1361
1362 -`COMPOSIO_MULTI_EXECUTE_TOOL` calls through this method run on the backend. Custom tools named in those calls are not executed in your process.
1362 +`COMPOSIO_MULTI_EXECUTE_TOOL` calls through this method run on the backend. Local tools named in those calls are not executed in your process.
1363
1364 ### authorize()
1365
docs/content/docs/extending-sessions/custom-mcp.mdx
+2 -2
@@ -11,7 +11,7 @@ Custom MCP lets you add your own remote MCP server to Composio and use its tools
11 Custom MCP is experimental. The APIs may change.
12 </Callout>
13
14 -This is different from [Custom Tools and Toolkits](/docs/extending-sessions/custom-tools-and-toolkits), which run inside your app. A Custom MCP server runs on its own public HTTPS URL.
14 +This is different from [Local Tools and Toolkits](/docs/extending-sessions/local-tools-and-toolkits), which run inside your app. A Custom MCP server runs on its own public HTTPS URL.
15
16 ## How it works
17
@@ -413,7 +413,7 @@ curl -X POST https://backend.composio.dev/api/v3.1/tool_router/session \
413
414 <Cards>
415 <Card title="Using sessions via MCP" href="/docs/sessions-via-mcp" description="Connect an MCP client to a Composio-hosted session" />
416 -<Card title="Custom Tools and Toolkits" href="/docs/extending-sessions/custom-tools-and-toolkits" description="Run your own tools inside your application process" />
416 +<Card title="Local Tools and Toolkits" href="/docs/extending-sessions/local-tools-and-toolkits" description="Run your own tools inside your application process" />
417 <Card title="Configuring Sessions" href="/docs/configuring-sessions" description="Configure toolkit and tool filtering" />
418 <Card title="Managing Multiple Connected Accounts" href="/docs/authentication/managing-multiple-connected-accounts" description="Select a connected account explicitly" />
419 </Cards>
docs/content/docs/extending-sessions/local-tools-and-toolkits.mdx renamed
+32 -30
@@ -1,7 +1,7 @@
1 ---
2 -title: Custom Tools and Toolkits
2 +title: Local Tools and Toolkits
3 description: Define local tools that run in-process alongside remote Composio tools
4 -keywords: [custom tools, custom toolkits, experimental, local tools, proxy execute]
4 +keywords: [local tools, local toolkits, custom tools, custom toolkits, experimental, proxy execute]
5 experimental: true
6 ---
7
@@ -9,16 +9,18 @@ For a complete agent that combines an internal lookup with a public API, follow
9
10 If you already have your own tool definitions, start with [Managed authentication for your own tools](/docs/authentication/managed-auth-for-custom-tools). You can call the authenticated proxy from your code without adopting the experimental session-extension API below.
11
12 -Custom tools let you define tools that run in-process alongside remote Composio tools within a session. You have three patterns:
12 +Local tools let you define tools that run in-process alongside remote Composio tools within a session. You have three patterns:
13
14 - **Standalone tools**: internal app logic that doesn't need Composio auth (DB lookups, in-memory data, business rules).
15 - **Extension tools**: wrap a Composio toolkit's API with custom business logic via `extendsToolkit` / `extends_toolkit`, using `ctx.proxyExecute()` / `ctx.proxy_execute()` for authenticated requests.
16 -- **Custom toolkits**: group related standalone tools under a namespace.
16 +- **Local toolkits**: group related standalone tools under a namespace.
17 +
18 +Local tools were previously called custom tools. The SDK options keep their names: `customTools` / `custom_tools` and `customToolkits` / `custom_toolkits`.
19
20 <IntegrationTabs tabs={[
21 { value: "standalone", label: "Standalone Tool" },
22 { value: "extension", label: "Extension Tool" },
21 - { value: "toolkit", label: "Custom Toolkit" },
23 + { value: "toolkit", label: "Local Toolkit" },
24 ]}>
25
26 <IntegrationContent value="standalone">
@@ -63,7 +65,7 @@ const composio = new Composio({ apiKey: "your_api_key" });
65
66 A standalone tool handles internal app logic that doesn't need Composio auth. `ctx.userId` identifies which user's session is running.
67
66 -{/* code-example: no-api reason="custom tool handlers are defined and run in-process in the SDK" */}
68 +{/* code-example: no-api reason="local tool handlers are defined and run in-process in the SDK" */}
69 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
70 <Tab value="Python">
71 ```python
@@ -122,7 +124,7 @@ const getUserProfile = experimental_createTool("GET_USER_PROFILE", {
124 <Step>
125 **Bind to a session**
126
125 -Pass custom tools via the `experimental` option. `session.tools()` returns both remote Composio tools and your custom tools.
127 +Pass local tools via the `experimental` option. `session.tools()` returns both remote Composio tools and your local tools.
128
129 {/* code-example: no-api reason="binding custom tools needs the SDK to serialize their schemas and run their handlers locally" */}
130 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
@@ -292,7 +294,7 @@ const sendPromoEmail = experimental_createTool("SEND_PROMO_EMAIL", {
294 <Step>
295 **Bind to a session**
296
295 -Pass custom tools via the `experimental` option. Extension tools inherit auth from the toolkit specified in `extendsToolkit`.
297 +Pass local tools via the `experimental` option. Extension tools inherit auth from the toolkit specified in `extendsToolkit`.
298
299 {/* code-example: no-api reason="binding custom tools needs the SDK to serialize their schemas and run their handlers locally" */}
300 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
@@ -377,9 +379,9 @@ const composio = new Composio({ apiKey: "your_api_key" });
379 <Step>
380 **Create the toolkit**
381
380 -A custom toolkit groups related standalone tools under a namespace. Tools inside a toolkit cannot use `extendsToolkit`.
382 +A local toolkit groups related standalone tools under a namespace. Tools inside a toolkit cannot use `extendsToolkit`.
383
382 -{/* code-example: no-api reason="custom toolkits and their tool handlers are defined in-process in the SDK" */}
384 +{/* code-example: no-api reason="local toolkits and their tool handlers are defined in-process in the SDK" */}
385 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
386 <Tab value="Python">
387 ```python
@@ -442,7 +444,7 @@ const userManagement = experimental_createToolkit("USER_MANAGEMENT", {
444 <Step>
445 **Bind to a session**
446
445 -Pass custom toolkits via the `experimental` option. `session.tools()` returns both remote Composio tools and your custom toolkit's tools.
447 +Pass local toolkits via the `experimental` option. `session.tools()` returns both remote Composio tools and your local toolkit's tools.
448
449 {/* code-example: no-api reason="binding custom toolkits needs the SDK to serialize their schemas and run their handlers locally" */}
450 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
@@ -487,14 +489,14 @@ const tools = await session.tools();
489
490 </IntegrationTabs>
491
490 -## Preloading custom tools
492 +## Preloading local tools
493
492 -Custom tools are searchable by default. Set `preload: true` / `preload=True` on a
493 -custom tool when it should be returned directly from `session.tools()`. Toolkit
494 +Local tools are searchable by default. Set `preload: true` / `preload=True` on a
495 +local tool when it should be returned directly from `session.tools()`. Toolkit
496 preload applies to all tools in that toolkit; set `preload: false` /
497 `preload=False` on one tool to opt it out.
498
497 -{/* code-example: no-api reason="preload is a property of SDK-defined custom tools whose handlers run in-process" */}
499 +{/* code-example: no-api reason="preload is a property of SDK-defined local tools whose handlers run in-process" */}
500 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
501 <Tab value="Python">
502 ```python
@@ -571,22 +573,22 @@ console.log(tools.map((tool) => tool.name));
573
574 ## Meta tools integration
575
574 -Custom tools work automatically with Composio's meta tools:
576 +Local tools work automatically with Composio's meta tools:
577
578 | Meta tool | Behavior |
579 |-----------|----------|
578 -| `COMPOSIO_SEARCH_TOOLS` | Includes custom tools in search results, with slight priority for tools that don't require auth |
579 -| `COMPOSIO_GET_TOOL_SCHEMAS` | Returns schemas for custom tools alongside remote tools |
580 -| `COMPOSIO_MULTI_EXECUTE_TOOL` | Runs custom tools in-process while remote tools go to the backend, merging results transparently |
580 +| `COMPOSIO_SEARCH_TOOLS` | Includes local tools in search results, with slight priority for tools that don't require auth |
581 +| `COMPOSIO_GET_TOOL_SCHEMAS` | Returns schemas for local tools alongside remote tools |
582 +| `COMPOSIO_MULTI_EXECUTE_TOOL` | Runs local tools in-process while remote tools go to the backend, merging results transparently |
583 | `COMPOSIO_MANAGE_CONNECTIONS` | Handles auth for extension tools. If a tool extends `gmail`, the agent can prompt the user to connect Gmail |
584
585 <Callout type="info">
584 -Custom tools are not supported in the sandbox.
586 +Local tools are not supported in the sandbox.
587 </Callout>
588
589 ## Context object (`ctx`)
590
589 -Every custom tool's `execute` function receives `(input, ctx)`. Use `ctx` to access the current user, make authenticated API requests, or call other Composio tools.
591 +Every local tool's `execute` function receives `(input, ctx)`. Use `ctx` to access the current user, make authenticated API requests, or call other Composio tools.
592
593 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
594 <Tab value="Python">
@@ -595,7 +597,7 @@ Every custom tool's `execute` function receives `(input, ctx)`. Use `ctx` to acc
597 |-------------------|-------------|
598 | `ctx.user_id` | The userID for the current session |
599 | `ctx.proxy_execute(toolkit, endpoint, method, body=None, parameters=[])` | Make an authenticated HTTP request via Composio's auth layer |
598 -| `ctx.execute(tool_slug, arguments)` | Execute any Composio native tool from within your custom tool |
600 +| `ctx.execute(tool_slug, arguments)` | Execute any Composio native tool from within your local tool |
601
602 </Tab>
603 <Tab value="TypeScript">
@@ -604,7 +606,7 @@ Every custom tool's `execute` function receives `(input, ctx)`. Use `ctx` to acc
606 |-------------------|-------------|
607 | `ctx.userId` | The userID for the current session |
608 | `ctx.proxyExecute({ toolkit, endpoint, method, body?, parameters? })` | Make an authenticated HTTP request via Composio's auth layer |
607 -| `ctx.execute(toolSlug, args)` | Execute any Composio native tool from within your custom tool |
609 +| `ctx.execute(toolSlug, args)` | Execute any Composio native tool from within your local tool |
610
611 </Tab>
612 </Tabs>
@@ -635,11 +637,11 @@ const customToolkits = session.customToolkits();
637 </Tab>
638 </Tabs>
639
638 -## Reusing a session with custom tools
640 +## Reusing a session with local tools
641
640 -When [reusing a session](/docs/how-composio-works#how-sessions-behave) via `composio.use()`, you can attach custom tools at the same time:
642 +When [reusing a session](/docs/how-composio-works#how-sessions-behave) via `composio.use()`, you can attach local tools at the same time:
643
642 -{/* code-example: no-api reason="attaching custom tools on use() needs the SDK to run their handlers locally" */}
644 +{/* code-example: no-api reason="attaching local tools on use() needs the SDK to run their handlers locally" */}
645 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
646 <Tab value="Python">
647 ```python
@@ -671,9 +673,9 @@ const session = await composio.use("session_id", {
673
674 ## Programmatic execution
675
674 -Use `session.execute()` to run custom tools directly, outside of an agent loop. Custom tools execute in-process; remote tools are sent to the backend automatically.
676 +Use `session.execute()` to run local tools directly, outside of an agent loop. Local tools execute in-process; remote tools are sent to the backend automatically.
677
676 -{/* code-example: no-api reason="custom tools execute in-process in the SDK, not on the backend" */}
678 +{/* code-example: no-api reason="local tools execute in-process in the SDK, not on the backend" */}
679 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
680 <Tab value="Python">
681 ```python
@@ -716,8 +718,8 @@ Slugs exposed to the agent are automatically prefixed with `LOCAL_` and the tool
718
719 Your slugs cannot start with `LOCAL_`. This prefix is reserved.
720
719 -Use the final `LOCAL_*` slug when you call a custom tool directly. The original slug still works
720 -when it identifies exactly one local tool. If two custom toolkits both define `SEARCH`, call
721 +Use the final `LOCAL_*` slug when you call a local tool directly. The original slug still works
722 +when it identifies exactly one local tool. If two local toolkits both define `SEARCH`, call
723 `LOCAL_CATALOG_SEARCH` or `LOCAL_SUPPORT_SEARCH`. Calling `SEARCH` directly raises an error with the
724 qualified slugs instead of choosing one toolkit silently.
725
docs/content/docs/extending-sessions/meta.json
+1 -1
@@ -3,7 +3,7 @@
3 "defaultOpen": false,
4 "pages": [
5 "proxy-execute",
6 - "custom-tools-and-toolkits",
6 + "local-tools-and-toolkits",
7 "shared-connections",
8 "custom-mcp"
9 ]
docs/content/docs/extending-sessions/proxy-execute.mdx
+1 -1
@@ -279,4 +279,4 @@ Composio sends a proxied call exactly once. A timeout, a connection error, or a
279
280 ## Next
281
282 -<Card icon={<Blocks />} title="Custom tools and toolkits" href="/docs/extending-sessions/custom-tools-and-toolkits" description="Define in-process tools and toolkits that run alongside Composio tools" />
282 +<Card icon={<Blocks />} title="Local tools and toolkits" href="/docs/extending-sessions/local-tools-and-toolkits" description="Define in-process tools and toolkits that run alongside Composio tools" />
docs/content/docs/how-composio-works.mdx
+3 -3
@@ -104,7 +104,7 @@ A **tool** is an individual action your agent can execute. Each tool has an inpu
104
105 See [Toolkits](/docs/toolkits) for how tools are grouped, discovered, and used with connected accounts.
106
107 -Every toolkit in the catalog is discoverable by default. Create a session without a `toolkits` parameter and the agent can find any of them at runtime. To restrict the set, pass `toolkits` when you create the session. See [Enable and disable toolkits](/docs/configuring-sessions). You can also bind local, in-process tools to a session with the experimental [custom tools and toolkits](/docs/extending-sessions/custom-tools-and-toolkits) API.
107 +Every toolkit in the catalog is discoverable by default. Create a session without a `toolkits` parameter and the agent can find any of them at runtime. To restrict the set, pass `toolkits` when you create the session. See [Enable and disable toolkits](/docs/configuring-sessions). You can also bind local, in-process tools to a session with the experimental [local tools and toolkits](/docs/extending-sessions/local-tools-and-toolkits) API.
108
109 ### Meta tools
110
@@ -166,7 +166,7 @@ Do not execute session tools with `tools.execute()`, or by passing a user ID to
166 | --- | --- | --- |
167 | `data` | `data` | The tool-specific output. |
168 | `error` | `error` | Error text, or `null` (`None` in Python). A failed execution can have no error text. |
169 -| `logId` | `log_id` | The execution log ID. Local custom tools return an empty string. |
169 +| `logId` | `log_id` | The execution log ID. Local tools return an empty string. |
170 | `resultType` | `result_type` | `completed` if execution succeeded, or `failed` if it failed. |
171
172 The result can also include `instantCharge` (`instant_charge` in Python) when you enable [Instant usage charge reporting](/docs/instant-tools#report-charges-and-use-instant-tools).
@@ -181,7 +181,7 @@ If you pass a custom TypeScript `ToolCallSession` to a provider, its `execute()`
181
182 A session tool can request user input, such as an approval, before it runs. In Python, catch `ToolInputRequiredError` from `composio.exceptions`. In TypeScript, catch `ComposioToolInputRequiredError` from `@composio/core`. The error carries the questions on `input_requests` / `inputRequests` and opaque continuation state on `request_state` / `requestState`.
183
184 -This also applies to provider-wrapped session tools, `session.proxy_execute()` / `session.proxyExecute()`, and the session execution helpers passed to custom tools. Present the questions to your user rather than treating the error as an empty tool result.
184 +This also applies to provider-wrapped session tools, `session.proxy_execute()` / `session.proxyExecute()`, and the session execution helpers passed to local tools. Present the questions to your user rather than treating the error as an empty tool result.
185
186 <Callout type="warn">
187 An input-required call has not executed and is not retried. To resume `session.execute()` or `session.executeMeta()` in TypeScript, repeat the call with `inputResponses` and `requestState`. In Python, repeat `session.execute()` or `session.execute_meta()` with `input_responses` and `request_state`. Wait for the person's answers and forward decline and cancel responses unchanged. Keep the continuation state unchanged; it is excluded from logs and serialized error output, so read it directly from the error object.
docs/content/docs/migration-guide/new-sdk.mdx
+4 -4
@@ -620,11 +620,11 @@ const result_2 = await composio.tools.execute(
620 </Tab>
621 </Tabs>
622
623 -### Custom Tools
623 +### Local tools
624
625 -Custom tools are now session-scoped. Define local tools with the experimental custom-tools API and attach them when creating or reusing a session.
625 +Custom tools are now called local tools, and they are session-scoped. Define them with the experimental local tools API and attach them when creating or reusing a session.
626
627 -{/* code-example: no-api reason="custom tool handlers are defined and run in-process in the SDK" */}
627 +{/* code-example: no-api reason="local tool handlers are defined and run in-process in the SDK" */}
628 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
629 <Tab value="Python">
630 ```python
@@ -688,7 +688,7 @@ const session = await composio.create("default", {
688 </Tab>
689 </Tabs>
690
691 -For more information, see [Custom Tools and Toolkits](/docs/extending-sessions/custom-tools-and-toolkits).
691 +For more information, see [Local Tools and Toolkits](/docs/extending-sessions/local-tools-and-toolkits).
692
693 ### Auth configs (formerly integrations)
694
docs/content/docs/providers/eve.mdx
+2 -2
@@ -97,7 +97,7 @@ export default defineComposioTools(session);
97 </Step>
98 </Steps>
99
100 -Your agent now has the Tool Router meta-tools (`COMPOSIO_SEARCH_TOOLS`, `COMPOSIO_MULTI_EXECUTE_TOOL`, `COMPOSIO_MANAGE_CONNECTIONS`) plus any preloaded custom toolkits, with auth handled in chat.
100 +Your agent now has the Tool Router meta-tools (`COMPOSIO_SEARCH_TOOLS`, `COMPOSIO_MULTI_EXECUTE_TOOL`, `COMPOSIO_MANAGE_CONNECTIONS`) plus any preloaded local toolkits, with auth handled in chat.
101
102 <Callout type="info">
103 eve's `defineTool` takes plain JSON Schema, so `EveProvider` passes Composio's `inputParameters`
@@ -169,7 +169,7 @@ When this returns `true`, eve pauses before execution and asks the user to appro
169 icon={<BookOpen />}
170 title="iMessage on eve"
171 href="/examples/imessage-agent"
172 - description="A full example: a custom toolkit for local iMessage plus the eve provider, on one session."
172 + description="A full example: a local toolkit for iMessage plus the eve provider, on one session."
173 />
174 <Card
175 icon={<BookOpen />}
docs/content/docs/security/token-custody.mdx
+1 -1
@@ -106,7 +106,7 @@ This redaction has a specific scope. It does not sanitize every provider respons
106
107 [Proxy Execute](/docs/extending-sessions/proxy-execute) requires absolute URLs to use the same scheme and registrable domain (eTLD+1) as the connected account's resolved base URL, so sibling subdomains are allowed. It also requires its own API-key permission. Use relative provider paths and let Composio supply authentication. Granting proxy access allows provider operations beyond predefined tool schemas, subject to the provider's permissions. Review that permission separately from tool selection.
108
109 -For custom business logic, [session extension tools](/docs/extending-sessions/custom-tools-and-toolkits) let your code call the proxy without reading tokens. If you instead [import credentials](/docs/authentication/importing-existing-connections) or handle authentication yourself, include those code paths in your credential review.
109 +For custom business logic, [session extension tools](/docs/extending-sessions/local-tools-and-toolkits) let your code call the proxy without reading tokens. If you instead [import credentials](/docs/authentication/importing-existing-connections) or handle authentication yourself, include those code paths in your credential review.
110
111 ## OAuth app ownership and token custody
112
docs/content/docs/toolkits.mdx
+1 -1
@@ -94,7 +94,7 @@ Toolkit filters choose the apps a session can access. Tool filters narrow that a
94
95 Use [session configuration](/docs/configuring-sessions) to enable or disable toolkits, select individual tools, or filter by tags such as read-only. The connected account's permissions still determine what those tools can do in the app.
96
97 -You can also attach your own local, in-process tools with the experimental [custom tools and toolkits](/docs/extending-sessions/custom-tools-and-toolkits) API.
97 +You can also attach your own local, in-process tools with the experimental [local tools and toolkits](/docs/extending-sessions/local-tools-and-toolkits) API.
98
99 ## Related concepts
100
docs/content/docs/tools-direct/executing-tools.mdx
+1 -1
@@ -413,7 +413,7 @@ curl -X POST https://backend.composio.dev/api/v3.1/tools/execute/proxy \
413 </Tabs>
414
415 <Callout type="info">
416 -Need an API that isn't supported by any Composio toolkit, or want to extend an existing one? Learn how to [create session custom tools](/docs/extending-sessions/custom-tools-and-toolkits).
416 +Need an API that isn't supported by any Composio toolkit, or want to extend an existing one? Learn how to [create session local tools](/docs/extending-sessions/local-tools-and-toolkits).
417 </Callout>
418
419 ## Automatic File Handling
docs/content/examples/custom-tools.mdx
+5 -5
@@ -1,7 +1,7 @@
1 ---
2 title: Combine your own tools with Composio
3 description: Enrich a public Hacker News profile with an internal research note using remote and local tools in one agent.
4 -keywords: [custom tools, preload, direct tools, python, typescript, hackernews]
4 +keywords: [local tools, custom tools, preload, direct tools, python, typescript, hackernews]
5 gallery:
6 categories: [General agents]
7 logos: [hackernews]
@@ -9,7 +9,7 @@ gallery:
9 order: 10
10 ---
11
12 -Build an agent that retrieves a Hacker News profile and adds a note from your own application. Composio executes the public lookup remotely. Your custom tool reads the internal note in your process.
12 +Build an agent that retrieves a Hacker News profile and adds a note from your own application. Composio executes the public lookup remotely. Your local tool reads the internal note in your process.
13
14 This follows the [TypeScript](https://github.com/ComposioHQ/composio/blob/next/ts/examples/tool-router/src/direct-tools-preset.ts) and [Python](https://github.com/ComposioHQ/composio/blob/next/python/examples/tool_router/direct_tools_preset.py) direct-tools examples. The task needs no connected account.
15
@@ -37,7 +37,7 @@ export OPENAI_API_KEY="your-openai-api-key"
37
38 The `HN_RESEARCH` toolkit contains one local tool. The direct-tools preset puts that tool and `HACKERNEWS_GET_USER` directly in the agent's tool list.
39
40 -{/* code-example: no-api reason="Local custom tool runs in the SDK process inside an OpenAI Agents loop" */}
40 +{/* code-example: no-api reason="Local tool runs in the SDK process inside an OpenAI Agents loop" */}
41 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
42 <Tab value="Python">
43
@@ -174,7 +174,7 @@ Use the direct-tools preset when the agent's allowed tool set is small and known
174 The repository's [TypeScript preload example](https://github.com/ComposioHQ/composio/blob/next/ts/examples/tool-router/src/preload.ts) and [Python preload example](https://github.com/ComposioHQ/composio/blob/next/python/examples/tool_router/preload.py) demonstrate that alternative:
175
176 - `preload.tools` selects remote tools to expose immediately.
177 -- `preload: true` on a custom tool or toolkit exposes its local tools immediately.
177 +- `preload: true` on a local tool or toolkit exposes its local tools immediately.
178 - Other allowed tools remain discoverable through search.
179
180 See [preloading tools](/docs/configuring-sessions#preloading-tools) for the configuration in both languages. Preloading controls initial visibility; use the session's tool filters to restrict what the agent can access.
@@ -186,5 +186,5 @@ The local callback runs in your application process. It can query your database
186 Keep the SDK tool execution in your process for this pattern. The [hosted MCP endpoint](/docs/sessions-via-mcp#trade-offs) can't invoke these in-process callbacks. Tool results still become model context, so return only the fields the model needs.
187
188 <Callout>
189 -Custom tools and toolkits are experimental. See [custom tools](/docs/extending-sessions/custom-tools-and-toolkits) for extension tools, authenticated API calls, and callback context.
189 +Local tools and toolkits are experimental. See [local tools and toolkits](/docs/extending-sessions/local-tools-and-toolkits) for extension tools, authenticated API calls, and callback context.
190 </Callout>
docs/content/examples/imessage-agent.mdx
+12 -12
@@ -1,8 +1,8 @@
1 ---
2 -title: iMessage custom toolkit with eve
3 -description: Walk through an agent that texts on your behalf from your own Mac. A Composio custom toolkit wraps local iMessage in-process, and the eve provider puts it on the same session as the whole Composio catalog.
2 +title: iMessage local toolkit with eve
3 +description: Walk through an agent that texts on your behalf from your own Mac. A Composio local toolkit wraps iMessage in-process, and the eve provider puts it on the same session as the whole Composio catalog.
4 keywords:
5 - [custom toolkit, imessage, local tools, eve, provider, session, custom tools, macOS, applescript]
5 + [local toolkit, imessage, local tools, custom toolkit, eve, provider, session, custom tools, macOS, applescript]
6 full: true
7 gallery:
8 categories: [General agents, Background agents]
@@ -25,7 +25,7 @@ you › what did Lena and I last text about?
25
26 The pattern is the takeaway, not iMessage specifically. It comes together from a handful of Composio pieces:
27
28 -1. **A custom toolkit** wraps local iMessage (send, contacts, history, memory) as Composio tools.
28 +1. **A local toolkit** wraps local iMessage (send, contacts, history, memory) as Composio tools.
29 2. **In-process execution** runs each tool right on your Mac through `session.execute`, with no remote API.
30 3. **One session** puts those local tools on the same surface as the 1000+ app catalog.
31 4. **The eve provider** turns `session.tools()` into [eve](https://github.com/vercel/eve)-native tools, so `eve dev` can call them.
@@ -33,7 +33,7 @@ The pattern is the takeaway, not iMessage specifically. It comes together from a
33
34 <ImessageFlow />
35
36 -Below you build the integration core: the custom toolkit first, then the wiring that puts it on a session, then triggers, then a browse of the relevant source. You bring a Composio API key and a Mac. Composio brings the catalog.
36 +Below you build the integration core: the local toolkit first, then the wiring that puts it on a session, then triggers, then a browse of the relevant source. You bring a Composio API key and a Mac. Composio brings the catalog.
37
38 ## Setup
39
@@ -61,9 +61,9 @@ COMPOSIO_API_KEY=xxxxxxxxx
61 </Step>
62 </Steps>
63
64 -## The custom toolkit
64 +## The local toolkit
65
66 -A custom toolkit is a named group of custom tools. Each tool declares an input schema and an `execute` that runs locally. Here is `SEND`, which shells out to AppleScript to drive Messages.app:
66 +A local toolkit is a named group of local tools. Each tool declares an input schema and an `execute` that runs locally. Here is `SEND`, which shells out to AppleScript to drive Messages.app:
67
68 <FileBuildup name="send" />
69
@@ -87,7 +87,7 @@ export function createImessageToolkit() {
87 }
88 ```
89
90 -The toolkit depends only on `@composio/core`, so it drops into any Composio agent. Custom tools execute in-process through `session.execute`, which is why they aren't on the MCP URL yet.
90 +The toolkit depends only on `@composio/core`, so it drops into any Composio agent. Local tools execute in-process through `session.execute`, which is why they aren't on the MCP URL yet.
91
92 ## Wire it up
93
@@ -107,7 +107,7 @@ The provider is what makes `session.tools()` return eve-native tools instead of
107
108 ### Register the local toolkit
109
110 -Pass the custom toolkit through `experimental.customToolkits`, and the local iMessage tools join the catalog on the same session.
110 +Pass the local toolkit through `experimental.customToolkits`, and the local iMessage tools join the catalog on the same session.
111
112 <FileBuildup name="wiring" step={3} />
113
@@ -240,7 +240,7 @@ Use the exact slug from the Composio triggers catalog for each. Signature verifi
240
241 ## Browse the project
242
243 -The key files, in one place. The custom toolkit and the session wiring carry the integration, the eve provider is imported from `@composio/experimental/eve`, and the rest is local macOS glue.
243 +The key files, in one place. The local toolkit and the session wiring carry the integration, the eve provider is imported from `@composio/experimental/eve`, and the rest is local macOS glue.
244
245 <RepoBrowser
246 source="imessage"
@@ -261,8 +261,8 @@ The browser above is an implementation slice, not a standalone fixture: it omits
261 description="EveProvider, the defineComposioTools resolver, and the (ctx, next) hooks."
262 />
263 <Card
264 - title="Custom tools and toolkits"
265 - href="/docs/extending-sessions/custom-tools-and-toolkits"
264 + title="Local tools and toolkits"
265 + href="/docs/extending-sessions/local-tools-and-toolkits"
266 description="Build and register your own in-process Composio tools."
267 />
268 </Cards>
docs/content/examples/index.mdx
+1 -1
@@ -11,7 +11,7 @@ For smaller SDK tasks, browse the [TypeScript and Python examples](/examples/sdk
11 <Card title="General agent with Pi" href="/examples/general-agent-with-pi" description="Build a Pi + Composio agent and drop it into Slack: triggers, per-user sessions, a shared connection, redirected auth links, and the proxy." />
12 <Card title="Daily standup bot" href="/examples/standup-slackbot" description="A Slack bot that drafts each teammate's standup from their own connected tools: your own Slack app, tool-router sessions, manual tool execution, the proxy, and per-member auth links." />
13 <Card title="Local sandbox PR reviewer" href="/examples/local-sandbox-pr-reviewer" description="Run a PR reviewer in your own sandbox while it calls GitHub tools through a Composio session." />
14 - <Card title="iMessage custom toolkit with eve" href="/examples/imessage-agent" description="An agent that texts on your behalf from your own Mac: a custom toolkit wraps local iMessage in-process, and the eve provider puts it on the same session as the whole Composio catalog." />
14 + <Card title="iMessage local toolkit with eve" href="/examples/imessage-agent" description="An agent that texts on your behalf from your own Mac: a local toolkit wraps iMessage in-process, and the eve provider puts it on the same session as the whole Composio catalog." />
15 <Card title="Integrate Composio into an existing harness" href="/examples/harness-integration" description="Connect apps, index tool schemas, and execute tools from your own planner." />
16 <Card title="Run an agent on Cloudflare Workers" href="/examples/cloudflare-workers" description="Deploy an authenticated Worker that calls Composio tools with OpenAI." />
17 <Card title="Select tools with TypeSafe" href="/examples/typesafe-tool-selection" description="Choose a tool, complete its arguments, and execute it with the TypeSafe provider." />
docs/content/reference/glossary.mdx
+5 -5
@@ -39,14 +39,14 @@ A stored set of credentials (OAuth tokens or API keys) linked to a userID, creat
39 The object returned when you initiate authentication. It contains the Connect Link URL and a `waitForConnection()` method that resolves once the user completes the flow.
40 </GlossaryTerm>
41
42 -<GlossaryTerm name="Custom Tool">
43 -A tool you define yourself and use alongside Composio's built-in tools. Add local experimental custom tools and custom toolkits through [Custom tools and toolkits](/docs/extending-sessions/custom-tools-and-toolkits).
44 -</GlossaryTerm>
45 -
42 <GlossaryTerm name="In-Chat Authentication">
43 A flow in which the agent handles authentication itself by calling `COMPOSIO_MANAGE_CONNECTIONS` to generate a Connect Link and send it to the user in the conversation. See [In-chat authentication](/docs/authentication#in-chat-authentication).
44 </GlossaryTerm>
45
46 +<GlossaryTerm name="Local Tool">
47 +A tool you define yourself that runs in your application process alongside Composio's built-in tools. Previously called a custom tool. Add experimental local tools and local toolkits through [Local tools and toolkits](/docs/extending-sessions/local-tools-and-toolkits).
48 +</GlossaryTerm>
49 +
50 <GlossaryTerm name="MCP (Model Context Protocol)">
51 An open protocol for connecting AI models to external tools. Create a session with `mcp: true` to expose `session.mcp.url` and `session.mcp.headers`, an MCP-compatible endpoint any MCP client can connect to. See [Using sessions via MCP](/docs/sessions-via-mcp).
52 </GlossaryTerm>
@@ -64,7 +64,7 @@ Middleware that transforms tool behavior. [Schema modifiers](/docs/tools-direct/
64 </GlossaryTerm>
65
66 <GlossaryTerm name="Native Tools">
67 -Tools you access through provider packages with `session.tools()` and call directly, rather than over MCP. Both paths give the agent the same capabilities, but tools called directly integrate with your AI framework and support modifiers and custom tools.
67 +Tools you access through provider packages with `session.tools()` and call directly, rather than over MCP. Both paths give the agent the same capabilities, but tools called directly integrate with your AI framework and support modifiers and local tools.
68 </GlossaryTerm>
69
70 <GlossaryTerm name="Organization">
docs/lib/home-navigation.ts
+14 -2
@@ -175,7 +175,12 @@ export const DOCS_PRODUCTS = {
175 {
176 type: 'group',
177 label: 'Toolkits & Tools',
178 - links: [{ url: '/docs/toolkits' }, { url: '/docs/instant-tools' }],
178 + links: [
179 + { url: '/docs/toolkits' },
180 + { url: '/docs/instant-tools' },
181 + { url: '/docs/extending-sessions/local-tools-and-toolkits' },
182 + { url: '/docs/extending-sessions/custom-mcp' },
183 + ],
184 },
185 {
186 type: 'group',
@@ -213,7 +218,14 @@ export const DOCS_PRODUCTS = {
218 {
219 label: 'Customize',
220 items: [
216 - { type: 'folder', path: 'extending-sessions' },
221 + {
222 + type: 'group',
223 + label: 'Extend sessions',
224 + links: [
225 + { url: '/docs/extending-sessions/proxy-execute' },
226 + { url: '/docs/extending-sessions/shared-connections' },
227 + ],
228 + },
229 { type: 'folder', path: 'sandbox' },
230 {
231 type: 'group',
docs/next.config.mjs
+17 -6
@@ -637,12 +637,23 @@ const config = {
637 // Custom tools and proxy execute moved under the Extending sessions section.
638 {
639 source: '/docs/custom-tools-and-toolkits',
640 - destination: '/docs/extending-sessions/custom-tools-and-toolkits',
640 + destination: '/docs/extending-sessions/local-tools-and-toolkits',
641 permanent: true,
642 },
643 {
644 source: '/docs/toolkits/custom-tools-and-toolkits',
645 - destination: '/docs/extending-sessions/custom-tools-and-toolkits',
645 + destination: '/docs/extending-sessions/local-tools-and-toolkits',
646 + permanent: true,
647 + },
648 + // Custom Tools and Toolkits was renamed to Local Tools and Toolkits.
649 + {
650 + source: '/docs/extending-sessions/custom-tools-and-toolkits',
651 + destination: '/docs/extending-sessions/local-tools-and-toolkits',
652 + permanent: true,
653 + },
654 + {
655 + source: '/docs/extending-sessions/custom-tools-and-toolkits.:format(md|mdx)',
656 + destination: '/docs/extending-sessions/local-tools-and-toolkits.md',
657 permanent: true,
658 },
659 {
@@ -652,17 +663,17 @@ const config = {
663 },
664 {
665 source: '/docs/custom-tools',
655 - destination: '/docs/extending-sessions/custom-tools-and-toolkits',
666 + destination: '/docs/extending-sessions/local-tools-and-toolkits',
667 permanent: true,
668 },
669 {
670 source: '/docs/tools-direct/custom-tools',
660 - destination: '/docs/extending-sessions/custom-tools-and-toolkits',
671 + destination: '/docs/extending-sessions/local-tools-and-toolkits',
672 permanent: true,
673 },
674 {
675 source: '/docs/tools-direct/custom-tools/:path*',
665 - destination: '/docs/extending-sessions/custom-tools-and-toolkits',
676 + destination: '/docs/extending-sessions/local-tools-and-toolkits',
677 permanent: true,
678 },
679 {
@@ -731,7 +742,7 @@ const config = {
742 },
743 {
744 source: '/custom-tools/:path*',
734 - destination: '/docs/extending-sessions/custom-tools-and-toolkits',
745 + destination: '/docs/extending-sessions/local-tools-and-toolkits',
746 permanent: true,
747 },
748 // Error handling redirect (old fern URL)
docs/tests/integration/redirects.test.ts
+6 -5
@@ -23,10 +23,10 @@ const REDIRECTS = [
23 { from: "/docs/providers/langgraph", to: "/docs/providers/langchain" },
24 { from: "/tools", to: "/toolkits" },
25 { from: "/docs/fetching-tools", to: "/docs/tools-direct/fetching-tools" },
26 - { from: "/docs/custom-tools", to: "/docs/extending-sessions/custom-tools-and-toolkits" },
27 - { from: "/docs/tools-direct/custom-tools", to: "/docs/extending-sessions/custom-tools-and-toolkits" },
28 - { from: "/docs/tools-direct/custom-tools/github", to: "/docs/extending-sessions/custom-tools-and-toolkits" },
29 - { from: "/custom-tools/github", to: "/docs/extending-sessions/custom-tools-and-toolkits" },
26 + { from: "/docs/custom-tools", to: "/docs/extending-sessions/local-tools-and-toolkits" },
27 + { from: "/docs/tools-direct/custom-tools", to: "/docs/extending-sessions/local-tools-and-toolkits" },
28 + { from: "/docs/tools-direct/custom-tools/github", to: "/docs/extending-sessions/local-tools-and-toolkits" },
29 + { from: "/custom-tools/github", to: "/docs/extending-sessions/local-tools-and-toolkits" },
30 { from: "/docs/how-tools-work", to: "/docs/how-composio-works" },
31 { from: "/authentication", to: "/docs/authentication" },
32 { from: "/changelog", to: "/docs/changelog" },
@@ -40,7 +40,8 @@ const REDIRECTS = [
40 { from: "/docs/managed-authentication", to: "/docs/authentication" },
41 { from: "/docs/workbench", to: "/docs/sandbox/remote" },
42 { from: "/docs/sandbox", to: "/docs/sandbox/remote" },
43 - { from: "/docs/custom-tools-and-toolkits", to: "/docs/extending-sessions/custom-tools-and-toolkits" },
43 + { from: "/docs/custom-tools-and-toolkits", to: "/docs/extending-sessions/local-tools-and-toolkits" },
44 + { from: "/docs/extending-sessions/custom-tools-and-toolkits", to: "/docs/extending-sessions/local-tools-and-toolkits" },
45 { from: "/docs/proxy-execute", to: "/docs/extending-sessions/proxy-execute" },
46 { from: "/docs/white-labeling-authentication", to: "/docs/authentication/white-labeling-authentication" },
47 { from: "/docs/shared-connections", to: "/docs/extending-sessions/shared-connections" },
docs/tests/static/sidebar-nav-index.test.ts
+1 -1
@@ -48,7 +48,7 @@ describe('buildSidebarNavIndex', () => {
48 group: 'Guides',
49 folder: 'Extend sessions',
50 depth: 2,
51 - position: index['/docs/extending-sessions/custom-tools-and-toolkits'].position + 1,
51 + position: index['/docs/extending-sessions/local-tools-and-toolkits'].position + 1,
52 });
53 });
54