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, 12:15 UTC
docs: clarify generated changelog notes
jkomyno committed
Sep 16, 2026 at 15:09 UTC
2cfcb464d8f429eab3e0b0835db12458fafc60fd
3 files changed
+12
-11
docs/content/docs/extending-sessions/custom-tools-and-toolkits.mdx
+4
-4
@@ -696,10 +696,10 @@ Slugs exposed to the agent are automatically prefixed with `LOCAL_` and the tool
696
697
Your slugs cannot start with `LOCAL_`. This prefix is reserved.
698
699
-You can execute a custom tool by its fully qualified slug. A bare child slug also works when it
700
-identifies exactly one local tool. If two custom toolkits both define `SEARCH`, for example, call
701
-`LOCAL_CATALOG_SEARCH` or `LOCAL_SUPPORT_SEARCH`. Calling bare `SEARCH` raises an error that lists
702
-the qualified slugs instead of choosing one toolkit silently.
699
+Use the final `LOCAL_*` slug when you call a custom tool directly. The original slug still works
700
+when it identifies exactly one local tool. If two custom toolkits both define `SEARCH`, call
701
+`LOCAL_CATALOG_SEARCH` or `LOCAL_SUPPORT_SEARCH`. Calling `SEARCH` directly raises an error with the
702
+qualified slugs instead of choosing one toolkit silently.
703
704
## Next
705
docs/content/docs/sandbox/remote.mdx
+3
-3
@@ -119,9 +119,9 @@ The mount exposes four methods:
119
120
A `RemoteFile` carries the file's bytes and a presigned `downloadUrl`. Read it with `text()` or `buffer()`, or write it to disk with `save(path)`. Its `expiresAt` is when that download link expires, not a TTL on the file: the mount itself has no expiry you set.
121
122
-`RemoteFile.buffer()`, `blob()`, `text()`, and `save()` stop downloads at 100 MiB, even when the
123
-server omits or misreports `Content-Length`. Connection and streamed-body failures raise
124
-`RemoteFileDownloadError`.
122
+A `RemoteFile` download through `buffer()`, `blob()`, `text()`, or `save()` stops at 100 MiB, even
123
+when the server omits or misreports `Content-Length`. Connection failures and streamed-body failures
124
+raise `RemoteFileDownloadError`.
125
126
Every file lives on the session's default `files` mount, surfaced at `/mnt/files/`. Each method takes a `mountId` to address a mount by ID, but there's no SDK call to create custom mounts today, so you'll normally work with `files`.
127
docs/content/docs/tools-direct/executing-tools.mdx
+5
-4
@@ -491,10 +491,11 @@ console.log(result);
491
</Tab>
492
</Tabs>
493
494
-Automatic downloads are limited to 100 MiB, including when the server omits or reports an
495
-incorrect `Content-Length`. A failed Python download removes the partial file and raises
496
-`ErrorDownloadingFile`. TypeScript reports connection and streamed-body failures as
497
-`RemoteFileDownloadError`.
494
+Automatic S3 downloads stop at 100 MiB, even when the server omits or reports an incorrect
495
+`Content-Length`. Python removes partial files for transport and filesystem failures and raises
496
+`ErrorDownloadingFile`; oversized responses raise `ResponseTooLargeError`. In TypeScript, failed
497
+automatic S3 downloads return `file_downloaded: false`. `RemoteFile` connection failures and
498
+streamed-body failures raise `RemoteFileDownloadError`.
499
500
## Security for local file paths
501