Notion vs Proton Bridge

The 3.5 and 3.6 releases turned Notion into a developer platform: Workers run custom code on Notion's infrastructure, a CLI and Markdown API exist for coding agents, and External Agents bring Claude and Cursor onto a shared board where a team can assign and watch them. Custom Agents have accumulated the surrounding machinery in the weeks since — five more MCP connections, calendar tools, Outlook mail, Microsoft file read and write, audit-log coverage, and a people directory. The most recent entries are smaller and mostly about wiring: sharing context from the Share menu, sharing Workers across a team, and surfacing Worker usage in the credits dashboard before the free beta ends.

Notion is positioning itself as the orchestration layer rather than another agent vendor, which is a different bet than most of its competitors are making. The supporting work is consistent with that: Workers to run the code, a credits dashboard to price it, an audit log to govern it, and sharing so one person's Worker becomes a team asset. The recent shift from platform launches to permissions, sharing and billing surfaces is what a product does after the capability lands and adoption becomes the constraint.

Workers move onto paid credits on August 11, so the near-term work should keep clustering around usage visibility and cost controls. The trigger surface is the other thread to watch — meeting notes became an agent trigger this window, and the same pattern applied to other Notion events is the obvious next step.