Enhanced Session Log Visibility

GitHub has released improvements to Copilot coding agent's session logs, making it easier for developers to understand and debug what the agent is doing while working on tasks in the background. Three key areas have been enhanced to provide better transparency.

Built-in Setup Steps Visibility

Before Copilot can start work on your task, it must initialize by cloning your repository and starting the agent firewall (if enabled). These setup operations now show detailed progress updates in the session logs, allowing developers to see when each step starts and completes. This eliminates the guesswork and provides clear visibility into what's happening while Copilot prepares to begin work.

Custom Setup Steps Output

Developers can customize Copilot's development environment using a copilot-setup-steps.yml file in their repository. The improvements now surface the output from these custom setup steps directly in the session logs, enabling developers to:

• Verify the environment is configured correctly
• Debug issues without navigating to verbose GitHub Actions logs
• Understand the current state of the development environment

Subagent Activity Tracking

Copilot often delegates work to subagents for research and code understanding. The improved logs now display subagent activity with a collapsible interface—subagent details are collapsed by default with a summary of current work, but can be expanded to view full output. This keeps the logs clean while maintaining access to detailed information when needed.

Getting Started

Developers using Copilot's coding agent will automatically benefit from these logging improvements. For more details, visit the Copilot coding agent documentation.