GitHub Copilot's coding harness requires approval for every action

Microsoft shipped the GitHub Copilot Agent for Agent Framework on August 4, and the detail that matters is what it doesn't let you skip. Every shell command, file write, URL fetch, and custom tool call routes through a permission handler you have to define yourself. There's no default-allow path. The package lands as Microsoft.Agents.AI.GitHub.Copilot for .NET 8+ and agent-framework-github-copilot for Python 3.11+, per Microsoft's announcement.

This matters because most agent harnesses treat approval as a setting you turn on if you're careful. Microsoft built it as the only path through. If you're wiring an agent to touch a filesystem or hit a network endpoint, you write the gate before the agent runs, not after something goes wrong.

The same release carries a second change that's easy to miss and probably more disruptive. Agent Framework 1.17.0 pulled Durable Task and Azure Functions integrations out of the core packages, so anyone depending on them directly now needs a separate reference. More significant: declarative workflows now fail when an agent returns an error, instead of continuing silently. Per Microsoft's post, that's a direct behavior change, not just a bug fix.

What breaks

If your workflow has been running clean for months, that may be because a step has been failing and the framework kept going anyway. Upgrading to 1.17.0 turns that into a visible failure. Worth checking your error logs against what actually ran before you assume anything's been passing that actually wasn't.

The harness change and the workflow change point the same direction: Microsoft is closing gaps where agent behavior went unchecked by default. Whether that's the whole story for this release, Microsoft's post doesn't say.