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.
Operate · Work tracking
A Task is the concrete thing somebody, or some Agent, does next. Tasks live at /tasks, each gets a per-account slug (T-1, T-2, …) that shows on every card, row and board tile, and a single Task can be filed under a Work while also carrying a Mission or an Idea association — the three are additive, not one owner you have to choose between.
Everything the board, the filters, and the Agent that runs it need — set once on the create form at /tasks/new.
A title of up to 200 characters — Create stays disabled while it is blank — and free-text description you can edit inline afterwards. A description that looks like it contains an API key is rejected: credentials belong in plugin settings.
Five levels, defaulting to P3. Priority is a filter and a label, not a queue: every list is sorted most-recently-updated first, so P0 pulls the eye without silently reordering anyone’s work.
The Labels field mirrors the slugified title as you type — “Redesign onboarding flow” becomes redesign-onboarding-flow — and stops mirroring for good the moment you type your own. Every label is capped at 80 characters.
Up to 20 commands that must exit 0 before an Agent’s work counts as finished, plus a Max gate attempts picker — Inherit from Work, or 1–5. Leave the section empty and the Task inherits the Work’s defaults.
Pick a Work on the form; Mission and Idea associations arrive when you create the Task from that Mission’s or Idea’s Tasks tab. All three can be set at once, and the Work is re-filable later from the detail page.
Files can be attached to a Task that is filed under a Work. On an unscoped Task the upload control is disabled — so pick the Work up front if you plan to attach anything.
Seven columns — Backlog, Todo, In Progress, In Review, Blocked, Done, Cancelled — and a strict lattice behind them: a move the state machine does not allow simply refuses the drop.
Go to /tasks → New Task. Every new Task lands in Backlog with its own slug — the form has no status picker, so nothing starts by accident.
Run hands the Task to an Agent, resolving in order: the one you pick, an Agent assignee, the Task’s own Agent, then the Work’s default. When every slot is busy the run is accepted and parked — “Queued — waiting for capacity” — and starts when one frees.
The acceptance checks run for real against the Task’s isolated workspace. A red gate hands the failure output back to the Agent to fix, inside the attempt budget you set — then stops rather than looping.
The card carries a pull-request status pill and a ± diff affordance that opens a preview of the branch’s changes. Your merge policy decides whether the Agent may land it or a human does.
Drag cards between columns, or use Move → for the same legal destinations as a menu. Run all sits in the Backlog, Todo and In Progress headers and dispatches up to 20 Tasks from the top of that column, each reporting its own outcome.
Any Task can parent others. Type a title in the Sub-tasks section and press Add; the checklist keeps an n/m done counter, and each child shows its status, an Agent chip per agent assignee, and an approval badge when it has approvers.
Promote a Task to recurring — Daily, Weekly, Monthly or a custom RRULE, with an optional end date and a maximum of 1–9999 occurrences — and each occurrence spawns a fresh instance. Or arm a single Scheduled run at an exact time.
Browse templates at /tasks/templates: Use template pre-fills /tasks/new with a ready title, description and labels. Workflow templates go further, expanding a parent Task plus one sub-task per step — with blockers, bound Agents and approval steps — in one transaction.
The Triggers tab turns something happening outside the platform into work inside it. A trigger listens on its own signed webhook URL or on an ingested platform event, creates a Task on every verified delivery, assigns it to the Agent you nominated, and can start the run immediately.
Every Task has a thread. @mention an Agent by slug and the reply arrives as a real run against the Task — not a comment — so the conversation and the work stay in the same place.
Some of the Task model is reachable only through the API today. We would rather say so than let you discover it after you have built a process around a button that does not exist.
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 →Declare the checks a change must pass. The platform runs them for real — and a red check opens no pull request.
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 →Named AI employees — a CEO, a CTO, a Researcher — that run your Missions, Ideas, and Works around the clock.
Learn more →Work refreshes, Mission ticks, Agent heartbeats, recurring Tasks and webhook triggers — every clock and every hook in one Schedules view.
Learn more →Decide which agent actions run on their own, which wait for a human, and how much any of it may spend — then approve from the dashboard or the Inbox.
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.