Collaboration tools shifted from adding AI features to governing, billing and triggering them.
The week in collaboration
The lead this week is that collaboration tools stopped adding AI features and started building the layer that governs, bills and triggers them. GitHub shipped four sparks in seven days, and the through-line was accounting rather than capability: a return-on-investment section inside the Copilot admin dashboard, MCP allowlists in enterprise managed settings, and Copilot automations you trigger from a pull-request comment. The vendor is now supplying the renewal justification and the governance controls in the same release train as the features they cover.
Underneath that, the agent-native rewrite kept spreading into products that used to be plain editors and trackers. Asana relaunched Notes as a real collaborative document surface, Notion turned a finished meeting note into an event that starts agent work, SiYuan grew an AI agent and Model Context Protocol support in a single alpha, and Document360 rebuilt its API reference into a console that both developers and agents can act inside. Four different starting points — work management, a personal notebook, a knowledge base, a docs portal — converging on the same shape: a surface an agent can read and drive.
Leaders
GitHub had the densest week. The Copilot impact dashboard's new return-on-investment section ties seat spend to pull-request output, and read alongside MCP allowlists in enterprise settings and comment-triggered Copilot automations, it marks the point where GitHub started shipping the justification surface, not just the capability. The parallel deprecation of GitHub Spark shows it pruning as fast as it adds.
Asana made the window's clearest single move: Notes became Pages, gaining real-time co-editing, presence, inline comments, version history and task creation from the page, shipped across every tier. A mid-week improvement added rich text in custom fields, so the editor work reads as one program rather than scattered polish. Asana is careful to say Pages is not a wiki, which bounds it to documents attached to work.
Notion extended its orchestration argument from agents you invoke to agents that fire on their own: an AI Meeting Note now triggers a Custom Agent that can update a tracker, post a recap or file tickets, and Custom Agents gained a Share-menu path to context. The credits dashboard picked up Workers in the same window, keeping spend visible as the agent surface widens.
SiYuan opened its 3.8.0 line with four things it had never shipped — an AI agent, semantic search over embeddings with reranking, MCP support and OIDC login. A local-first, self-hostable block editor grew both an agent surface and a standard protocol for outside tools to reach the notes inside it, then spent the following alphas on sync acceleration and mobile polish.
Document360 turned its API reference from a document into a console — endpoints tested, validated and authorized in place, with Eddy AI answering inline — paired with a new Widget 2.0 embedding architecture. It is the agent-and-developer surface of prior releases finally landing where readers actually touch it.
Wildcards
AFFiNE produced one substantive tag amid a stream of canary dependency bumps: workspace-level BYOK profiles that let an organisation supply its own model providers, credentials and catalog instead of the platform's fixed Copilot. The signal is real; the noise around it is a reminder that most of this project's week was maintenance.
Whimsical closed a loop it opened in April. Ask Whimsical brings the diagram-generating agent inside the product — creating flowcharts, wireframes and mind maps and searching the workspace — after months when the same capability existed only for external agents over MCP. It then went back to polishing the canvas with better flowchart search and icons.
Ethico is the off-pattern entry: a whistleblower-hotline vendor assembling a compliance suite. Policy+ arrives as a distinct product rather than a case-management feature, launched with a Form Builder — risk before, policy during, cases after.
Themes that compounded
- MCP as table stakes: SiYuan, GitHub, Document360 and Outline all treat Model Context Protocol as a shipping requirement, not an experiment.
- Governance and cost move into the product: GitHub's ROI dashboard and MCP allowlists put spend and control in the admin surface.
- Documents became agent surfaces: Asana Pages, Notion meeting-note triggers and Document360's console all make ordinary artifacts something an agent acts on.
- Bring-your-own-model spreads to self-hosted tools: AFFiNE hands workspaces their own provider keys.
- The agent moves from invoked to autonomous: Notion fires agents on events, and Double runs bookkeeping tasks from chat.
Watch this week
Watch whether the governance layer GitHub is building becomes a pattern others copy — Notion's credits dashboard and event triggers point the same way, toward admins who need to see and cap agent spend. On the editor side, Asana Pages and SiYuan's 3.8.0 alpha are both early; the question is whether the next releases turn them from launch surfaces into daily habits, and whether Document360's interactive console draws the agent traffic its architecture is clearly built to invite.