> For the complete documentation index, see [llms.txt](https://docs.chirpwireless.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chirpwireless.io/rules-engine/reference/rules-page-and-tabs.md).

# Rules Page and Tabs

The Rules page is where you manage all your home automations. Open it from the sidebar by clicking **Rules engine**. The page is organized into three tabs: **Rules**, **Artifacts**, and **Trash**.

***

## Rules tab

This is the main list of your automations. Each row shows:

| Column            | What it shows                                                             |
| ----------------- | ------------------------------------------------------------------------- |
| **Name**          | The automation name and its description (if you added one)                |
| **Last Modified** | How long ago the automation was last changed — for example, "2 hours ago" |

### Actions

Each automation has three actions on the right side of its row:

* **Edit** — Opens the automation in the visual editor so you can change its logic.
* **Clone** — Creates a copy of the automation. Useful when you want a second automation based on the same pattern — say, a "Bedroom Humidity Alert" cloned from your existing "Basement Humidity Alert."
* **Delete** — Moves the automation to the Trash tab (it is not permanently removed right away).

### Lock indicator

If another household member is currently editing an automation, a lock icon appears next to its name. Hovering over the icon shows a tooltip: *"The rule is in edit mode. The rule cannot be changed while it is being worked on by another employee of the organization."* along with the time the lock expires.

While an automation is locked, Edit, Clone, and Delete are disabled for everyone else. The lock releases automatically after the editor saves and exits, or after a period of inactivity.

### Adding a new automation

Click the **Add Rule** button to create a new automation. This opens a blank canvas in the visual editor with a Start Event already placed.

***

## Artifacts tab

The Artifacts tab shows every automation that has been **built** — compiled into a deployable artifact. This is where you deploy, stop, and manage the running versions of your automations.

### Search

A search input at the top lets you filter the artifacts list by name. This is helpful when you have many automations and need to find one quickly.

### Layout

Artifacts are grouped by automation name. Each group shows the **Rule name** and **Description** as columns. Click the expand arrow on a row to see all builds for that automation.

### Expanded artifact details

Each build shows:

* **Build timestamp** — When this artifact was compiled.
* **Status** — One of:
  * **Running** (green) — The artifact is live and processing sensor data right now.
  * **Stopped** (orange) — The artifact was deliberately stopped by you or a household member.
  * **Force Stopped** (red) — The system detected repeated errors and automatically stopped the artifact. See [Fixing Builds and Runtime Stops](/rules-engine/reference/fixing-builds-and-runtime-stops.md) for recovery steps.
* **Comment** — A text note attached to the build. Comments are inline editable — click a comment to update it without rebuilding. Add notes like "initial version" or "replaced by v3 due to false alarms."
* **Artifact Source** — A link that opens the automation's current state in a read-only editor view.
* **Deploy** / **Stop** / **Delete** — Actions to control the artifact lifecycle.

***

## Trash tab

Automations you delete from the Rules tab appear here. Each row shows:

| Column           | What it shows                    |
| ---------------- | -------------------------------- |
| **Name**         | The automation name              |
| **Description**  | The automation description       |
| **Deleted time** | The date and time it was deleted |

The only action available is **Restore rule**, which moves the automation back to the Rules tab. Restored automations come back unlocked.


---

# 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://docs.chirpwireless.io/rules-engine/reference/rules-page-and-tabs.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.