Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | --- |
| 2 | type: "troubleshooting" |
| 3 | title: "Tool Router Files" |
| 4 | description: "Public guidance for passing Tool Router session files to toolkit actions." |
| 5 | category: "sessions-and-execution" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-07-14T00:00:00Z" |
| 8 | tags: |
| 9 | - "mcp" |
| 10 | - "tool-router" |
| 11 | - "files" |
| 12 | - "uploads" |
| 13 | --- |
| 14 | # Tool Router Files |
| 15 | |
| 16 | ## Session paths are not `FileUploadable` storage keys |
| 17 | |
| 18 | Tool Router session files and toolkit `FileUploadable` inputs are different abstractions. Do not pass `/workspace/output/...`, `/mnt/files/...`, a local machine path, or an old/foreign `file_...` handle directly as `s3key`. |
| 19 | |
| 20 | When workbench/meta tools are available: |
| 21 | |
| 22 | - For a file already under `/mnt/files`, use `get_mount_file_s3_key("file.ext")`. |
| 23 | - For another sandbox path, use `upload_local_file("/path/to/file.ext")`. |
| 24 | - Pass the returned key to the toolkit action as `{ "name": "file.ext", "mimetype": "...", "s3key": "<returned key>" }`. |
| 25 | |
| 26 | In SDK/API flows, upload or stage the file first and pass the fresh returned file object. |
| 27 | |
| 28 | If an action reports `Failed to download file with s3key ... storage returned HTTP 404`, it failed while resolving the Composio-staged file, before the provider received it. Re-stage the file and retry with the fresh object. |