Notion AI Updates 2026: Every AI Feature Shipped So Far

Matthew Diakonov··14 min read

Notion AI Updates 2026: Every AI Feature Shipped So Far

Notion's AI capabilities have changed more in four months of 2026 than in the entirety of 2025. What started as a text generation add-on is turning into a compute platform with code execution, voice input, and cross-page context awareness. If you rely on Notion AI for daily work, your mental model from last year is already outdated.

This post tracks every Notion AI update shipped in 2026, organized by month, with concrete details on what changed and how it affects real workflows.

Full Timeline of Notion AI Updates in 2026

| Month | AI Update | Category | Impact | |---|---|---|---| | January | Faster AI autofill for databases | Performance | Autofill dropped from 8-12s to under 3s per page | | January | AI context window expansion | Core | AI prompts can reference up to 50 pages of context, up from 20 | | February | AI autofill improvements (better context) | Database AI | Generated values now consider linked relation properties | | February | Inline AI suggestions in documents | Editing | AI offers completions as you type, similar to GitHub Copilot | | March | AI blocks with cross-page context | Core | AI blocks reference content from linked pages, not just the current page | | March | Custom AI prompt templates | Productivity | Save and reuse prompt templates across your workspace | | April | Workers for Agents (developer preview) | Platform | AI agents can execute custom server-side code inside Notion | | April | Voice input for AI prompts | Input | Speak prompts on macOS and Windows instead of typing | | April | AI meeting notes from Cmd+K | Meetings | Capture meeting notes without navigating to a dedicated page | | April | Custom instructions for AI meeting notes | Meetings | Set tone, format, and team-specific context for generated notes |

Q1 2026: The Foundation Updates (January to March)

Faster AI Autofill

The January performance update was less flashy than later releases but arguably the most impactful for daily users. AI autofill on databases with 500+ pages previously took 8 to 12 seconds per page. After the January update, the same operation runs in under 3 seconds. For teams using autofill across project tracking databases, this cut batch processing time by roughly 70%.

The speed improvement came from Notion switching to a smaller, specialized model for structured data generation instead of routing every autofill request through their general-purpose model.

Expanded Context Window

Also in January, Notion quietly increased the context window for AI prompts from 20 pages to 50 pages. This matters when you ask Notion AI to summarize a project or generate a status report. With 20 pages of context, the AI would miss content from older or deeply nested sub-pages. At 50 pages, most workspaces can feed an entire project's documentation into a single prompt.

Smarter Autofill with Relation Awareness

February's autofill improvement addressed a long-standing frustration: AI autofill ignored relation properties. If you had a "Client" relation pointing to a CRM database and asked AI to generate a summary, it would only see the relation name, not the linked page's content. After the February update, autofill traverses one level of relations and includes property values from linked pages.

Note

Relation traversal is limited to one level. If Page A relates to Page B which relates to Page C, autofill on Page A sees Page B's properties but not Page C's. Deep traversal is not supported yet.

Inline AI Suggestions

February also brought inline AI suggestions to documents. As you type in a Notion page, the AI offers completions that appear as grayed-out text you can accept with Tab. This is opt-in per workspace and can be toggled under Settings > AI. Early reports suggest it works well for structured writing (meeting notes, documentation) but generates noisy suggestions in free-form brainstorming.

Cross-Page Context for AI Blocks

The March update was the biggest architectural change. AI blocks (the /ai slash command output) could previously only see content on the current page. After March, AI blocks automatically pull context from pages linked via mentions, relations, or synced blocks. This makes AI-generated summaries and analyses significantly more accurate because they can consider the full picture across related pages.

Q2 2026: The Platform Shift (April)

April's updates signal a strategic pivot. Notion AI is no longer just a text tool; it is becoming a programmable agent platform.

Workers for Agents

Workers for Agents, released in developer preview on April 7, lets AI agents execute custom JavaScript or Python code on Notion's servers. Before Workers, agents could read pages, write content, and update properties. Now they can run arbitrary computations: call external APIs, transform data, perform calculations, and chain multiple operations together.

// Example: A Worker that calculates project health scores
// based on task completion rates across a database
export default async function calculateHealth(context) {
  const tasks = await context.databases.query({
    database_id: context.params.projectDb,
    filter: { property: "Sprint", select: { equals: "Current" } }
  });

  const total = tasks.results.length;
  const done = tasks.results.filter(
    t => t.properties.Status.select.name === "Done"
  ).length;

  const healthScore = total > 0 ? Math.round((done / total) * 100) : 0;

  await context.pages.update({
    page_id: context.params.dashboardPage,
    properties: {
      "Health Score": { number: healthScore },
      "Last Calculated": { date: { start: new Date().toISOString() } }
    }
  });

  return { healthScore, total, done };
}

