> 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/managing-automations.md).

# Managing Automations

Once you have a few automations running, you will want to know that everything is under control — that you can review what is running, undo a change if something goes wrong, and clean up automations you no longer need.

Chirp gives you a set of management tools designed around one principle: **you should never lose your work, and you should always be able to recover.** Every edit is versioned, every delete goes to trash first, and editing locks make sure two people do not accidentally overwrite each other's changes.

## What This Section Covers

* [**View, Edit, and Locks**](/rules-engine/managing-automations/view-edit-and-locks.md) — Understand the difference between viewing and editing an automation, how editing locks work when multiple household members share the platform, and how autosave keeps your work safe while you make changes.
* [**History, Restore, and Recovery**](/rules-engine/managing-automations/history-restore-and-recovery.md) — Browse the full version history of any automation, give versions meaningful names, view what an automation looked like at any point in time, and restore a previous version if a recent change caused problems.
* [**Trash and Restore**](/rules-engine/managing-automations/trash-and-restore.md) — When you delete an automation, it goes to trash — not into the void. Learn how to find it, bring it back, and understand how long deleted automations are kept.

These features work quietly in the background while you build and run your automations. You might not think about them until the day you need to undo a mistake — and when that day comes, you will be glad they are there.


---

# 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/managing-automations.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.