Autonomy
See what changes when the owner of an area gives agents more or less autonomy. Run a change and watch who acts at each step: Loom, a person, or nobody. Full stays off until the owner accepts the risk statement, and a one-click revert is shown after the merge. Concept
autonomy
Autonomy is set for each area, by its owner
The modes work like the permission modes of a coding agent such as Claude Code, with allow and deny rules on top.
- Observe
Loom reports what it sees. Nothing changes.
- Suggest default
Loom drafts changes. A person approves each one.
- Auto with guardrails
Routine changes merge when every check passes. Anything else waits for a person.
- Full
Changes merge when the required checks pass, with no review: the owner accepts that risk in writing. Any person can revert a change with one click afterwards.
What it cannot do: this is the design. Agents do not yet act on their own under these modes. Data: sample.
Start with a conversation about your system.
We read your system, show you what we found, and agree with your team what to fix first.