Agents Need CI, Not Vibes: Evaluating Microsoft 365 Copilot Agents

Microsoft 365 Copilot agents are crossing the line from demo artifacts into software products. Once that happens, manual spot checks are not enough. A production agent needs a release discipline: evaluation datasets, judge configuration, thresholds, CI/CD gates, evidence packages, and regression memory. Not as governance theatre. As the shortest safe path from “nice demo” to “we can ship this and explain why.” This is the blueprint I would use to move a Copilot agent from vibe-based confidence to governed delivery. ...

May 15, 2026 · 18 min · 3701 words · Pavel Nasovich

Managing AI Agents and Code Context in 2026: Context, Cost, and Control

As of May, 2026, the strongest pattern in AI coding is not “give the agent a bigger context window.” It is the emergence of a controlled agent operating layer around the repository. That layer has a few recognizable parts: canonical instructions in version control, path-scoped rules near the code they govern, task specs before implementation, bounded subagents, MCP/tool allowlists, sandboxing, audit logs, cost-aware model routing, and a verification loop that does not confuse “the agent says it passed” with evidence. ...

May 6, 2026 · 19 min · 3980 words · Pavel Nasovich