-[**Premium license**](../../licensing/index.md)

-**Compatible Terraform provider**: Use`coder/coder` Terraform provider`>= 2.4.0`.

-**Compatible Terraform provider**: Use`coder/coder` Terraform provider`>= 2.4.1`.

-**Feature flag**: Enable the`workspace-prebuilds`[experiment](../../../reference/cli/server.md#--experiments).

Prebuilt workspaces that fail during provisioning are retried with a backoff to prevent transient failures.

1. When a developerrequests a new workspace, the claiming process occurs:

1. When a developercreates a new workspace, the claiming process occurs:

1. Developer selects a template and preset that has prebuilt workspaces configured.

1. If an eligible prebuilt workspace exists, ownership transfers from the`prebuilds` user to the requesting user.

datasources (see[Preventing resource replacement](#preventing-resource-replacement) for further considerations).

Thedeveloper doesn't see the claiming process — the workspace will just be ready faster than usual.

Theclaiming process is transparent to the developer — the workspace will just be ready faster than usual.

You can view available prebuilt workspaces in the**Workspaces** view in the Coder dashboard:


_Note the search term`owner:prebuilds`._

Unclaimed prebuilt workspaces can be interacted with in the same way as any other workspace.

However, if a Prebuilt workspace is stopped, the reconciliation loop will not destroy it.

This gives template admins the ability to park problematic prebuilt workspaces in a stopped state for further investigation.

Prebuilt workspaces are not updated after they are provisioned.

has[`ForceNew`](https://github.com/hashicorp/terraform-provider-aws/blob/main/internal/service/ec2/ec2_instance.go#L75-L81) set,

since the AMI cannot be changed in-place._

Once a prebuilt workspace has been claimed, and if its template uses`ignore_changes`, users may run into an issue where the agent

does not reconnect after a template update. This shortcoming is described in[this issue](https://github.com/coder/coder/issues/17840)

and will be addressed before the next release (v2.23). In the interim, a simple workaround is to restart the workspace

when it is in this problematic state.

The prebuilt workspaces feature has these current limitations:

Prebuilt workspaces can only be used with the default organization.

-**Autoscaling**

Prebuilt workspaces remain running until claimed. There's no automated mechanism to reduce instances during off-hours.