Workers run in a sandboxed V8 isolate with a 10-second execution limit and 128MB memory cap. They can make outbound HTTP requests but cannot access the filesystem. This is intentionally constrained to prevent abuse while still enabling meaningful automation.

Notion AI Agent Architecture with Workers (April 2026)User Prompt"Calculate health"AI AgentPlans + orchestratesWorkerRuns JS/PythonNotion APIRead/write pagesExternal APIOptional HTTPPage ContextUp to 50 pagesExisting (pre-2026)New in April 2026Optional capability

Voice Input for AI Prompts

Voice input shipped on April 3 for macOS and Windows desktop apps. You click the microphone icon next to any AI prompt field, speak your request, and Notion transcribes it and runs the prompt. Transcription uses Whisper v3 and runs locally on-device, so your audio never leaves your machine.

In practice, voice input is most useful for long, nuanced prompts. Typing "summarize the Q1 OKR page, highlight anything at risk, and format as bullet points sorted by team" is tedious. Saying it takes about 5 seconds.

AI Meeting Notes Improvements

Two updates to meeting notes landed in the same week. First, you can now trigger meeting note capture from Cmd+K (or Ctrl+K on Windows) without navigating to a meeting page. Second, custom instructions let you configure how meeting notes are generated per workspace. You can specify:

  • Preferred format (bullet points vs. prose vs. action items only)
  • Tone (formal for client calls, casual for standups)
  • Team-specific context ("always include Jira ticket numbers when mentioned")
  • What to exclude ("skip small talk, focus on decisions and action items")

What Is Still Missing

Despite the pace of updates, several gaps remain in Notion AI as of April 2026.

| Missing Feature | Why It Matters | Current Workaround | |---|---|---| | Cross-app agent actions | Workers only run inside Notion; no native ability to trigger actions in Slack, Linear, or Google Docs | Use external automation tools like Fazm or Zapier to bridge the gap | | Fine-tuning on workspace data | AI uses general models, not models trained on your specific writing style or domain | Write detailed custom instructions and prompt templates | | Image generation | No ability to generate or edit images inside Notion pages | Use external tools and paste results manually | | Offline AI | All AI features require an internet connection | No workaround; plan around connectivity | | Granular AI permissions | Cannot restrict AI access to specific pages or databases | All-or-nothing workspace toggle |

Warning

Workers for Agents is in developer preview as of April 2026. The API surface, execution limits, and pricing are all subject to change before general availability. Do not build production workflows on Workers without accepting that risk.

How Notion AI Compares Before and After 2026

AI autofill now runs 3-4x faster on large databases
Context window expanded from 20 pages to 50 pages
AI blocks pull context across linked pages, not just the current page
Custom code execution via Workers for Agents
Voice input for hands-free AI prompting
Still no cross-application agent actions
No offline AI capabilities
No granular per-page AI access controls

Common Pitfalls When Using Notion AI in 2026

  • Assuming AI sees everything. The 50-page context limit means large workspaces still hit boundaries. If your AI summary seems incomplete, check whether the source pages fit within the limit. You can verify by counting the pages mentioned or linked from your prompt's scope.

  • Over-relying on autofill for critical data. Autofill is faster now, but it still generates content based on patterns, not verified facts. Always review AI-generated property values before using them in reports or client deliverables.

  • Building production workflows on Workers before GA. The developer preview is explicitly not production-ready. Execution limits, billing, and API surface will change. Use it for prototyping and internal tools, not customer-facing automation.

  • Ignoring custom instructions for meeting notes. The default meeting note format is generic. Teams that set up custom instructions see noticeably better output because the AI knows what to prioritize. Spending 10 minutes configuring this saves hours of manual editing over a quarter.

Bridging the Gaps with External Automation

The biggest limitation of Notion AI in 2026 is that it only operates inside Notion. Workers for Agents can call external APIs, but they cannot control other applications directly. If your workflow spans Notion, Slack, Linear, and Google Sheets, you still need an external orchestration layer.

This is where tools like Fazm fit. Fazm is an open-source macOS AI agent that can interact with any application on your desktop, including Notion. Where Notion AI handles in-app intelligence, Fazm handles the cross-app coordination that Workers cannot reach.

For example, you could use a Notion Worker to calculate a project health score, then use Fazm to read that score from Notion and post a summary to Slack, update a Linear ticket, and log it in a shared spreadsheet. The two tools complement each other rather than competing.

Wrapping Up

Notion AI in 2026 has shifted from a text generation feature to a programmable platform. The Q1 foundation updates (faster autofill, bigger context windows, relation awareness) made the existing AI more reliable. April's Workers for Agents is the inflection point, giving developers the ability to run custom code inside the Notion ecosystem. The remaining gaps, particularly cross-app automation and offline support, are real, but the trajectory is clear.

Fazm is an open-source macOS AI agent that works across all your applications. Open source on GitHub.

Related Posts