We’re building Ever Works in public. Some things may be incomplete, missing, or broken while we continue improving the platform.We’re building Ever Works in public — expect a few rough edges.
Feature · Review
An Agent that edits your site should be at least as easy to review as a colleague. In Ever Works every task works on its own branch, your own checks decide whether the work is done, a merge policy decides who may land it, and the run leaves a full record behind: the files it touched, the commands it ran, the commits it made. You review evidence, not a summary.
A task gets a dedicated branch and an isolated checkout, so Agents working in parallel never share a working tree. Before a pull request exists, the merge is tested and any conflicts are named by file.
Build, test, lint, type check or any command of your own run against that checkout. Set the Work’s checks to required and a red result goes back to the Agent with the failure output, for one to five attempts.
Under a required policy, only a green gate opens the pull request. When the attempts run out, the task stops with the gate red and the failure recorded, so you never have to close a pull request that should not exist.
By default Agents open pull requests and people merge them. Agent merging is off, a green gate and a recorded human approval are both required, and main, master, develop and stage are protected branches.
Every run leaves records you can open, read and keep.
Each run’s detail page lists the files it touched and every tool call with its arguments and results, with secrets redacted.
Watch a run live in its terminal, or replay its stored output after it ends. The output is redacted before it is ever written down.
Each check’s verdict, exit code and log tail, plus an attempt counter. After a run it shows the checks that actually ran, so editing a check later never rewrites history.
Side-effectful actions such as spawning an agent, scheduling a task, sending a message or overriding a budget can queue for you, flagged as destructive, cross-scope, high fan-out or budget override.
The Activity Log records generations, deployments, imports, and plugin and schedule changes, and exports to CSV. A Work’s History tab lists the items, comparisons and taxonomy entries that were added, updated or removed.
The change itself is a commit on the task’s branch in a repository you own. Diff it, comment on it or revert it with the tools you already use.
Review in Ever Works happens on the pull request, before the merge. There is no preview-then-promote step for deploys today: a deploy goes to the live site, and a redeploy is a rolling update of the same site, so the merge is the gate that matters. The evidence is the transcript, the checks and the diff, not screenshots. The platform’s screenshot capability is used for item previews and social images, not for capturing anyone’s screen.