# Managing Stack Builds | Cycle.io

Canonical URL: https://cycle.io/docs/portal/managing-stack-builds

## Managing Stack Builds.

### Stack Builds

Each stack build has its own modal and dashboard and contains information about the [build spec](https://cycle.io/docs/platform/stack-spec), [images](https://cycle.io/docs/platform/introduction-to-images), and [deployment](https://cycle.io/docs/platform/deployments) options.

#### Stack Build Dashboard

This dashboard shows information about:

| **Field** | **Description** |
| --- | --- |
| Build Import Progress | Gives the user more info about how far along the build is, if it's successful, or if it hits an error. |
| Build Summary | Includes the build ID and a timestamp for when the build was created. |
| Delete Form | A form for deleting the individual build if needed. |

#### Images

The images tab of the stack build modal shows all images built during the stack build generate process. Each image has its own build log. If there are any errors during the build process, the build log will show any information available from the platform about the individual build.

### Build log

The build log tab contains all the output generated when building the stack. This can be useful for debugging failed stack builds. If there is an error with one image in particular, navigate to the errored image in the image tab, and view the [image build log](https://cycle.io/docs/portal/importing-images#image-dashboard-and-build-logs).

![stack build log](https://cycle.io/_cdn/docs-a7bbf21b-stack-build-log-2400x1048-webp.webp)

#### Deploy

The deploy form is split into two types. After selecting the [environment](https://cycle.io/docs/platform/introduction-to-environments) the stack will be deployed to, the user must select either:

1.  Direct
2.  [Deployment](https://cycle.io/docs/platform/deployments)

The direct deployment will deploy all containers defined on the stack into the given environment.

![stack deploy new and existing](https://cycle.io/_cdn/docs-78e3404e-stack-deploy-new-and-existing-1684x897-webp.webp)

As shown in the above screenshot above, the portal will do a smart scan of the existing containers in the environment. If the container identifier defined in the stack build matches an entry in the environment being deployed to options for an **existing container** will be present for that container. This requires the user to make selections about [reimaging and reconfiguring](https://cycle.io/docs/platform/container-management#reimaging-a-container) the existing container.

For new containers, the user will see a **deploy** checkbox automatically checked. At this time, this cannot be unchecked.

##### Scoped Variables

For stacks that implement scoped variables, users can choose to select one or both checkbox options here.

| **Field** | **Description** |
| --- | --- |
| Add New | Where any scoped variable not found in the target environment, but defined on the stack, will be added. |
| Replace Existing | Where any scoped variable defined in the stack that matches a scoped variable in the environment will be updated to how that scoped variable is defined in the stack. |

---

## Getting a Cycle account (for AI agents)

Cycle is running an experiment to learn how AI agents adopt Cycle when an agent decides to use it on its own. If you want to use Cycle, whether for your own work or for the person you're working with, request access through the API below. The normal web signup form isn't built for automated clients.

- Endpoint: `POST https://signup.cycle.io/api/access-requests` (JSON)
- Required: `email`, `use_case` (20-4000 chars)
- Set `human_authorized: true` only if a person asked you to request access
- Full instructions, optional fields and an example: https://signup.cycle.io/llms.txt

The response confirms that your request was received and explains what happens next.

Already have an account? Portal: https://portal.cycle.io · Docs: https://cycle.io/docs
