Introduction

After you give Copilot a task, it works autonomously in the background to complete it. SeeAbout GitHub Copilot coding agent.

The agents panel,agents page, the GitHub CLI, and GitHub Copilot extension for Raycast provide an overview of your agent sessions across repositories. You can use them to kick off new tasks and track Copilot's progress.

You can also track Copilot's sessions in a specific repository from Visual Studio Code.

During or after an agent session, you can inspect the session logs to understand Copilot's approach to your problem.

Tracking agent sessions from the agents panel or page

You can see a list of your running and past agent sessions in the agents panel, available from every page on GitHub, or on the dedicated agents page.

To open the agents panel, click in the navigation bar on any page.

To open the agents page, open the agents panel, then clickView all.

For each session listed below, you can see its status at a glance, or click on it to navigate to the linked pull request.

To view the session logs, click through to the pull request in the list, then find the "Copilot started work..." event in the timeline, and then clickView session.

You can also start new agent sessions from the page and panel. SeeAsking GitHub Copilot to create a pull request.

Tracking agent sessions from the GitHub CLI

You can see a list of your running and past agent sessions from the GitHub CLI with thegh agent-task list command. The output will show a list of your recent sessions.

To see more information on a specific session, use thegh agent-task view command. For example, to view information about the session associated with pull request #123 in themonalisa/bookstore repository, rungh agent-task view --repo monalisa/bookstore 123.

To view the session logs, add the--log option. Optionally, use the--follow option to stream live logs as the agent works.

To see all of the available options, rungh agent-task list --help orgh agent-task view --help.

Tracking agent sessions from Raycast

Raycast is an extensible launcher for macOS. With the GitHub Copilot extension for Raycast, you can start and track Copilot coding agent tasks wherever you are on your computer.

1. Install Raycast from theRaycast website.
2. Install the GitHub Copilot extension for Raycast by clicking theInstall Extension button on theextension's page.
3. Open Raycast, search for "Copilot," find theView Tasks command, then pressEnter.
4. ClickSign in with GitHub, then complete the authentication flow. Raycast will re-open.
5. You'll see a list of your tasks. To navigate to the linked pull request, pressEnter. To view the session logs, pressCommand+L.

You can also start new agent sessions from Raycast. SeeAsking GitHub Copilot to create a pull request.

Tracking sessions from Visual Studio Code

You can see a list of your running and past agent sessions for a specific repository in Visual Studio Code with theGitHub Pull Requests extension.

Once you've installed the extension, you can see Copilot's sessions by clicking theGitHub button in the sidebar.

For each session listed, you can see its status at a glance, or click on it to navigate to the pull request within Visual Studio Code.

To view the session logs, click on the pull request in the list, then clickView Session.

You can also start new agent sessions from Visual Studio Code. SeeAsking GitHub Copilot to create a pull request.

Tracking sessions from GitHub Mobile

You can see a list of your running and past pull requests generated by agents in GitHub Mobile.

1. In the "Agents" section on the GitHub Mobile Home page, tapAgent Tasks.

   A list of the currently open pull requests, that you asked Copilot to generate, is displayed.

2. Use the buttons at the top of the list to filter the list of pull requests.

   For example, to show only merged tasks, tapOpen and then, in the dropdown, tapMerged.

   

Using the session logs to understand Copilot's approach

You can dive into Copilot's session logs in GitHub or Visual Studio Code to understand how it approached your task.

In the session logs, you can see Copilot's internal monologue and the tools it used to understand your repository, make changes and validate its work.

Stopping a Copilot session

You can stop Copilot from continuing to work on a task by clickingStop session in the session log viewer.

Reasons you might want to stop a session include:

• Copilot appears to be going in a wrong direction, and you want to stop it and give it more clarity.
• You made a mistake in your description of the required work, and you've decided to start over.
• You've realized that the change you asked for doesn't need to be made, so you want to stop Copilot from doing any more work on it.

Further reading

• Best practices for using GitHub Copilot to work on tasks
• Troubleshooting GitHub Copilot coding agent