Warp: Cloud Agents Now Accept Image and File Attachments
WarpWarp's cloud agents (Oz) can now accept images and file attachments as context — a capability previously limited to local agent conversations. This removes a long-standing limitation for developers who rely on cloud-based agent sessions, enabling richer, visually-grounded prompts for remote tasks such as UI debugging, design-to-code workflows, and documentation-driven development.
Key Takeaways
- Cloud agents can now accept image and file attachments, removing a limitation that previously required developers to describe visual context in text when using remote Oz sessions.
- The feature closes a parity gap between Warp's local and cloud agents, enabling the same rich visual workflows in both execution environments.
- UI debugging and design-to-code workflows become viable in cloud sessions, since screenshots and mockups can now be passed directly as context.
- File attachments are also supported, allowing log files, configuration files, and documents to be provided to cloud agents without stdin workarounds.
- This is part of Warp's ongoing roadmap to bring cloud agents to full feature parity with local agents as teams increasingly adopt cloud-based scheduled and team-scoped workflows.
- Warp's cloud agent differentiation strengthens against competitors: image-aware cloud execution is a capability few terminal-based agent platforms currently offer.
Sources & Mentions
4 external resources covering this update
Cloud Agents Gain Image and File Context Support
Warp's Oz cloud agents have reached feature parity with local agents on a key dimension: the ability to accept images and file attachments as context. Until this release, image and file attachment support was restricted to local agent conversations — cloud agents required developers to describe visual context in text or reference file paths within the remote environment.
What Changed
Cloud agent conversations now support the same image attachment methods available to local agents:
- Uploading via the toolbelt's image upload button
- Copying and pasting images directly into the conversation
- Dragging and dropping images from a file manager or screenshot utility
Supported formats include .jpg, .jpeg, .png, .gif, and .webp. File attachments can also be passed alongside images, enabling developers to provide documents, configuration files, or other binary context to cloud-running agents.
Why This Matters
Cloud agents in Warp run in isolated, managed environments — a key feature for teams that want reproducible, server-side execution. But this isolation previously meant that any workflow involving visual artifacts (screenshots, design mockups, error dialogs) required extra effort to translate visual context into text before an agent could act on it.
With image and file attachment support now available in cloud sessions, workflows like these become possible without workarounds:
- UI debugging: Attach a screenshot of a broken interface and ask the cloud agent to diagnose and fix the underlying component.
- Design-to-code: Provide a design mockup and have the agent generate or update the corresponding implementation.
- Log analysis: Attach a long log file directly rather than piping its contents through stdin.
Closing the Gap Between Local and Cloud Agents
This update is part of a broader trend in Warp's roadmap: progressively aligning the capabilities of cloud-based agents with their local counterparts. As cloud agents become the standard for team-scoped and scheduled workflows, ensuring they can process the same rich context that local agents handle is essential for adoption by teams that rely on visual or file-based workflows.