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: note that unwritable download names are rejected
jkomyno committed
Sep 30, 2026 at 13:32 UTC
b010e9bdfe1c5ce33d0a3b8e53d96024919ea3b5
2 files changed
+5
-4
docs/content/docs/sandbox/remote.mdx
+1
-1
@@ -123,7 +123,7 @@ A `RemoteFile` carries the file's bytes and a presigned `downloadUrl`. Read it w
123
124
`save(path)` writes exactly where you point it and overwrites whatever is there. Call `save()` with no path and the file goes to `~/.composio/files/` under its name on the mount — and an existing file there survives: the new copy gets a number before its extension, so a second `report.pdf` saves as `report-1.pdf`. The returned path tells you which name was used.
125
126
-Mount paths come from the sandbox, so the SDK makes that default name safe to write before using it. Characters Windows reserves (`:`, `?`, `*`, and control characters) become `_`, over-long names are truncated with their extension kept, and trailing dots and spaces are dropped. Any name these rules changed also carries a short digest of the original, so `What is this?.png` and `What is this*.png` don't land on the same file.
126
+Mount paths come from the sandbox, so the SDK makes that default name safe to write before using it. Characters Windows reserves (`:`, `?`, `*`, and control characters) become `_`, over-long names are truncated with their extension kept, and trailing dots and spaces are dropped. Any name these rules changed also carries a short digest of the original, so `What is this?.png` and `What is this*.png` don't land on the same file. A name that can't be written at all, one containing a NUL byte or with nothing usable left, such as `..`, raises an error instead of saving.
127
128
A `RemoteFile` download through `buffer()`, `blob()`, `text()`, or `save()` stops at 100 MiB, even
129
when the server omits or misreports `Content-Length`. Connection failures and streamed-body failures
docs/content/docs/tools-direct/executing-tools.mdx
+4
-3
@@ -537,9 +537,10 @@ console.log(result);
537
Python names each downloaded file after the name in the tool response, made safe to write first:
538
characters Windows reserves become `_`, an over-long name is truncated with its extension kept, and
539
trailing dots and spaces are dropped. A name any of those rules changed also carries a short digest
540
-of the original, so two names that clean up the same way stay distinct. An existing file in the
541
-download directory is never replaced — the new download gets a number before its extension, so a
542
-second `report.pdf` lands as `report-1.pdf`. TypeScript names automatic downloads after the tool
540
+of the original, so two names that clean up the same way stay distinct. A name that can't be
541
+written at all, one containing a NUL byte or with nothing usable left, fails the download instead.
542
+An existing file in the download directory is never replaced — the new download gets a number
543
+before its extension, so a second `report.pdf` lands as `report-1.pdf`. TypeScript names automatic downloads after the tool
544
slug and a timestamp instead, so its names are already unique.
545
546
Automatic S3 downloads stop at 100 MiB, even when the server omits or reports an incorrect