GitHub Copilot Coding Agent: Enhanced Session Log Visibility
GitHub CopilotGitHub has expanded the transparency of the Copilot coding agent's session logs, giving developers clearer insight into what the agent does before and during task execution. Setup steps — including repository cloning, agent firewall initialization, and custom copilot-setup-steps.yml commands — now surface directly in the session view, eliminating the need to dig through verbose GitHub Actions logs. When the agent delegates work to subagents, their activity appears collapsed by default with a live heads-up display of current status, expandable on demand for full output.
Sources & Mentions
4 external resources covering this update
Improved Transparency in Copilot Coding Agent Session Logs
When GitHub Copilot's coding agent works on a task, it operates autonomously in a cloud-based development environment — cloning the repository, running setup, executing tests, and pushing changes before asking for human review. Until now, much of what happened during that startup and delegation phase was opaque to the developer waiting on the other side. GitHub has changed that with a meaningful upgrade to session log visibility, shipped on March 19, 2026.
Setup Step Visibility
Before the coding agent begins actual task work, it performs a series of preparatory operations: cloning the target repository and, if configured, initializing the agent firewall. These steps now appear explicitly in the session logs, with timestamps indicating when each phase begins and ends. Developers no longer need to wonder whether the agent is stuck or simply still initializing — the log makes the waiting period legible.
Custom Setup Steps in the Session View
For teams that have defined a copilot-setup-steps.yml file to customize the agent's development environment, the output from those steps now streams directly into session logs. Previously, verifying whether a custom setup step executed correctly required navigating out of the session view and into the underlying GitHub Actions logs. With this change, developers can confirm environment configuration and debug issues without leaving the session context.
Subagent Activity Tracking
The Copilot coding agent can delegate specialized work to subagents — for example, when it needs to research the current state of the codebase before making changes. Subagent activity now appears in the session log in a collapsed state by default. A heads-up display shows what the subagent is currently working on, and developers can expand the entry at any time to inspect the full output. This design keeps the session log readable while still providing the detail needed when something goes wrong.
Availability
These session log improvements are available to all GitHub Copilot users with access to the coding agent feature. Documentation on tracking coding agent sessions is available in the GitHub Copilot docs.