1
0
mirror of synced 2025-12-23 21:07:12 -05:00
Files
docs/content/copilot/how-tos/use-copilot-agents/coding-agent/track-copilot-sessions.md

7.2 KiB

title, shortTitle, intro, product, versions, topics, redirect_from, contentType
title shortTitle intro product versions topics redirect_from contentType
Tracking GitHub Copilot's sessions Track Copilot sessions You can use the Agents panel or page, {% data variables.product.prodname_vscode %}, Raycast and session logs to track {% data variables.product.prodname_copilot_short %}'s progress and understand its approach. {% data reusables.gated-features.copilot-coding-agent %}<br><a href="https://github.com/features/copilot/plans?ref_cta=Copilot+plans+signup&ref_loc=using+the+copilot+coding+agent+logs&ref_page=docs" target="_blank" class="btn btn-primary mt-3 mr-3 no-underline"><span>Sign up for {% data variables.product.prodname_copilot_short %}</span> {% octicon "link-external" height:16 %}</a>
feature
copilot
Copilot
/copilot/using-github-copilot/using-copilot-coding-agent-to-work-on-tasks/using-the-copilot-coding-agent-logs
/copilot/using-github-copilot/coding-agent/using-the-copilot-coding-agent-logs
/copilot/how-tos/agents/copilot-coding-agent/using-the-copilot-coding-agent-logs
/copilot/how-tos/agents/copilot-coding-agent/tracking-copilots-sessions
/copilot/how-tos/agents/copilot-coding-agent/track-copilot-sessions
/copilot/how-tos/agents/coding-agent/track-copilot-sessions
how-tos

Note

{% data reusables.copilot.coding-agent.preview-note-text %}

Introduction

After you give {% data variables.product.prodname_copilot_short %} a task, it works autonomously in the background to complete it. See AUTOTITLE.

The Agents panel, Agents page, and {% data variables.product.prodname_copilot %} extension for Raycast provide an overview of your agent sessions across repositories. You can use them to kick off new tasks and track {% data variables.product.prodname_copilot_short %}'s progress.

You can also track {% data variables.product.prodname_copilot_short %}'s sessions in a specific repository from {% data variables.product.prodname_vscode %}.

During or after an agent session, you can inspect the session logs to understand {% data variables.product.prodname_copilot_short %}'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 {% data variables.product.github %}, or on the dedicated Agents page.

To open the Agents panel, click {% octicon "agent" aria-label="The Agents icon" %} in the navigation bar on any page.

To open the Agents page, open the Agents panel, then click View 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 "{% data variables.product.prodname_copilot_short %} started work..." event in the timeline, and then click View session.

Screenshot of a section of a pull request with the 'View session' button highlighted.

You can also start new agent sessions from the page and panel. See AUTOTITLE.

Tracking agent sessions from Raycast

{% data reusables.copilot.coding-agent.raycast-intro %}

{% data reusables.copilot.coding-agent.raycast-setup %}

  1. Open Raycast, search for "{% data variables.product.prodname_copilot_short %}," find the View Tasks command, then press Enter.
  2. Click Sign in with {% data variables.product.github %}, then complete the authentication flow. Raycast will re-open.
  3. You'll see a list of your tasks. To navigate to the linked pull request, press Enter. To view the session logs, press Command+L.

Note

If you are unable to see some tasks in Raycast, the organization that owns the repository may have enabled {% data variables.product.prodname_oauth_app %} access restrictions. To learn how to request approval for the "{% data variables.product.prodname_copilot %} for Raycast" {% data variables.product.prodname_oauth_app %}, see AUTOTITLE.

You can also start new agent sessions from Raycast. See AUTOTITLE.

Tracking sessions from {% data variables.product.prodname_vscode %}

You can see a list of your running and past agent sessions for a specific repository in {% data variables.product.prodname_vscode %} with the GitHub Pull Requests extension.

Once you've installed the extension, you can see {% data variables.product.prodname_copilot_short %}'s sessions by clicking the {% data variables.product.github %} 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 {% data variables.product.prodname_vscode %}.

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

You can also start new agent sessions from {% data variables.product.prodname_vscode %}. See AUTOTITLE.

Using the session logs to understand {% data variables.product.prodname_copilot_short %}'s approach

You can dive into {% data variables.product.prodname_copilot_short %}'s session logs in {% data variables.product.github %} or {% data variables.product.prodname_vscode %} to understand how it approached your task.

In the session logs, you can see {% data variables.product.prodname_copilot_short %}'s internal monologue and the tools it used to understand your repository, make changes and validate its work.

Note

{% data variables.product.prodname_copilot_short %} has its own development environment, including the ability to run automated tests and linters, to validate its changes before it pushes.

Stopping a {% data variables.product.prodname_copilot_short %} session

You can stop {% data variables.product.prodname_copilot_short %} from continuing to work on a task by clicking Stop session in the session log viewer.

Screenshot of the log viewer with the 'Stop session' button highlighted.

Reasons you might want to stop a session include:

  • {% data variables.product.prodname_copilot_short %} 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 {% data variables.product.prodname_copilot_short %} from doing any more work on it.

Further reading