Files SDK launches unified storage API with 18 providers and OpenAI, Vercel AI, and Claude tools

• haydenbleasel's launch post says Files SDK shipped with a single storage API across 18 backends, including S3, R2, Vercel Blob, and Google Drive.
• According to the launch post, the core verbs are upload, download, head, delete, copy, list, and url.
• haydenbleasel's thread pitches Files SDK as a web-standards I/O layer that runs across Node, Bun, Deno, edge runtimes, and browsers.
• the same thread also says the package ships tool bindings for OpenAI, Vercel AI, and Claude Agents SDKs.

You can jump straight to the docs site or the GitHub repo. The launch post also makes two unusually concrete promises for a v1 storage abstraction: an "escape hatch" back to native clients, and runtime coverage that includes both edge environments and browsers haydenbleasel's launch post.

The headline claim is breadth. haydenbleasel's launch post lists 18 supported providers and names S3, R2, Vercel Blob, and Google Drive in the opening announcement.

That makes the package read less like a thin wrapper for one cloud and more like a portability layer for object and blob storage. The official landing page is linked in the docs tweet.

The initial API is small:

• upload
• download
• head
• delete
• copy
• list
• url

haydenbleasel's launch post frames that as "one small, honest API," which is the interesting product choice here. The public pitch is not feature completeness, it is keeping the shared surface narrow and leaving an escape hatch for provider-specific work.

The runtime matrix in haydenbleasel's launch post covers Node, Bun, Deno, edge runtimes, and browsers.

The same post says Files SDK also ships tools for three agent stacks:

• OpenAI
• Vercel AI
• Claude Agents SDK

That combination turns the package into more than a storage client. It is also a ready-made file layer for agent workflows that need upload, retrieval, or URL generation without binding the whole stack to one storage vendor.

The package installs with npm i files-sdk, according to the install tweet. That same post links directly to the GitHub repository, while the prior tweet points to the docs site.

Those two links are the only public launch surfaces in the evidence set, which makes this a clean low-ceremony ship: announcement, docs, repo, and a tightly scoped feature set.