Enhanced Visibility for Agent Sessions

GitHub has released a set of improvements to the Copilot coding agent's session logging, giving developers clearer insights into what the agent is doing while working on delegated tasks. The changes address three key areas: built-in setup processes, custom environment configuration, and subagent delegation.

Better Setup Step Tracking

Before Copilot begins working on a task, it needs to prepare by cloning your repository and starting the agent firewall (if enabled). Previously, developers had limited visibility into these setup steps. Now, the session logs display clear updates when these initialization steps start and finish, allowing you to understand what's happening while you wait for Copilot to begin actual work.

Custom Environment Configuration Visibility

Developers can customize Copilot's development environment using a copilot-setup-steps.yml file in their repository. The improvement now surfaces the output from these custom setup steps directly in session logs, eliminating the need to jump to verbose GitHub Actions logs for debugging. This makes it much easier to verify that your custom environment is configured correctly and troubleshoot any issues.

Cleaner Subagent Tracking

When Copilot delegates work to subagents—such as research agents that analyze your codebase before making changes—the subagent activity is now collapsed by default with a heads-up display showing current work. You can expand the details at any time to see full output, reducing log clutter while maintaining full transparency when needed.

Action items: Review your session logs next time you delegate a task to Copilot to take advantage of the improved logging. Consider implementing copilot-setup-steps.yml files in your repositories to customize Copilot's development environment with fully visible output.