Weekly signal

This week (July 6–14, 2026) pushed agentic AI deeper into creative workflows: design canvases and no-code site builders shipped agent features that act on files and code; the agent infra stack hardened with a major MCP (Model Context Protocol) release candidate that makes tool-servers scale; and marketplaces and mobile agent apps expanded distribution for creative teams. These moves materially change how creative teams delegate discrete tasks (asset generation, motion, copy drafts, page edits) to persistent agents that operate inside product canvases and toolchains rather than only via one-off prompts.

What changed

1. Figma’s Config follow‑ups kicked off July early access for Code Layers (runnable code as a canvas layer) and broadened the in‑canvas agent with Skills and connectors to GitHub, Notion, Slack and Atlassian—putting motion, code, and agent automation in a single multiplayer design file. Early access for Code Layers and agent connectors opened in July 2026.

2. Notion launched a dedicated Notion Agents iPhone app and external‑agent support (Claude, Gemini, GPT models), shipping a mobile entry point for workspace‑aware agents that can act on documents, databases and simple workflows—useful for briefs, rapid content capture and first‑draft creative work on the go. The app news appeared the week of July 7–8, 2026.

3. The Model Context Protocol published its 2026‑07‑28 release candidate (stateless core, MCP Apps, Tasks), removing protocol‑level sessions so agent tool servers can scale behind ordinary HTTP load balancers—a major infra enabler for multi‑tenant, agentic creative services. The RC is in the ten‑week validation window before a July 28 final. W3C and web tool vendors picked up the spec activity during the July 3–10 window.

4. Agent skill marketplaces and lightweight agent platforms continued fast growth: Agensi announced crossing 2,000 published agent skills on July 9, signaling developer/creator demand for task‑specific agent components creatives can adopt.

5. Adobe continued to promote agent orchestration and multi‑agent creative patterns at industry events (Adobe Summit London sessions on agent workflows, July 7), emphasizing production pipelines that combine Firefly Creative Agent capabilities with enterprise orchestration.

What to do with it

1. If you run creative teams, pilot agents inside your design canvas (Figma/Framer) for repeatable tasks (animation templates, asset variants, A/B copy) but enforce guardrails and a review step for brand/taste. Start with one Skill or Code Layer to measure time saved.

2. Try Notion Agents on mobile for fast idea capture and brief generation; integrate an external model only after testing retrieval accuracy against your workspace documents. Treat mobile agents as idea‑acceleration, not final creative output.

3. For product and tooling engineers: audit MCP client/server dependencies now — the 2026‑07‑28 RC changes session semantics and scaling expectations. If you host agent tool servers, plan migration and conformance tests before July 28.

4. For agencies and vendors: explore agent skill marketplaces to ship taskized skills (creative briefs, scene lists, asset variants) and price them for repeat usage—market demand is visible. Track provider credit models and rights terms.