Reviewing changes
Open the Changes inbox, read the diff for every staged file, and approve or discard each one. Conflicts are flagged when the live file moved in the meantime.
Every edit an agent makes to the Library waits for a person. The review happens in the Changes
inbox at /helios/library/changes. Open it from Library in the sidebar, then Changes.
Nothing is shared until you approve it.
The inbox
The inbox has two tabs.
Open lists every change that still has files waiting. Each row shows the session that produced it, how many files it touches, and when. You see a change only if you can read at least one of its files.
History lists every merged change, newest first. Each entry shows who approved it and when. Files approved together are grouped as one entry.
Reviewing one change
Open a change to see every staged file as a side-by-side diff. Each file is labelled Added, Modified, or Deleted. The diff compares the staged file with the version the agent started from.
A file that a person edited during the session is marked Edited by you.
Three actions are available.
| Action | What it does |
|---|---|
| Approve all | Approves every file in the change that can be approved. |
| Approve | Approves one file. It becomes the live version in the Library. |
| Discard | Rejects one file. The live Library is left as it was. |
Approval is per file. You can approve half of a change and discard the rest.
What approval checks
Approval succeeds only when all of these are true.
- The staged file is the exact version you saw. If the agent rewrote it after you opened the review, Helios refuses and asks you to review the file again.
- The run was allowed to write that path. Edits in a folder that was read-only for the run cannot be approved.
- You have editor access on that path. See permissions.
Every approved version is kept. Approving a change never deletes history.
Conflicts
If someone else changed the live file after the agent staged its version, the file shows a Conflict badge. The review also shows the current live content so you can compare all three.
A file in conflict cannot be approved. Two ways to resolve it.
- Ask the agent to redo its edit on top of the current version. The new edit is staged and replaces the old one.
- Discard the staged file and keep the live version.
Discarding
A discard is recorded even when the sandbox that produced the change has already stopped. If the sandbox is still running, Helios also reverts the file inside the sandbox so the agent sees the original again. That revert is best effort. If it fails, the agent's local copy keeps the edit until the sandbox ends.
Agents cannot approve their own work
A run's own credentials are refused on approve, discard, write, and revert. Only a person with editor access on the path can move a file into the live Library. See permissions.
Next
- Files panel - see a diff while the agent is still working.
- Permissions - who can approve what.
Last updated on
Proposing changes
Agents edit Library files inside their sandbox. Helios captures the edits after a short quiet period and stages them as a change. Nothing is live until a person approves it.
Library permissions
Library access starts from your organization and project roles. Library path grants add viewer or editor access on any folder, for a person, a group, a service account, or the whole organization.