Storage

Handles all file operations in Butterbase apps through a single manage_storage tool with five actions: upload_url, download_url, list, delete, and update_config. The mental model is clean: you store object_id UUIDs in your tables (users.avatar_id, posts.image_id), never the s3_key, and generate fresh presigned URLs on demand since they expire in an hour. Upload is a three-step dance: request a URL, PUT the file to S3 with matching Content-Type, then persist the object_id or you've orphaned it. Access control is hardcoded to owner-or-public with an optional app-wide publicReadEnabled flag. No custom RLS on storage_objects, so if you need workspace-level permissions or similar, wrap downloads in a serverless function that checks your own tables first.