Microsoft Research launched Flint for agent-friendly charting: a new visualization language/compiler that lets agents produce polished charts from compact specs, with an MCP server for chart creation and validation. The repo already shows traction at 1.9k stars, 308 commits, and a v0.3.0 release on July 19. Sources: Microsoft Research post ; GitHub repo ; HN discussion
Microsoft Research’s SkillOpt reframes agent skills as trainable parameters instead of hand-edited prompts. The June 30 post says the method was best or tied-best across 52 evaluation cells, improved GPT-5.5 direct-chat performance from 58.8 to 82.3 on the six-benchmark average, and transferred across harnesses. Sources: Microsoft Research post
Microsoft Security published a concrete agent-risk playbook on MCP tool poisoning. The post walks through how a poisoned tool description can turn a routine read/write workflow into exfiltration, and maps mitigations to Defender, Purview DLP, Sentinel, Entra Agent ID, and human approval gates. Sources: Microsoft Security blog
Satya Nadella’s June 15 LinkedIn note, “A frontier without an ecosystem is not stable,” keeps pushing the same strategic line: AI value compounds when human capital and token capital form a learning loop, not when teams just rent a frontier model. Sources: Satya Nadella LinkedIn post ; Microsoft Source archive reference
OpenAI’s “How agents are transforming work” is the clearest fresh product-research read on agent adoption this cycle. OpenAI says Codex has moved from a developer tool to the default work tool across every department internally, with 80.6% of sampled individual users making at least one request estimated to exceed 30 minutes and non-developer adoption growing 137x since August 2025. Source: OpenAI article
A production agent migration writeup from Ploy gives a useful model-swap reality check: GPT-5.6 beat Claude Opus in their evals, finished builds 2.2x faster, and cut cost by 27%, but only after they fixed harness assumptions, tool-call schemas, prompt caching, and reasoning replay. Sources: Ploy blog ; HN discussion
r/LocalLLaMA is converging on a practical floor for local agentic coding: roughly 24GB VRAM is bare minimum, 40–48GB is the comfortable daily-use zone, 100k+ context is preferred, and reliability/tool-use quality matters more than raw tok/s. Source: Reddit discussion