Environments
See the short-lived machines your agents create to run code, open their preview links, extend their lifetime, or destroy them from the Environments page.
When a task needs a machine to run an app — to build it, deploy it, and give you a link to try — an agent can create an environment: a short-lived machine with the app running on it. The Environments page lists those machines so you can open them, keep them longer, or clean them up.
Before you start#
- Environments must be turned on for your team. When they are, Environments appears in the account menu. If they are off, the page says “Environments are off for this team.”
- Team limits, such as the maximum lifetime, are shown read-only in Settings → Team.
Steps#
- Open Environments from the account menu.
- Filter with Whose environments (All or Mine) and Live or ended (Live or Ended).
- Read each row: its state (for example Creating, Starting, Ready, Failed), who created it, and when it Expires. Rows created by an agent link to the task with Created by an agent. Open the task.
- Open Preview links to try the running app in a new tab.
- Select Extend and pick 1 hour more, 4 hours more, or 1 day more. An extension stops at the team limit.
- Select Destroy to delete the machine now. Preview links stop working, and you cannot undo it.
Turn on Auto-refresh to keep the list current while an environment starts.
Example#
A task asks the agent to “deploy this branch and give me a link.” The agent creates an environment and posts the preview link in chat. You review it, select Extend → 4 hours more so a teammate can look, and Destroy it when the review is done.
Questions
- What happens when an environment expires?
- It ends and its machine is removed. It moves to the Ended list, and its preview links stop working.
- Who can extend or destroy an environment?
- You can change the environments you are allowed to manage, such as ones you or your agents created. The page shows the actions available to you.