Predicted changes, then reported changes
See files, packages, services and users in a change view. Check shows what Ansible predicts; some steps cannot be predicted, and some tasks can make real changes even during a dry run. Review your playbooks before Check.
Apply re-runs the playbook. It cannot apply a saved plan, and the result may differ. BareTold flags changes that were not predicted as Ansible reports them. See how a run works.
Diffs and the raw log
Read additions, removals, permissions and ownership changes when Ansible provides them. Package versions are labelled as reported, looked up or not reported. Some steps have no diff to show.
Open the raw log for Ansible’s own output, with secrets masked by BareTold. Masking in the app does not protect logs kept outside it. Understand the safety limits.
Searchable run history
Return to runs made through BareTold and search the evidence. Changes made outside BareTold are not recorded.
Free gives access to the latest 10 runs of the open project before filters. Pro gives access to full retained history. The Free reading limit does not delete older runs. Compare history access and plans.
Edit and reuse steps with Pro
Pro includes editing in the step editor, block library and project files. Free keeps these views available to read, with editing view-only.
Save selected steps as a reusable block in your personal or project library. Review the changes before saving or inserting. A block may need variables or other steps from its original project; review those dependencies and Check in the destination project. Inserting a block never runs it automatically.
Export change reports with Pro
Preview a run’s report, then export it as Markdown or PDF. Reports describe Ansible’s predictions or reports, rather than guaranteeing the host’s state.
Secrets are masked, but reports can still identify projects, hosts and people. Review the preview before sharing. Editing and reports are included in free Pro access during the beta until 1.0. See pricing or browse the Guide.