Releases
What’s new in aitasks? Each release post highlights the most notable changes in plain language. For full technical details, check the linked GitHub release notes.
v0.20.1 Release
Sunday, May 10, 2026 in Releases
A quick maintenance release. The nfpm GitHub Action we relied on for building Debian and RPM packages was deleted upstream, which broke our release pipeline. v0.20.1 swaps it for a direct Docker invocation of the same tool, so .deb and .rpm packages …
v0.20.0: Install via your distro's package manager, A dedicated syncer TUI, and Opt-in PyPy fast-path
Wednesday, May 06, 2026 in Releases
v0.20.0 is a big one — a brand new sync TUI, package-manager installs across four ecosystems, an opt-in PyPy fast-path that makes the long-running TUIs noticeably snappier, and a wave of polish across brainstorm. Install via your distro’s …
v0.19.2: Python wrappers that actually stay inside the venv, Warnings before you build on stale main, and Source-tree setup gets the starter tmux config too
Wednesday, April 29, 2026 in Releases
v0.19.2 is a reliability-focused release for the everyday setup and release workflows. It fixes a few sharp edges around Python environments, tmux setup, macOS docs, and stale task data during changelog generation. Python wrappers that actually stay …
v0.19.1: Releases and changelogs no longer miss remote tasks, and macOS test suite is back at parity with Linux
Tuesday, April 28, 2026 in Releases
v0.19.1 is a quick follow-up to v0.19.0 with two reliability fixes you’ll appreciate if you contribute to aitasks itself or develop on macOS. Releases and changelogs no longer miss remote tasks If you cut a release while local main was a few …
v0.19.0: A modern Python venv that installs itself, `ait setup` on a fresh clone, polished end-to-end, Brainstorm: fewer crashes, and more visibility
Tuesday, April 28, 2026 in Releases
v0.19.0 is mostly an infrastructure release — the Python venv story, ait setup on a fresh clone, and brainstorm stability all got a lot of attention. There’s also a new audit-wrappers skill that closes a recurring drift class. A modern Python …
v0.18.3: Brainstorm agents run interactive by default, Brainstorm sessions that don't get stuck, and MissedHeartbeat is gone (and that means a small migration)
Monday, April 27, 2026 in Releases
v0.18.3 is mostly a brainstorm release — the TUI got a lot more transparent and a lot more resilient when things flake out. The agent-crew state machine also took a small but breaking turn. Brainstorm agents run interactive by default Every …
v0.18.2: Multi-session stats in the TUI, Monitor and minimonitor handle cross-session agents correctly, and Agent crews that recover instead of erroring out
Sunday, April 26, 2026 in Releases
v0.18.2 is mostly a polish release for multi-session — stats picks up every session you’ve got, and the monitor finally stops mixing up which project a foreign-session agent belongs to. Agent crews and brainstorm sessions also got a lot more …
v0.18.1: Triage manual-verification checklists in batches, Filter the board by issue type, and `ait upgrade` actually upgrades branch-mode setups now
Sunday, April 26, 2026 in Releases
v0.18.1 is a polish-and-fix release. The headline changes are a faster manual-verification flow, a new issue-type filter in the board, and a fix for branch-mode upgrades that were silently leaving framework files uncommitted. Triage …
v0.18.0: Your monitor and minimonitor now see every project at once, The TUI switcher teleports across sessions, and `ait install` is now `ait upgrade`
Friday, April 24, 2026 in Releases
v0.18.0 is the multi-session release. If you keep two or three aitasks projects open in separate tmux sessions, every TUI now sees them all at once instead of pretending only the current session exists. Your monitor and minimonitor now see every …
v0.17.3: Task IDs now start at 1, Tmux targeting no longer confuses sibling projects, and `ait setup` adds `__pycache__/` to `.gitignore`
Thursday, April 23, 2026 in Releases
v0.17.3 is a small bug-fix release — three quality-of-life fixes aimed at people running the framework across multiple projects or starting fresh ones. Task IDs now start at 1 New projects used to begin at t10 because of a buffer that made room for …