Releases
What's new
A clear summary of what changed in each MaulTeam.app release.
First time here?
Maul Team coordinates a small group of AI agents that plan a Sprint, implement backlog
items, review the code, and demonstrate the result. As Product Owner, you
decide what to build and whether to accept it. You can use the Mac app or run the same
workflow from the terminal.
- Sprint
- A round of work with a defined goal. The team plans it, builds it, and then demonstrates the result.
- PBI
- A single item on the to-do list — “add a login screen”, “fix the CSV export”.
- Scrum Master · Developer
- The agent roles. The Scrum Master coordinates the plan; Developers write and review the code.
- The framework
- The free, open-source workflow used by the agent team. It is included in the Mac app, so app updates can also update the workflow.
Download for macOS
September 6, 2026
·
v2.0.12
Latest
New
Improved
Fixed
The audit remembers, and guards must be able to fail
MaulTeam now remembers every kind of problem its periodic project-wide review has ever found, so nothing comes back under a new name — and the kinds a script can catch are turned into checks that stop them returning at all. Checks themselves are held to the same standard: they have to be shown failing before the team trusts them.
- The review remembers what it has already found. The periodic read-through of the whole project now keeps a running list of every kind of problem it has ever seen, so the same one is never filed again under a new name, and every place a problem turns up is recorded as a proper list instead of buried in prose. Where a kind of problem can be caught by a script, the team writes that check and wires it into the gate that lets finished work in — anything that brings the problem back is stopped right there, and a check that is itself broken fails loudly instead of quietly passing. A problem counts as guarded only once that gate has been seen to run.
- Reviews now show their evidence. When a design review claims that something you asked for is not covered, it has to quote your wording, say what it searched for and what it found. And it reads what you asked for from the to-do list itself, never from someone else's summary of it.
- A check has to prove it can fail. Anything the team delivers as a test, a check or an alarm is now demonstrated twice: once with the fault deliberately put back, to show it is caught, and once with the fault gone. A check that cannot be made to fail on demand is not accepted.
- The team's own records are protected from anywhere. The safeguards that stop those records being edited by hand now locate the project root wherever they are run from, so they hold inside a sub-folder of a package or a per-item working copy — places where such edits used to slip through unnoticed. When the root cannot be found, they refuse to judge rather than guess.
- It runs everywhere it says it does. The documented one-line start command now works on Linux, where it used to stop immediately. On the release side, the step that gets the Mac app cleared by Apple retries when the network hiccups instead of failing the build, and every test suite now runs before a release goes out.
Full technical notes on GitHub ↗
September 6, 2026
·
v2.0.11
New
Improved
Fixed
Simpler coordination and fewer false warnings
The Scrum Master now uses shorter instructions and delegates routine work to two assistants. Progress checks were also adjusted to avoid interrupting work that is still active.
- Shorter Scrum Master instructions. Two new assistants handle research and routine ceremony steps so the Scrum Master can focus on coordination.
- More specific status messages. The status line now shows whether an agent is planning, designing, building, or reviewing instead of showing only “busy.”
- Longer review timeout. Reviews can remain quiet while an agent reads the work, so the warning threshold increased from ten to thirty minutes. Warning messages now identify what the agent was waiting for.
- Pending documentation updates no longer stop a task. When a design changes during a Round, documentation that has not caught up is no longer treated as a conflicting code change.
- Blocked items no longer prevent Sprint completion. A Sprint can now close when an item is waiting on an external dependency.
- Full audits now run every third Sprint. Other Sprints use a lighter cross-review, reducing repeated repository scans.
Full technical notes on GitHub ↗
August 9, 2026
·
v2.0.10
Fixed
Improved
More reliable progress checks
MaulTeam now judges more accurately whether active work is progressing or stalled. This reduces false warnings and makes status messages easier to trust.
- Activity timing is now measured consistently across the app.
- Work with no recorded activity is clearly identified instead of showing a misleading idle time.
- Already-merged updates no longer appear as changes in active work.
Full technical notes on GitHub ↗
August 8, 2026
·
v2.0.9
New
Improved
Review findings now require your approval
The end-of-Sprint review now grades each finding, explains it, and asks for your decision before creating work. Rejected findings remain dismissed unless their severity increases.
- Findings include a severity grade. Each finding is classified as a behavior problem, technical debt, or an optional improvement, and you see the full list before any PBIs are created.
- Rejected findings remain dismissed. Later reviews do not raise them again unless the issue has become more severe.
- Design documents describe the current system. Change history moves to the decision log, and reviews flag historical notes left in specifications. The team asks you to resolve ambiguous specifications.
- Retrospectives can produce framework feedback. The team can prepare a report for the Maul Team project, remove project-specific details, and check it for names, identifiers, and paths. It sends the report only with your approval.
Full technical notes on GitHub ↗
August 2, 2026
·
v2.0.8
Fixed
Reliability fixes for safeguards and updates
This release fixes safeguards that were reported as active but were not being applied. It also repairs cross-model review, project updates, and several causes of stalled or repeated work.
- Design document protections are enforced. Edits from unauthorized roles are now rejected, and the document catalog remains read-only.
- Cross-model reviews run in app-created projects. The reviewer can now find the required file instead of incorrectly reporting that the second model is unavailable.
- Older projects are repaired during updates. Projects created before earlier updates are migrated automatically the next time they open.
- Quality checks report when they cannot run. The check for justified skipped code now examines the code or reports that it could not complete the check.
- Fewer stalls and duplicate assignments. Several paths that could leave agents waiting or reassign completed work have been fixed.
Full technical notes on GitHub ↗
August 2, 2026
·
v2.0.7
New
Project tabs and response notifications
You can now switch between running projects with tabs. The app also notifies you when a team needs your response.
- Tabs for running projects. Every project with a live team shows up as a tab at the top of the window. Click to switch; the others keep working in the background. The × stops a project's team — after asking you first.
- Notifications show when a response is needed. The project tab displays an orange badge. If another tab is open, a macOS notification shows the question and opens the relevant project when clicked.
- Long-running projects open faster. A history check now runs in one pass. In a measured project with months of history, startup time fell from nearly four minutes to five seconds.
- Stalled work is restarted. A supervisor checks every ten minutes and restarts work that stopped while waiting for a missing message.
Full technical notes on GitHub ↗
July 20, 2026
·
v2.0.6
New
Reviews now find every occurrence
When a review finds a problem, it now searches the rest of the project for the same pattern so related instances can be fixed together.
- One report lists every occurrence. A finding includes all matching locations in the project, and the task remains open until each one is addressed.
- Documentation findings are grouped. Related comments and other small documentation updates now appear in one backlog item.
- This site speaks Portuguese — eight languages now.
- License wording now allows for a possible paid Enterprise plan. The framework remains free and open source, and the app remains free for personal and internal business use.
Full technical notes on GitHub ↗
July 19, 2026
·
v2.0.5
Improved
Small fixes to the team's bookkeeping
This release corrects Sprint progress tracking and escalation records, and updates the documentation for the new editor.
- Sprint progress adds up. If you drop an item from a Sprint, the progress counter no longer waits for it forever. The Sprint can reach 100%.
- Escalations include a reason and response options. When the team needs your decision, the handoff records why and provides the available choices.
- Docs and site. The app's README was rewritten for the new editor, with a fresh screenshot and updated wording in all seven languages.
Full technical notes on GitHub ↗
July 18, 2026
·
v2.0.4
New
The app updates itself
From this release on, MaulTeam.app finds new versions and installs them for you. No more downloading a disk image by hand.
- Automatic updates. With your permission, the app checks for and installs later releases, verifying each download's signature. Version 2.0.4 itself still requires a manual installation.
- Rebuilt file editor. The editor now supports syntax highlighting and opens in a separate window that you can place beside the terminal.
- View options for that editor, including indent guides.
- macOS 14 (Sonoma) or later. The app has needed this since the previous version — now the site and the README say so.
Full technical notes on GitHub ↗
July 17, 2026
·
v2.0.3
Fixed
Framework updates now reach every project
Some projects continued using an older framework after the app was updated. This release fixes the installation path and records the installed framework version so mismatches are visible.
- Install paths with spaces now work. Framework updates install correctly when the app is in the default Applications folder or another path containing spaces.
- The framework is synchronized at launch. Each launch reinstalls the framework files, migrates saved project data, and records the installed version.
- What to do. Install this version and reopen your project. The next launch syncs everything.
Full technical notes on GitHub ↗
July 16, 2026
·
v2.0.2
Improved
Housekeeping
This maintenance release updates the terminal engine and automates dependency and security update pull requests.
- The terminal you type into inside the app runs on SwiftTerm, now updated to 1.14.0.
- Dependency and security updates now arrive automatically as pull requests.
- Fixed the download counter writing to a branch it was not allowed to touch.
Full technical notes on GitHub ↗
July 16, 2026
·
v2.0.1
Improved
A friendlier first five minutes
This release adds manual update checks, a standard drag-to-Applications installer, and clearer names for the two run modes.
- Check for Updates… in the app menu. It compares your version against the latest one and takes you to the download when there is a newer one.
- Standard macOS installer. The disk image now opens with a drag-to-Applications layout instead of a file list.
- Clearer names for the two run modes. In human-in-the-loop mode, you review and guide each step. In loop engineering mode, you define the intended product and an agent Product Owner continues the workflow.
- Site and docs. The landing page now renders properly on phones, and the READMEs explain how several agents work in parallel and what code has to pass before it is merged.
Full technical notes on GitHub ↗
July 15, 2026
·
v2.0.0
First release
Maul Team, now a Mac app
The first public release adds a native Mac interface for the Maul Team framework.
- Terminal and dashboard in one window. Talk to the Scrum Master in the built-in terminal and use the dashboard to follow Sprint progress, backlog items, and agent activity.
- Opens without warnings. The download is signed and notarized by Apple, so macOS lets it run straight away.
- Install it by downloading the disk image, or with
brew install --cask maul-team.
- You will need macOS 14 (Sonoma) or later, plus Claude Code, Python 3.9+,
tmux and git.
Full technical notes on GitHub ↗
Versions before v2.0.0 came out before the Mac app existed, and covered the framework on
its own. They are still on the
GitHub releases page.
MaulTeam