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.
Control & safety · Governance
Merge policy is a setting, not a hardcoded rule. Decide whether agents may merge at all, which branches they may merge into, and what has to be true first. Set it broadly at the tenant level and tighten it where it matters.
The widest default. Set the rule your whole account inherits.
Override per organization when different teams work at different speeds.
Tighten a single site or repository without changing anything else.
Trust one agent with more, or hold a new one to review-only, without touching the rest.
Out of the box the policy is the careful one: changes arrive as pull requests for a human to merge. Loosen it deliberately, at the level you choose, once you have watched enough runs to trust them. The most specific setting wins, so a narrow exception never forces a broad one.
Declare the checks a change must pass. The platform runs them for real — and a red check opens no pull request.
Learn more →Every task gets its own branch and its own checkout. Agents open pull requests, and conflicts surface before the PR — with the conflicting files named.
Learn more →Code and content both live in your own Git, and the platform is open source under AGPLv3 — nothing is locked in.
Learn more →Run many agents at once from one cockpit — live status, current activity, tokens and cost — and steer, interrupt, or resume any of them.
Learn more →Describe what you want to build. Ever Works researches it, ships it, and keeps it improving — content and code, owned in your own Git.