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 · Acceptance
A quality gate is an acceptance check you declare on a task or on a whole Work: build, test, lint, type check, or any command of your own. The platform runs the checks against the task workspace and only opens a pull request when they pass.
The project must build. A change that does not compile never reaches review.
Your test suite runs against the task workspace, not a mock of it.
House style is enforced by the same linter your team already runs.
Types must be clean before the change is considered done.
Any command you can run in CI can be a gate — schema checks, snapshot diffs, your own scripts.
Set gates once for a Work, or tighten them for a single task that needs more care.
When a gate fails, the agent gets the failure output and another attempt — a bounded retry loop, not an infinite one. If the checks still fail after the allowed attempts, the task stops and reports what failed instead of opening a pull request you would have to close.
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 →Who may merge, when, and into which branches — a setting you resolve at tenant, organization, Work, and Agent level.
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 →Every run is metered in credits, recorded in a ledger you can read — with daily free credits, plan entitlements, and free runs on your own keys.
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.