Governance

Trace Every Copilot Agent Commit Back to Its Session Logs

Agent-generated commits used to arrive like any other push: you saw the diff, but not the reasoning, tool calls, or missteps that produced it. In March 2026, GitHub tightened that story.

Copilot coding agent commits can now include an Agent-Logs-Url trailer that points reviewers back to the full session logs for that change. GitHub also highlighted live monitoring of Copilot coding agent logs through integrations such as Raycast.

This is not a flashy model upgrade. It is infrastructure for accountability.

GitHub's Agent Control Plane: What Enterprise AI Governance Actually Looks Like

On February 26, 2026, GitHub made its Enterprise AI Controls and agent control plane generally available. The timing is notable: it came in the same week that Claude and Codex became available for Copilot Business and Pro users, and as GitHub Enterprise Server 3.20 hit release candidate. The GA isn’t a coincidence—it reflects an industry that has moved from “should we let agents into our codebase?” to “how do we govern agents that are already in our codebase?”

The 32% Problem: Why Most Engineering Orgs Are Flying Blind on AI Governance

Here’s a statistic that should concern every engineering leader: only 32% of organizations have formal AI governance policies for their engineering teams. Another 41% rely on informal guidelines, and 27% have no governance at all.

Meanwhile, 91% of engineering leaders report that AI has improved developer velocity and code quality. But here’s the kicker: only 25% of them have actual data to support that claim.

We’re flying blind. Most organizations have adopted AI tools without the instrumentation to know whether they’re helping or hurting, and without the policies to manage the risks they introduce.