Journal · February 2026
February 2026: FORGE, an agent runner for Jira tasks
- Covers:
- Last updated:
- Releases:
- 13
- Versions:
- 1.0.0 → 1.4.0
- Release days:
- 5
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.
What shipped
- v1.0.0 (18 Feb): first release. A Jira webhook puts the task in a Redis queue, and the orchestrator agent MAX delegates to FINN (code), VERA (tests), LENA (pull request), DUKE (deployment), SAGE (documentation) and RAY (notifications).
- v1.1.0 to v1.1.3: the agents' work became visible live, with streamed output of the orchestrator in the admin UI.
- v1.2.0: admins can cancel, stop, kill and delete a running job.
- v1.2.2: authentication and network access were hardened.
- v1.3.0: every job runs in its own Git worktree, and failed CI runs are retried automatically.
- v1.3.1: review comments on GitHub and Bitbucket pull requests start a fix run.
- v1.4.0: every job gets an AI-written summary, with performance metrics per agent.
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 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 alternative