Journal · March 2026
March 2026: from agent runner to a platform for teams
- Covers:
- Last updated:
- Releases:
- 35
- Versions:
- 1.5.0 → 4.0.1
- Release days:
- 12
In March the agents learned to ask before they guess, and each project got its own isolated container. At the end of the month version 3.0 turned the runner into a platform: teams, tasks that live in Crew itself, configurable agent pipelines and a first client portal.
What shipped
- v1.5.0: interactive jobs. An agent can stop and ask a question, answered in a chat in the UI or as a Jira comment. Each project can get its own LXD container.
- v1.7.0: duplicate Jira webhooks are collapsed into one job, and a budget monitor alerts, switches to a cheaper model or pauses when costs run high.
- v1.9.0 and v2.0.0: a priority queue for hotfixes, no two jobs on the same repository at once, and agent stages that run in parallel, shown as a pipeline in the job view.
- v2.1.0: inside the container Crew detects the project's stack, installs dependencies, builds and starts the app on its own.
- v2.3.0: scheduled tasks on a cron schedule, structured event logging and a watchdog for stalled jobs.
- v3.0.0 (25 Mar): teams, built-in tasks, configurable agent pipelines, artifact storage and preset team templates.
- v3.4.0 to v3.7.0: full-text search, recurring tasks, saved filters, roles and permissions, sprints, a first Gantt view and a first client portal.
- v4.0.0: a Documents section and project visibility by group.
Watch
Features
AI agents and run gates
Agent teams write code, test it, open pull requests and deploy in isolated containers. Crew Runs stop at gates where a person approves before anything is released.
October 2026 chapterTasks and boards
Task types, a hierarchy from epic to sub-task, workflow schemes and kanban boards with swimlanes. Moving a task between projects keeps its old key working.
April 2026 chapter