Clarify self-hosted task images

[jasonkeung]

Summary

Clarifies that custom dependencies for self-hosted/cloud agent runs belong in the task/workspace image, not Warp-managed sidecar/runtime images.

This updates the environment and self-hosting docs to:

• Define the environment Docker image as the task image where code, setup commands, dependencies, and scripts live
• Note that Warp manages agent sidecar/runtime images separately
• Clarify that Kubernetes default_image should be the task/workspace image

Related issues

Source context: https://staging.warp.dev/conversation/c96df305-5df2-4af8-8b14-762460f83164

Validation

• git --no-pager diff --check
• Reviewed the changed MDX sections manually
• Did not run Astro typecheck/build because this is a docs-only text clarification and dependencies were not installed in the fresh clone

Screenshots

Not applicable; text-only docs change.

Follow-ups

None.

Co-Authored-By: Oz oz-agent@warp.dev

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	May 27, 2026 9:58pm

[oz-for-oss]

@jasonkeung

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[oz-for-oss]

Overview

This PR clarifies that custom dependencies for self-hosted and cloud agent runs belong in the task/workspace image, not Warp-managed agent runtime images. The changes are scoped to documentation copy, and I did not find security concerns.

Concerns

• One wording issue could be more precise: a Docker image is the base for the task container/workspace, not the workspace itself.

Verdict

Found: 0 critical, 0 important, 1 suggestions

Approve with nits

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[oz-for-oss]

💡 [SUGGESTION] The image is the base for the task container/workspace, not the workspace itself; this wording avoids implying users should bake cloned code into the image.

Suggested change

The Docker image in an environment is the **task image**: the workspace where your code is cloned, setup commands run, and language dependencies or system packages should be installed. It is separate from Warp-managed agent sidecar/runtime images. If you need tools like `libssl`, `libclang`, package managers, or internal scripts available during a run, add them to your task image or start from one of Warp's [prebuilt dev images](https://github.com/warpdotdev/oz-dev-environments).

The Docker image in an environment is the **task image**: the base image for the workspace where your code is cloned, setup commands run, and language dependencies or system packages should be installed. It is separate from Warp-managed agent sidecar/runtime images. If you need tools like `libssl`, `libclang`, package managers, or internal scripts available during a run, add them to your task image or start from one of Warp's [prebuilt dev images](https://github.com/warpdotdev/oz-dev-environments).

[liliwilson]

Thank you for doing this!

[rachaelrenk]

LGTM, going to add this to the merge queue--thanks very much for the updates!