Lead workflow
MCP Changes Integration from Fixed Endpoints to Dynamic Tool Discovery
n8n has published a guide comparing the Model Context Protocol (MCP) with traditional APIs, explaining when to use each and how to combine them in workflows.
Edition 2026-09-15
Edition for 2026-09-15 (America/Denver). Every item is dated from its source, and anything that has aged out of the news window stays in the archive instead.
Also in this edition
Lead workflow
Gemini 3.8 Live models expose speech-to-speech via WebSocket endpoint
Google released two new speech-to-speech models, Gemini 3.8 Live and 3.8 Live Extended Thinking, and a developer built a browser UI to try them. The useful integration detail…
Lead workflow
Scheduler decouples turn readiness from release to cut agentic workflow tail latency
A tail-risk-aware turn release scheduler for agentic LLM workflows matches eager release under light load and cuts P95 workflow flow time under contention by up to 3.50×, according…
Lead workflow
Harness choice shows no resolved average task advantage in paired agentic coding tests
A preprint reports paired same-model contrasts on a private contamination-controlled suite of 256 repository and post-cutoff contest tasks. It finds no resolved average harness advantage, with cost and…
Lead workflow
Claude Code v2.1.267 adds a provider-wide effort cap and a fresh-prompt switch
A point release adds a maxEffortLevel setting that caps effort across providers, plus a flag to stop reusing a conversation's recorded system prompt. It also bundles a batch…
What changed since the last edition
- first edition for this desk: nothing to compare against yet
All editions · Archive · RSS