Tasks 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 chapterJournal
What changed in Crew, month by month
Crew ships small and often: 992 releases between 18 February and 23 October 2026. This journal sums up each month in plain words, taken from the changelog, so you can see what exists today and how it got there.
RSS feedCrew in 9 months
- releases
- 992
- months
- 9
- days with a release
- 135
- tickets referenced
- 482
- from first to latest version
- 1.0.0 → 5.412.1
Month by month
· 151 releases · 5.343.0 → 5.412.1
October 2026: runs with gates, Focus and a Claude plugin
October brought the largest change to how agents work in Crew: runs that stop at human gates before anything is released. Around it came seven languages, a redesigned Gantt, Focus and Notebook, dashboards and an MCP server, so Claude can work with Crew directly.
Read the chapter· 187 releases · 5.230.0 → 5.342.1
September 2026: notes, planning, Missive and live editing
September brought Crew closer to the individual: personal notes, four daily priorities, colour schemes and a week planner. Crew got public pages with videos and a privacy policy, a Missive panel turns emails into tasks, and planning notes can be edited by several people at once.
Read the chapter· 19 releases · 5.218.0 → 5.229.3
August 2026: fixes, Jira status sync and a wiki in Crew
August was the quietest month, with 19 releases from 12 August on. Most of them fixed what daily use had shown: notifications, Jira statuses and task keys. One new feature stood out, a read-only Outline wiki inside projects and clients.
Read the chapter· 53 releases · 5.196.5 → 5.217.1
July 2026: Slack, a planning timeline and PDF reports
July was shorter, with releases until 17 July. Crew got a Slack app and a timeline that shows all projects on one Gantt. Deployments by agents are now verified and rolled back when the health check fails.
Read the chapter· 208 releases · 5.92.15 → 5.196.4
June 2026: deployments, a feedback widget and Teams
June was about getting work out of Crew and feedback back in. Agents learned to check whether a project is ready to deploy and to provision servers, with production access limited to named people. Clients can report bugs from their own website and use the portal inside Microsoft Teams.
Read the chapter· 283 releases · 5.2.5 → 5.92.14
May 2026: Jira sync, time sheets and a real client portal
May was the month real teams moved in. Jira projects stay in sync continuously, time is logged and approved in Crew, and planning meetings got their own module. At the end of the month the client portal grew from a view into a place where clients work on their tasks.
Read the chapter· 43 releases · 4.1.0 → 5.2.4
April 2026: the name Crew, task types, Gantt and Jira import
In April FORGE became Avidia Crew at crew.avidia.ai. Version 5.0 brought the project management a team needs to leave Jira: task types, a hierarchy, releases and a Gantt timeline. A seven-step wizard moves existing Jira projects over.
Read the chapter· 35 releases · 1.5.0 → 4.0.1
March 2026: from agent runner to a platform for teams
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.
Read the chapter· 13 releases · 1.0.0 → 1.4.0
February 2026: FORGE, an agent runner for Jira tasks
Crew did not start as a project tool. On 18 February 2026 FORGE 1.0 went live: a server that takes a labelled Jira task from a queue and hands it to a team of AI agents. The rest of the month was about seeing and controlling what those agents do.
Read the chapter
The main features
What the nine months added up to, in short.
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 chapterClient portal
Clients see their own projects, tasks, timeline and, if allowed, hours and costs. They create and comment on tasks in the browser or in Microsoft Teams.
About the client portalPlanning and timeline
A Gantt timeline across all projects with milestones, dependencies and scales from week to year. Planning meetings have a live view and a resource planner.
July 2026 chapterTime tracking and timesheets
Log time on any task, see it per project or in a calendar, and lock and approve months. Hours sync with Jira and Tempo, and reports come out as PDF.
May 2026 chapterDocuments and open links
Folders for files and agent output, with previews for PDF, Office, images and video. An open link shares one document without a login and shows its title when pasted.
October 2026 chapterFocus and Notebook
Focus plans today, the week and the review with up to four priorities a day. Notebook keeps notes next to projects and meetings and turns them into tasks.
October 2026 chapterJira sync, API and MCP
Jira projects can be imported once or kept in two-way sync, so a team can move over step by step. A documented v1 API and an MCP server let tools and Claude work with Crew.
Crew as a Jira alternativeHosting and data ownership
Made in Switzerland by Netgen Switzerland AG with two server locations, Germany and Switzerland: hosting in Switzerland on request is no problem, and so is on-premise. Own AI models and your own mail server are possible. The public site uses no analytics or tracking pixels.
Data ownershipVideos
Short walkthroughs of the features above.
Source: the Crew changelog. Version numbers refer to releases on crew.avidia.ai.