What shipped, as it shipped. Warden moves fast — the agents insist.
Two new first-class trackers, both connected with one OAuth click — no API keys to paste.
GitLab imports issues per project and syncs status through labels, alongside the existing merge-request support. Notion imports any database as a backlog: a per-database property picker maps your status, assignee, and label properties onto Warden's board, so pages move columns as runs progress.
Personas are reusable agent identities — a name, icon, color,
and system prompt kept in .warden/persona/ — that any
prompt step can put on. Your spec writer and your implementer no longer
have to sound like the same agent.
Phases can now publish design artifacts: the agent renders previews of what it built (screens, diagrams) and Warden delivers them to your review surfaces — the gate, Slack, the tracker.
GitHub Projects (v2) boards are a tracker of their own, with real status columns — where plain repo issues only know open and closed.
Warden is now multi-tenant: sign up with email, GitHub, or Linear; create an organization; invite your team with a link. Admins manage members and roles from the web, and every run, task, and connector is scoped to its org.
Connector management moved into the editor's Settings hub, and tracker boards now mirror the real task board — including tasks currently owned by a run.
The backlog now holds tasks from multiple trackers and manual tasks at once, each keeping its origin, priority, assignee, and labels. Imported issues route to a workflow by label/assignee rules you edit next to the tracker.
In-editor code review shipped alongside: leave native review comments on a run's diff and submit them as a "request changes" rework — any time, not just at a gate.
Warden's source also went public under the MIT license.
Runs open a draft pull request when work starts and mark it ready as it lands; branches derive from the task, so a run's history reads like a teammate's. The live session shows the exact prompt each phase sent, friendlier markers for git steps, per-phase model and reasoning-effort chips, and one-click checkout of the committed branch.
Trackers push changes in over webhooks, so imported tasks stay live without polling delays — and can auto-start a run on arrival (opt-in). Statuses became per-origin: each tracker's own columns sync natively, with no translation table, and workflow phases can reference them in status automation.
A workflow phase can declare onStatus — the board column
that triggers it — and setStatus — where the task moves when
the phase lands. Drag a task to "In Progress" and the right phase starts;
when it finishes, the card moves on. The board becomes the control
surface.