What this is
This page covers how to run workflows and how autonomy approvals keep execution safe.
Why I built this
I built Rune to make automation feel visual and controllable instead of hidden behind technical setup. Teams often know what they want to automate, but they lose momentum when configuration is hard to understand or trust. Rune gives teams a guided workflow builder with clear runs and approvals so automation can be adopted safely.
Who should use this
- Operations teams designing repeatable automated routines.
- Product teams that need visual workflow editing and safe approvals.
- People who want automation without writing technical scripts.
What you can do today
- Launch runs and review completion state.
- Inspect autonomy requests before approval.
- Keep a safe progression from manual to autonomous execution.
Quick start
By the end of this page, you will have a clear and repeatable first outcome in Rune Runs and Autonomy.
- Start with supervised runs until outputs are stable.
- Use inspect view to review autonomy context.
- Approve only when expected behavior is consistent.
Known limits and maturity
- Autonomy is powerful and should be introduced with guardrails.
- Approval workflows are not optional in early rollout.
- Escalation paths should remain available for uncertain cases.
- Current maturity: active.