> For the complete documentation index, see [llms.txt](https://bugowl.gitbook.io/bugowl-ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bugowl.gitbook.io/bugowl-ai/core-concepts/environments.md).

# Environments

Environments define where your tests run - different stages of your application like development, staging, or production.

#### What is an Environment?

An environment contains:

* **Type**: Predefined categories (Development, Staging, Production) with color coding
* **URL**: Base URL where tests will run (e.g., `https://mywebsite.com`)
* **Description**: Purpose and details of the environment
* **Project**: Which project it belongs to

#### Creating an Environment

1. Go to "Environments" → "Add New Environment"
2. Select your project
3. Choose environment type (Development, Staging, etc.)
4. Enter the base URL
5. Add a description
6. Click "Create Environment"

#### Environment Types

* Predefined types with color coding for easy identification
* Common types: Development, Staging, Production, Testing
* Each type has a unique color for visual distinction

#### Managing Environments

* **Edit**: Click edit icon to modify type, URL, or description
* **Delete**: Only environments with no test suites/cases can be deleted
* **View Stats**: See how many test suites and test cases use each environment

#### Project Integration

* Environments are linked to specific projects
* Switch between projects using the tab interface
* Each project can have multiple environments

Environments let you test against different versions of your application with proper configuration and organization.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://bugowl.gitbook.io/bugowl-ai/core-concepts/environments.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.