Changes and approvals
The Changes page is the ledger of write actions across your environments: everything the agent has proposed, applied, or been denied. If the agent only ever answers questions in Read-only mode, this page stays empty; the moment a Manual-mode run proposes a fix, it shows up here.
The approval flow (Manual mode)
When an environment is in Manual mode and the agent decides a change is needed, the run suspends and the proposed action is recorded as pending. You can decide it in either place:
- inline in the Agent chat, where the proposal interrupts the conversation, or
- from Changes, where every pending proposal across environments is listed with two actions: Approve and apply or Dismiss without applying.
Approving relays exactly the proposed action to the environment's connector and resumes the agent run with the result. Dismissing resumes the run with the denial, so the agent can adjust its plan (or explain what would have been needed).
What lands in the ledger
| Entry | When |
|---|---|
| Pending proposal | Manual mode: the agent wants to change something and is waiting on you. |
| Applied change | You approved it, or the environment was in Auto mode and validation passed. |
| Dismissed proposal | You declined it; nothing was executed. |
Every entry records what the action was and the environment it targeted, so the ledger doubles as the audit trail for agent-driven writes.
What counts as a change
Anything that is not a read. In practice, on the connector side there are exactly two write channels, both opt-in on the host:
- Active response relays (for example a firewall-drop on an agent), enabled by default in the connector config and the only write a default install can perform.
- Shell commands for diagnose-and-fix work, only if the connector was
installed with
--enable-exec, and always screened by a server-side safety denylist on top of the mode and approval gates.
See connector configuration for how to widen or narrow what a given host allows.