Agents get a shared memory as Figma and Notion rebuild their context layers

Agents that remember where they live

Notion's biggest move of the week was about making your workspace the durable home for context rather than something trapped in one assistant. Notion 3.8 connects agents over MCP, letting them read workspace context and act across 150-plus external tools, and adds a Skills API so agent skills can be synced between ChatGPT and Claude. Just as important is the governance side: column-level database permissions now control which properties each person — or agent — can view or edit, which is the difference between an agent that can be trusted with a database and one that can't. The release also rebuilt synced databases for GitHub, Jira, and Salesforce, upgraded version history across both pages and databases, and lets you draw on a ChatGPT Plus or Pro plan for AI usage inside Notion.

The SDK server-side story got a quick correction too. After the previous version threw BrowserTokenNotAllowedError in Cloudflare Workers and Deno worker threads, Notion's JS SDK stopped mistaking server runtimes for browsers, restoring client creation with auth and the user-agent header — and letting server code drop the dangerouslyAllowBrowser workaround.

Figma's context-and-code push

At Config India 2026, Figma unveiled tools for building with code, capturing and sharing context, and designing with real data and content — a triple that lines up closely with where Notion is heading, each product trying to keep design and product context alive across the tools that consume it.

Figma Make, meanwhile, is rolling out Gemini 4 Argon, giving prompt-to-interface work a newer model underneath it. For teams shipping code from those designs, Code Connect now reports preflight validation failures back to Figma (opt out with DO_NOT_TRACK=1), confirms the active library and framework on Professional plans when publishing, and fixes file discovery in folders with special characters, text-layer filtering crashes in findLayers, and vague "fetch failed" errors that now report the underlying cause.

Lighter updates under the hood

Two products kept it quiet. Slack's latest desktop build is a speed and leanness pass with bug fixes, and Linear Mobile picked up assorted fixes and minor improvements. Notion's app build added its own bug fixes and performance work alongside the 3.8 launch. None of it changes workflows; all of it is the kind of maintenance you notice only when it's missing.

The throughline: Notion and Figma both spent the week making their products a place where context accumulates and agents can use it, while the smaller releases focused on the dependable groundwork underneath.