Jan 20, 2026

Version Information

TypeScript/JavaScript

• Package: @composio/core and provider packages
• Version: 0.5.3+

Python

• Package: composio and provider packages
• Version: 0.10.8+

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.

What Changed

Before (Bug)

File properties inside anyOf, oneOf, or allOf were not detected:

// This schema's file_uploadable was NOT being processed
inputParameters: {
  type: 'object',
  properties: {
    fileInput: {
      anyOf: [
        {
          type: 'string',
          file_uploadable: true  // ❌ Not detected
        },
        {
          type: 'null'
        }
      ]
    }
  }
}

After (Fixed)

File properties are now correctly detected and processed at any nesting level:

// Now properly detected and transformed
inputParameters: {
  type: 'object',
  properties: {
    fileInput: {
      anyOf: [
        {
          type: 'string',
          file_uploadable: true  // ✅ Detected and processed
        },
        {
          type: 'null'
        }
      ]
    }
  }
}

Affected Scenarios

How to Update

TypeScript/JavaScript

npm update @composio/core@latest

pnpm update @composio/core@latest

yarn upgrade @composio/core@latest

Python

pip install --upgrade composio

uv pip install --upgrade composio

poetry update composio

Backward Compatibility

This release is fully backward compatible:

• All existing code continues to work without modifications
• No migration required
• File upload/download for direct properties continues to work as before
• The fix only adds support for previously unsupported schema patterns

Impact Summary

Summary

Files involved in tool execution are now shared via presigned URLs with a default TTL (time-to-live) of 1 hour. You can customize the file TTL through your project configuration.

What changed

When tools return files (images, documents, exports, etc.), these files are now delivered as presigned URLs with a configurable TTL instead of non-expiring URLs. This provides:

• Automatic cleanup - Files expire after the configured TTL
• Configurable retention - Adjust file availability based on your application's needs

Default behavior

All files returned from tool execution now have a 1 hour TTL by default. After this period, the presigned URLs expire and files are no longer accessible.

Configuring file TTL

You can adjust the file TTL to match your application's needs.

Via Dashboard

1. Navigate to Project Settings in your Composio dashboard
2. Find the File TTL configuration option
3. Set your desired TTL value

Via API

Use the Update Project Config API to programmatically configure the file TTL:

curl -X PATCH "https://backend.composio.dev/api/v3/org/projects/config" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "fileTtl": 3600
  }'

Impact

Migration

No code changes are required. Your existing integrations will continue to receive file URLs as before, but these URLs will now expire after the configured TTL.

If your application stores or caches file URLs for later use, ensure you handle URL expiration appropriately by either:

• Downloading files before the TTL expires
• Re-executing the tool to obtain fresh URLs when needed
• Increasing the TTL via project settings to match your retention requirements