Plans and helpers for bigger requests

Ask Halon for something that takes more than one step, such as a release or a fix across two systems, and it now writes a short plan first and keeps it up to date while it works. See Halon's plans.

A checklist you can watch. The plan shows your goal in your words and one step per action, each naming where it happens, in the chat and in the Slack thread you asked from. A step that changes something shows how to put it back before it runs. Each change still asks you as usual, and approval rules still apply.

Checked, then reported. A plan that changes something ends by reading how what it touched stands now, against its usual error rate and latency, and says Worked, Did not work or Could not check. Halon then reports against your goal with links to the run or the deploy. If a step fails, the plan stops and offers Retry and Undo.

Helpers. When a question needs several reads that do not depend on each other, such as the logs, the recent deploys and the error rate of one service, Halon hands them to helpers that read at the same time and report back in a few lines. Helpers only read, with the same permissions as whoever Halon is working for. See Helpers.