What one Mac productivity app actually shipped in 14 days
Every roundup of productivity app updates in April 2026 lists the same six tools. This guide does the opposite. It walks the full changelog of one Mac productivity app (Fazm) between April 3 and April 16, 2026, release by release, and shows what the month really looked like on the inside: nine numbered ships, one pop-out window saga, one protocol upgrade, and a lot of tiny regressions that never make it into marketing copy.
Versions Fazm shipped between April 3 and April 16, 2026
Why walk one changelog instead of six
If you search for productivity app updates in April 2026, you get the same shape of article every time: Notion shipped X, Todoist shipped Y, Linear shipped Z, Microsoft 365 has a release wave, the end. Those roundups are fine. They are also interchangeable.
The part those pieces skip is the actual texture of productivity app development in April 2026. A product ships. The ship breaks something adjacent. The next release fixes the break. Five ships later, the original feature actually works. That pattern is what shipping a productivity tool looks like right now, and no roundup captures it, because the roundup only quotes the press-ready summary of the headline release.
So this guide does one thing well instead: it reads the full public CHANGELOG.json of one Mac productivity app and narrates the month in the order it actually happened.
The pop-out window saga, in five releases
Most productivity apps this month added a way to pop their AI chat into its own window. The marketing copy on each one is one sentence. The real cost shows up in the week after. Here is what five consecutive Fazm releases did to one feature.
v2.0.1 (Apr 3): the pop-out button ships
Added pop-out button to open chat in a separate window that behaves like a normal Mac window. Default chat window also made 30% wider and 50% taller. Push-to-talk mic button added next to Send.
v2.0.6 (Apr 4): window restoration
Detached chat windows now restore automatically after app restart or update. Fixed stuck loading spinner when popping out chat mid-stream. Fixed detached window losing responses after the first query. Fixed floating bar not starting a fresh chat after popping the conversation out.
v2.1.3 (Apr 9): pop-out error visibility
Fixed error messages not showing in pop-out chat window. This is the class of bug where the window exists, the API fails, and the user sees nothing. Easy to miss in QA, brutal in production.
v2.2.0 (Apr 11): global shortcut + restore fix
Added global shortcut Cmd+Shift+N to open a new pop-out chat window from anywhere. Fixed pop-out windows not restoring after app update or restart (second iteration of the v2.0.6 fix, more thorough).
v2.2.1 (Apr 12): duplicate response fix
Fixed duplicate AI response appearing in pop-out and floating bar when sending follow-up messages. Classic regression: the new window class subscribed to both streams.
v2.3.2 (Apr 16): stream isolation
Fixed AI responses leaking between pop-out chat windows when streaming simultaneously. Also tightened onboarding copy from nothing leaves your device to local-first, since the first phrase overstated the privacy guarantee.
“One feature. Six follow-up releases over two weeks to make it actually work across app restart, update, error surfacing, global shortcut, duplicate responses, and simultaneous streams. That is a productivity app shipping in public in April 2026.”
Fazm, CHANGELOG.json versions 2.0.1 through 2.3.2
Where this data comes from
There is no blog post behind this guide. There is one file in the source repo. Every release string quoted here maps back to one entry in CHANGELOG.json. Here is the shape of a single release entry, copied verbatim from the repo.
Nothing summarized, nothing spun. One release, eight shipped changes, one new global shortcut, and a founder-chat crash loop fix that anybody reading press releases would never know existed.
The April 7 protocol upgrade nobody wrote about
The single highest-leverage change in the April window was not a user-visible feature. It was v2.1.2 on April 7, which upgraded the Agent Client Protocol between the Swift app and the tool- calling LLM bridge to v0.25.0. That unlocked two downstream fixes in the same release.
If you are writing about productivity app updates in April 2026, this is the release shape to notice. Headline productivity app roundups list features. Actual April velocity shows up in the plumbing: a protocol jump, two silent failure modes turned into visible errors, and a mobile tunnel reconnection path that finally survives a desktop app restart.
Full April 2026 changelog, release by release
Nine Fazm releases, in reverse chronological order. Every bullet is copied verbatim from CHANGELOG.json, lightly trimmed for readability where a line referenced an internal component.
Privacy language + streaming isolation
- Tightened onboarding and system prompts to say local-first instead of nothing leaves your device
- Fixed AI responses leaking between pop-out chat windows when streaming simultaneously
- Fixed onboarding chat splitting AI messages into multiple bubbles
Pop-out duplicate response fix
- Fixed duplicate AI response appearing in pop-out and floating bar when sending follow-up messages
Global shortcut + custom API endpoint
- Added global shortcut Cmd+Shift+N to open a new pop-out chat window from anywhere
- Added custom API endpoint setting for proxies and corporate gateways
- Fixed pop-out windows not restoring after app update or restart
- Fixed suggested replies persisting after starting a new chat
- Fixed typing indicator flickering during network retries with a 600 ms debounce
- Fixed founder chat crash loop on repeated rate limit failures
Manage Subscription + pop-out errors
- Added Manage Subscription button in Settings for Fazm Pro subscribers
- Fixed error messages not showing in pop-out chat window
- Fixed follow-up messages replacing previous user messages when sent during a stuck loading state
ACP v0.25.0 protocol upgrade
- Upgraded ACP protocol to v0.25.0 with improved error handling for credit exhaustion and rate limits
- Fixed onboarding silently failing when credits run out, now shows an error with options to connect Claude or skip
- Fixed mobile web app failing to connect when desktop tunnel restarts
Credit-exhausted error surfacing
- Fixed error messages not showing when Claude credits are exhausted
- Added scroll-to-bottom button in chat when scrolled up
Claude model fallback + browser tabs
- Fixed chat failing silently when personal Claude account lacks access to the selected model, now auto-falls back to built-in account
- Fixed browser agent ignoring already-open tabs when navigating to websites
- Fixed voice input silently failing when transcription times out, now shows error feedback
Detached chat + Smart/Fast toggle
- Chat observer cards are now auto-accepted (deny to undo) instead of requiring manual approval
- Detached chat windows now restore automatically after app restart or update
- Fixed stuck loading spinner when popping out chat to detached window mid-stream
- Fixed detached chat window losing responses after the first query
- Fixed AI agent accidentally typing its reasoning into user documents when controlling desktop apps
- Added Smart/Fast model toggle in the chat header bar for quick switching between Opus and Sonnet
- Fixed floating bar not starting a fresh chat after popping the conversation out to a detached window
- Fixed chat view jumping around during AI response streaming
Pop-out chat window ships
- Added pop-out button to open chat in a separate window that behaves like a normal Mac window
- Made the default chat window 30% wider and 50% taller
- Added push-to-talk microphone button next to the send button in chat input
- Improved knowledge graph performance: capped visible nodes to 100, debounced updates, and replaced text rendering with lightweight textures
- Fixed send button and observer cards not visible in light mode
- Fixed detached chat window not streaming AI responses
- Redesigned paywall to show all upgrade options as equally visible cards with inline pricing
- Fixed crash on Intel Macs caused by Sparkle framework code signature validation failure
What the month was really about
Clustering 14 days of shipped changes by what they were trying to fix, rather than by release number.
Pop-out chat windows
The biggest theme. Ships in v2.0.1, window restoration in v2.0.6, error visibility in v2.1.3, global shortcut in v2.2.0, duplicate response fix in v2.2.1, cross-window stream isolation in v2.3.2. Six releases over 14 days on one feature.
ACP v0.25.0 upgrade
April 7 plumbing jump. Moved the bridge between the Swift app and the tool-calling LLM to a new protocol version, unlocking proper error surfacing for credits and rate limits.
Credit-exhausted surfacing
Three separate April releases touched this (v2.0.9, v2.1.2, v2.1.3). The target: no more silent stalls when a user runs out of Claude credits mid-session.
Mobile tunnel reliability
v2.1.2 fixed the mobile web app failing to reconnect when the desktop tunnel restarts. Small change, large impact for anyone driving Fazm from their phone.
Smart/Fast model toggle
v2.0.6 added a quick switch between Opus and Sonnet in the chat header. One of the few purely additive UX shipments in the month, everything else was fixing regressions from v2.0.1.
Privacy copy correction
v2.3.2 tightened onboarding language from nothing leaves your device to local-first. That phrasing overstated what the product actually guarantees. Good habit, worth noting.
Why Fazm could ship nine releases without regressing latency
Shipping every 36 hours is easy to say and hard to do without breaking things. One architectural decision from the previous month kept April's cadence sane: Fazm reads the screen through macOS accessibility APIs, not screenshots. That switch landed in v1.5.0 on March 27 and held through every April release.
Three lines. The return value is typed. No OCR, no vision model, no frame capture. When you are pushing nine ships in two weeks and one of them is a protocol upgrade, the last thing you want is a screen-reading path that depends on model weights you also need to keep current. Accessibility APIs are how the cadence stays cheap.
Why this matters for April 2026 productivity tools in general
Every productivity app adding AI this month has to pick a way to read the screen. The choice shapes what their April changelog looks like. Here is the tradeoff.
| Feature | Screenshot-based agents | Accessibility tree (Fazm) |
|---|---|---|
| Latency per frame | ~200 to 500 ms on M-series | Microseconds |
| Works across any native Mac app | Yes | Yes |
| Element roles and state (focused, enabled) | Inferred from pixels | Returned typed from the OS |
| Cost of a weekly ship | Vision model tied to app release | No model regression risk |
| Works inside a Qt or Flutter canvas | Yes | No (empty AX tree) |
| Consumer-friendly app, not dev framework | Usually a framework | Yes |
April 2026 in three numbers
Numbered releases shipped between April 3 and April 16, 2026. Roughly one ship every 36 hours.
Consecutive releases that touched pop-out chat windows, one feature cycling through add, restore, error surfacing, shortcut, duplicate fix, stream isolation.
Debounce added in v2.2.0 to stop the typing indicator from flickering during network retries. The kind of detail marketing copy never mentions.
The rest of the productivity category in April 2026
For context, here is the shape of what else shipped in the same window, compiled from the top productivity app roundups indexed this month. This is the shallow version; each line is worth a page of its own.
- Notion: voice input on desktop, shareable AI chat links, muted discussion replies, four new page cover art collections, database tab display options, markdown comment bodies in the Create Comment API.
- Todoist: AI-powered views that rebuild your task list on the fly based on a natural-language prompt.
- Linear: automation rules handling sub-issue cascades that previously required manual intervention.
- Fantastical: AI scheduling suggestions that analyze your calendar patterns and recommend meeting times based on focus-block history.
- Coda: column formulas from natural-language descriptions.
- Microsoft 365: Power Apps 2026 release wave 1 live, plus enhanced Gemini email proofreading in Gmail for Workspace accounts.
- Zoho Projects: Zoho Projects Infinity with custom modules, reports, dashboards, and deeper AI hooks.
- Claude Desktop: a major April 14 release per Anthropic's social posts.
- Fazm: the nine releases covered in this guide.
Why this picture is worth caring about
Productivity app updates in April 2026 look like big features on the outside and a lot of small regressions on the inside. The indie ones move faster than the platforms. A single two-week window on one Mac app produced nine ships, one protocol upgrade, and six releases chasing one pop-out chat feature. That is the honest shape of the month.
Fazm is the consumer app for Mac automation and AI chat across any app on your machine. It reads real accessibility APIs (not screenshots), it works with any native macOS app, and it ships in public: CHANGELOG.json is the source of every claim on this page. If you want a productivity tool whose April 2026 ship list you can verify in one file, start here.
Try the app behind this changelog
Fazm is a consumer-friendly Mac app, not a developer framework. Runs against real accessibility APIs, works with any app you have open, ships every few days in public.
Download Fazm →Frequently asked questions
What productivity app updates actually shipped in April 2026?
Many tools pushed updates in April 2026. Notion released voice input on desktop, shareable AI chats, and database tab customization. Todoist introduced AI-powered views. Linear added sub-issue cascade automation. Fantastical added AI scheduling suggestions. Microsoft 365 released Power Apps 2026 wave 1. The Claude desktop app also shipped a major April 14 release. This guide goes deeper on one app in that group, Fazm, because its public changelog.json lists nine numbered releases between April 3 and April 16, which makes it a cleaner case study for what weekly shipping on a Mac productivity app actually looks like in April 2026.
Which productivity app shipped the most releases in April 2026?
Hard to rank across the full category, but one concrete data point: Fazm shipped nine numbered versions between April 3 and April 16, 2026. That is v2.0.1, v2.0.6, v2.0.7, v2.0.9, v2.1.2, v2.1.3, v2.2.0, v2.2.1, and v2.3.2. The cadence averaged roughly one ship every 36 hours. Most ships were bug-fix dominated, not feature-dominated, which is a useful pattern for anyone writing about April product velocity across the category.
What is the ACP protocol and why did Fazm upgrade to v0.25.0 in April 2026?
ACP stands for Agent Client Protocol. It is the JSON-RPC format Fazm uses between the Swift app and the tool-calling LLM bridge. On April 7, Fazm shipped v2.1.2, which upgraded the bridge to ACP v0.25.0. The release notes specifically call out improved error handling for credit exhaustion and rate limits. Before that version, onboarding could silently fail when credits ran out, and the mobile web app failed to reconnect when the desktop tunnel restarted. Both were fixed in the same release. This is the kind of plumbing change that does not show up in marketing copy but is exactly what users feel as fewer dead loops.
What was the pop-out window architecture thread in Fazm's April 2026 releases?
Five separate April releases touched pop-out chat windows, each one fixing a different edge case. v2.0.1 on April 3 added the initial pop-out button. v2.0.6 on April 4 made detached windows restore automatically after app restart or update. v2.2.0 on April 11 added the global shortcut Command Shift N to open a new pop-out from anywhere, plus fixed pop-out windows failing to restore after an app update. v2.2.1 on April 12 fixed duplicate AI response bubbles in pop-out and floating bar on follow-up messages. Finally, v2.3.2 on April 16 fixed AI responses leaking between pop-out chat windows when streaming simultaneously. That is the shape of most real productivity app release cycles: one feature, four follow-up releases to make it actually work.
What is the difference between screenshot-based automation and accessibility API automation?
Screenshot-based agents capture the screen as a PNG and ask a vision model to describe what is on it. Accessibility API automation reads the OS's built-in structured tree (AXUIElement on macOS) directly. Fazm switched from browser screenshots to native accessibility APIs in v1.5.0 on March 27, 2026, and carried that architecture forward through all of April. The code that does this lives in Desktop/Sources/AppState.swift around line 439 where AXUIElementCreateApplication(frontApp.processIdentifier) runs, then AXUIElementCopyAttributeValue queries kAXFocusedWindowAttribute. That returns typed element data (roles, titles, values, positions) in microseconds, with zero model inference cost, which is why April release cadence could stay high without regressing latency.
Why did so many April 2026 productivity apps focus on AI chat pop-outs?
Because once an AI assistant is in a productivity app, the UX fight is no longer about whether it works. It is about where it lives. Docked sidebars get in the way. Floating bars get dismissed. A proper pop-out window that behaves like a first-class Mac window, restores after restart, has its own global shortcut, and does not leak responses across instances, ends up being the shape users actually want. Fazm's April 2026 changelog shows the cost of getting that right: five releases, multiple regressions, duplicate-response bugs, stream leakage. The pattern is visible across the category in April 2026.
Which April 2026 productivity app updates are actually automatable?
Most headline features this month are desktop UI only with no public API. Notion's voice input, shareable AI chats, and database tab display live in the desktop or web UI. Linear's sub-issue automation is API-accessible. Fantastical's AI scheduling is private. On macOS, the accessibility tree is the universal fallback: any productivity app that renders native controls exposes them through AXUIElement, which means Fazm can click, type, and read from those controls regardless of whether the vendor shipped a public API. That is how a single Mac productivity app can stay useful across all the other April 2026 updates.
Where does Fazm store its release log?
In the source repo at CHANGELOG.json. Each entry has a version, a date, and a flat array of change strings. The April 2026 entries are on versions 2.0.1 through 2.3.2, with dates April 3 through April 16. The file is the canonical source for everything in this guide. No release notes, blog posts, or press coverage were used. Reading the changelog directly is the cleanest way to see what a productivity app actually shipped, versus what its marketing copy claims.
Shipping a productivity app is not about the big release.
It is about the six follow-up releases that make the big release actually work. April 2026 was that story for Fazm. Come try the result.
Try Fazm free
Comments
Public and anonymous. No signup.
Loading…