Buildkite calls token efficiency a product constraint — the agent tool surface is being edited down
The lead
Buildkite's release notes carry the sentence the rest of the day is arguing about: token efficiency is now treated as a product constraint. Its MCP server stopped growing endpoints and started shrinking them — a multi-step failure investigation collapsed into a single getbuildfailuresummary call, a waitfor_build tool so agents stop hand-rolling polling loops, job listings trimmed and log-search responses cut by about 40%. The stated goal is fewer, fatter, bounded calls that answer a question rather than return data.
That is a different question from the one vendors spent the last year on. Whether an agent can reach a product is settled: 33 of today's 158 products mention a server. What changed is the admission underneath Buildkite's rewrite — a large tool surface makes the agent worse, because every tool description and verbose response spends context the model needed for the work itself. Today reads as the edit pass on a year of additions.
What moved
- The tool surface is being cut on purpose. Twenty added deferred tool loading on its open-ended
runAgentpath, alongside model pinning and typed result errors — determinism and thrift in one release. Tracecat did the same in its Claude runtime while handing agents workflow execution. Drift is the sharpest case: its server gained a second client surface this month and simultaneously lost a tool, with transcript retrieval pulled from the Claude connector. Tana shipped chat costing fewer tokens for the same answer quality.
- Reasoning is being rationed per unit of work. Qodo's Review Effort Modes let depth vary by change, so a README typo and a diff touching a payment path no longer draw the same reasoning budget. GitHub Copilot added a per-task reasoning level. v0 by Vercel runs four model tiers and repriced its Fast tier to about a third. Speakeasy hit 1.0 metering tokens under management across Claude Code, Codex, Cursor and ChatGPT.
- The vendors' own agents need somewhere to sign in. WorkOS shipped both halves at once — Agent Registration, letting an agent authenticate into AuthKit through the auth.md protocol as a first-class principal rather than a shared key, and Atlas, an AI coworker of its own in Slack. Agno 2.7.2 put OAuth in front of
/mcpand added aGET /infocapability-discovery endpoint, building for the operator who exposes an AgentOS. Resend became an OAuth provider so third parties sign in rather than hold keys. Workato took AIRO generally available worldwide, and Prowler's Lighthouse completed a read-only → write → page-aware arc.
- Un-gating ran the other way. Windmill absorbed dbt as a first-class script type and moved BigQuery and Snowflake out of the Enterprise license onto every edition, community builds included. Zoho Recruit shipped MCP at no extra cost. Blockly folded its keyboard-navigation plugin into core so accessibility is a default, not an install; PrestaShop 9.2 pulled one-page checkout and custom fields in. Prowler is the counterweight: every agentic capability it shipped landed on the paid side of the open-core line.
- And a calendar, mostly not about AI. GitHub closed Spark to new users on 4 August and shuts it entirely on the 31st, folding the surface back into Copilot. EGroupware ends 23.1 support on 15 August. Fulcrum auto-switches every remaining Google Maps org to Esri on 1 September, the day Buildkite's Agent v4 cutover lands; Clari customers must migrate to a new External Client Application by the 2nd. Talos Linux 1.14 defaults
/varto noexec and names Longhorn v1 and vCluster as workloads it breaks. Kavita hotfixed CVE-2026-47202, which affects every prior version.
Sectors today
Devtools carried the day at 34 products and every lead anchor. Development, analytics and collaboration ran the platform work — Neo4j's hosted MCP service, Lightdash letting coding agents scaffold data apps locally against live data, SiYuan opening a 3.8 branch with agents and embedding search in its first alpha. Project management was Atlassian feeding Rovo the file stores and winding Connect down, plus Asana gating agent-written rules behind human review. Communication and video were quieter: 3CX put MCP and an AI server inside the PBX; incident.io took MCP to GA and buried it in a post about navigation. Finance, CRM, HR, marketing, support, ecommerce and edtech were thin on releases and heavy on published content — Financial Cents' AI File Validator was the real one.
Watch tomorrow
Buildkite expects more composite tools shaped like getbuildfailure_summary; whether anyone copies that shape is the thing to watch, since it is the first concrete answer to what a second-generation MCP tool looks like. Drift's removed tool should be followed by per-tool permissions, not a blanket restore. Lightdash left its own release's question open: how an agent-authored app gets reviewed before viewers see it. On crawl quality,Metricool, Celoxis and Vendasta again produced six posts each and zero releases, and Firefly III fired eight nightly tags in a day.