feat(providers): support large agent-block attachments via Files APIs and remote URLs#5092

Merged

waleedlatif1 merged 16 commits into

stagingfrom

worktree-provider-files-api

Jun 16, 2026

Commits on Jun 16, 2026

feat(providers): support large agent-block attachments via Files APIs and remote URLs
waleedlatif1
committed
fix(providers): clear forged file handles for inline providers too
waleedlatif1
committed
fix(providers): correct OpenAI expiry serialization and Anthropic large-text-doc handling
waleedlatif1
committed
fix(providers): harden large-file path (SSRF fetch, ceiling gate, per-file UI limit)
waleedlatif1
committed
refactor(providers): read files-api upload bytes via storage SDK
waleedlatif1
committed
docs(providers): clarify files-api bytes are read from storage at upload time
waleedlatif1
committed
fix(providers): enforce access checks and strip forged ids in the upload path
waleedlatif1
committed
fix(providers): resolve UI attachment limit with the same model->provider helper as execution
waleedlatif1
committed
test(providers): add new models.ts exports to provider mocks
waleedlatif1
committed
fix(providers): guard Gemini upload response name before polling
waleedlatif1
committed
fix(uploads): type the file-handle key list so omit preserves UserFile fields
waleedlatif1
committed
refactor(providers): run handle-clear + URL-mint in executeProviderRequest for all callers
waleedlatif1
committed
fix(azure-openai): guard optional attachment dataUrl in inline image part
waleedlatif1
committed
fix(providers): upload OpenAI files via multipart and fix Buffer Blob part
waleedlatif1
committed
fix(providers): forward userId from the providers API to executeProviderRequest
waleedlatif1
committed
fix(providers): fail clearly when a large attachment has no cloud storage
waleedlatif1
committed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat(providers): support large agent-block attachments via Files APIs and remote URLs#5092

feat(providers): support large agent-block attachments via Files APIs and remote URLs#5092
waleedlatif1 merged 16 commits into
stagingfrom
worktree-provider-files-api

Commits on Jun 16, 2026

feat(providers): support large agent-block attachments via Files APIs and remote URLs

fix(providers): clear forged file handles for inline providers too

fix(providers): correct OpenAI expiry serialization and Anthropic large-text-doc handling

fix(providers): harden large-file path (SSRF fetch, ceiling gate, per-file UI limit)

refactor(providers): read files-api upload bytes via storage SDK

docs(providers): clarify files-api bytes are read from storage at upload time

fix(providers): enforce access checks and strip forged ids in the upload path

fix(providers): resolve UI attachment limit with the same model->provider helper as execution

test(providers): add new models.ts exports to provider mocks

fix(providers): guard Gemini upload response name before polling

fix(uploads): type the file-handle key list so omit preserves UserFile fields

refactor(providers): run handle-clear + URL-mint in executeProviderRequest for all callers

fix(azure-openai): guard optional attachment dataUrl in inline image part

fix(providers): upload OpenAI files via multipart and fix Buffer Blob part

fix(providers): forward userId from the providers API to executeProviderRequest

fix(providers): fail clearly when a large attachment has no cloud storage