Agent news digest

Write "Pingory Agent Weekly #17", a curated weekly digest sent to people who build agents inside Pingory workspaces and subscribe to the Pingory Blog & Newsletter. The issue is dated July 2026. The theme is the agent tax: the context and time an agent costs its user every time it has to be brought up to speed or checked on, and how agents that live inside the workspace avoid it.

Open with one intro paragraph on that theme, in the editor's voice, ending with the promise that this week's picks are all about agents that already know the room they work in.

Then list these seven items, numbered 1 to 7 in this order. Each item has a headline that links to its URL and one line of commentary underneath.

1. MCP, SDK, or CLI? How each Pingory Flow install path works and where to install it. https://pingory.s3.amazonaws.com/blog/mcp-sdk-or-cli
2. Flow MCP vs. SDK: What's the difference? A guide to choosing between Flow MCP and the Flow SDK, or using both. https://pingory.s3.amazonaws.com/blog/flow-mcp-vs-sdk
3. Popular Pingory Flow MCP templates. Seven ways teams are using Flow MCP, each with a ready-to-use template. https://pingory.s3.amazonaws.com/blog/flow-mcp-templates
4. Govern AI with one set of rules. The controls admins use to decide which apps and actions every agent in the workspace can touch. https://pingory.s3.amazonaws.com/flow/govern
5. Introducing FlowBench. How major AI models perform on the messy, complicated tasks businesses actually rely on. https://pingory.s3.amazonaws.com/flow/benchmarks
6. Recaps. An AI summary of the Rooms and threads a reader missed, linking straight to the messages it came from. https://pingory.s3.amazonaws.com/help/articles/recaps
7. Template: post new search result items to your team room. Opens in the Flow editor with the trigger and action apps pre-selected. https://pingory.s3.amazonaws.com/flow/templates/search-results-to-room

Close with one line inviting readers to share what they are building in the Pingory Community at https://pingory.s3.amazonaws.com/community.

Readers can log in at https://pingory.s3.amazonaws.com/dashboard and contact Pingory at https://pingory.s3.amazonaws.com/help/requests/new.

Use /world/pingory-email for brand chrome and CSS. For the Pingory logo, section icons, and social icons, use the absolute HTTPS URLs from tokens.json; do not use /world/ paths as image src. Reference artwork: assets.logo, assets.icons.newsletterArticles.

Dark mode should be supported.

Leave the HTML in output/email.html, a plain-text version in output/email.txt, and the subject in output/meta.json as {"subject": "..."}. Don't include From, To, or Date headers.