Notion announcements 2026, as one continuous ladder the agent is climbing

Four dated releases across four months. January 20, 2026 was Notion 3.2: Mobile AI that matches desktop, AI note transcriptions, People Directory, and a refreshed set of AI models. February 24, 2026 was Notion 3.3: Custom Agents, fully autonomous agents that run on a trigger or schedule, free through May 3, 2026. March 20, 2026 was custom skills for Notion AI: save repeatable AI tasks as first-class commands callable from the text menu or @mention. April 14, 2026 was Notion 3.4 part 2: Workers for Agents (sandboxed code execution, 30 second wall clock and 128 MB memory cap, Enterprise only), voice input for AI on desktop, AI Meeting Notes from Cmd+K, shareable read-only AI chat links, Views API with eight endpoints, smart filters, heading 4 blocks, tab block support in the API, writable wiki verification, Notion Academy in six new languages. On April 16, 2026 Notion swapped Opus 4.7 in as the default model. On April 17, 2026 Mail and Calendar joined Slack in the Custom Agent settings page, and the Custom Agents free trial was extended through May 3, 2026.

Yes. Every customer-facing change in 2026 either expanded what the Notion agent can think about, or expanded the allowlist of tools it can reach. 3.2 added brain: new models and mobile parity. 3.3 added autonomy: Custom Agents running on their own. March 20 added reusability: skills. 3.4 added compute (Workers) and widened the allowlist to Mail, Calendar, Slack, Salesforce, Box, and n8n via MCP. The ceiling baked into all four releases is the same: the agent runs inside Notion's infrastructure and its reach stops at the HTTPS APIs Notion has negotiated with partners. None of the 2026 updates let the agent open an app on your Mac, type into a native text field, or read what is on your screen.

Local execution reach. A ladder where rung 1 is 'think', rung 2 is 'run autonomously', rung 3 is 'reusable skills', rung 4 is 'cloud API integrations' needs a rung 5 that says 'drive any app on your machine'. Notion's 2026 releases climbed rungs 1 through 4. Fazm 2.4.0 on April 20, 2026 shipped the rung 5 piece: a user-editable config at ~/.fazm/mcp-servers.json, read on launch by MCPServerManager.swift, that starts any MCP server as a local subprocess under your user account. The command in the config can be a wrapper around macOS accessibility APIs, which means the same agent pattern Notion uses can now drive Xcode, Logic Pro, Figma desktop, QuickBooks, or any app that exposes an AX tree.

The path is ~/.fazm/mcp-servers.json in your home directory. The format is the same shape Claude Code's mcpServers field uses. It is a top-level JSON object keyed by server name. Each entry has command (string, required), args (array of strings, optional), env (object of string-to-string, optional), and enabled (boolean, optional, defaults to true). MCPServerManager.swift decodes it with JSONDecoder into a dictionary of RawServerConfig, then merges the entries with Fazm's built-in servers in the ACP bridge. The Settings UI writes the file back with .prettyPrinted and .sortedKeys formatting, so hand-edits and UI edits round-trip cleanly.

Yes. That is the point. The entry looks like { "notion": { "command": "npx", "args": ["-y", "@notionhq/notion-mcp-server"], "env": { "NOTION_TOKEN": "secret_..." } } }. At the same time you can add a second entry for a macOS accessibility MCP server. In one chat the agent can search your Notion workspace, pull a brief, then open Xcode on your Mac and run a build. Notion's cloud agent cannot reach the Xcode step. Fazm's local agent can, because the second MCP entry launches as a subprocess on your machine.

Fully autonomous agents that handle work 24/7 once you give them a job and a trigger or schedule. They were announced February 24, 2026 and made free to try through May 3, 2026. On May 4, 2026 they move to a Notion credits add-on billed on Business and Enterprise plans. The important thing about Custom Agents in the context of the 2026 arc is that they are the 'run on their own' upgrade. Before Custom Agents you had to be in the chat for the agent to do work. After 3.3 you could define a Custom Agent once and have it fire on a schedule. This works great inside Notion. It still cannot open an app on your Mac.

Custom skills are reusable prompts saved inside Notion and callable from the text selection menu or @mention in an agent chat. They run inside Notion against Notion content and the same Notion allowlist. MCP servers are external processes that speak the Model Context Protocol, which any agent client can call. A Notion skill like 'reshape this doc in our team format' stays inside Notion. An MCP server like @playwright/mcp@latest can drive a real browser on your machine. The two layers compose well: a skill can orchestrate the prompt, and an MCP server can do reach work. Fazm's mcp-servers.json hosts the second layer locally.

No. Workers for Agents adds code execution to Notion's agent, but the code runs inside Notion's own sandboxed infrastructure with a 30 second wall clock and a 128 MB memory cap. The sandbox has no direct network access to your machine, no file access to your local disk, and cannot drive another app on your computer. It is a clean isolated worker that unlocks things like on-the-fly data transforms and one-off scripts against Notion data. It does not change the cloud perimeter. Workers for Agents is also Enterprise only at launch.

They are cloud-to-cloud integrations added to Custom Agent settings. The Notion agent speaks to Gmail and Microsoft Graph over HTTPS, and to Slack via the Slack Web API. The call originates from Notion's servers using OAuth tokens you grant. That is a good fit for reading, drafting, summarizing, and sending inside those services, because those services expose stable public APIs. It is not a fit for anything that lives only on your machine. Your local Mail.app drafts folder, a Notes.app file you haven't synced, a Logic Pro session, a Final Cut timeline, and a Figma desktop document are all invisible to a Notion Custom Agent.

Three shipped together in 2.4.0. Custom MCP server support via ~/.fazm/mcp-servers.json with a Settings UI to add, edit, and toggle servers. Dynamic AI model discovery, so newly released Claude models (like Opus 4.7) appear in the model picker without an app update. A Referrals section in Settings with a $49 credit banner on the paywall. The release also upgraded the Claude agent protocol to v0.29.2, fixed follow-up messages that were not appearing during a streaming response, fixed AI responses splitting mid-word into separate bubbles, and shortened the free trial from 21 days to 1 day. Of those, the MCP server file is the one that changes the 2026 story.

Yes, that is the natural division of labor. Notion 2026's four rungs make Notion a strong place to plan: the dashboard view from 3.4 part 1 aggregates KPIs, AI Meeting Notes captures intent from a call, the Views API lets external services read structured Notion data, Custom Agents run on a schedule. Fazm runs on the same machine you actually do work on, so it picks up where Notion's allowlist stops. A common pattern: a Notion Custom Agent writes a brief, a Fazm chat asks 'do the brief', Fazm uses the notion MCP server to read the brief, then uses a macOS accessibility MCP server to open the real apps and do the work, then writes results back through the Notion API.