Instead of creating a new workspace when a developer requests one, if a workspace matches a preset defined in the

template parameters, Coder assigns an existing instance, reducing setup time significantly.

```

1. Publish and import the template.

1. Coder automatically provisions another prebuilt workspace through an internal reconciliation loop

(similar to Kubernetes) to maintain the number of specified `instances`.

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

A prebuilt workspace is automatically and transparently assigned to a user when a:

- User creates a new workspace via the API or the Coder web UI.

- User selected a preset which has been configured for prebuilds.

The ownership of the prebuilt workspace will change to the requesting user, and this is referred to as a "claim".

When a template version changes, all prebuilt workspaces relating to an inactive template version are destroyed.

New prebuilt workspaces will be provisioned for the active template version.

which is necessary for running an up-to-date workspace. For example, if

an [AMI](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html) which is referenced by your template is updated,

you can simply delete the prebuilt workspaces, and they will be recreated with the latest AMI.

Should this occur when a prebuilt workspace is claimed, all Template Admins will receive a notification which will

link them to the build logs to investigate which resource was being replaced.

To avoid this problem, you will need to add a `lifecycle` block to your resource:

"title": "Prebuilt workspaces",

"description": "Pre-provision a ready-to-deploy workspace with a defined set of parameters",

"path": "./admin/templates/extending-templates/prebuilt-workspaces.md",

},

{

"title": "Icons",