Using the Copilot coding agent logs

You can use the session logs to understand Copilot's approach.

この機能を使用できるユーザーについて

Copilot コーディング エージェント は、GitHub Copilot Pro+ のユーザーと GitHub Copilot Enterprise のお客様が利用できます。 また、GitHub Copilot Business のお客様へのロールアウトも開始されており、機能が利用できるようになったらメールでお知らせします。
Sign up for Copilot

この記事の内容

メモ

Copilot コーディング エージェント は パブリック プレビュー段階にあり、変更される可能性があります。 プレビュー期間中、この機能の使用は「GitHub プレリリース ライセンス条項」の対象となります。

Introduction

After you assign an issue to Copilot, or use Copilot Chat to ask Copilot to create a pull request, Copilot works autonomously to complete the task. See About assigning tasks to Copilot.

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

Using the session logs to understand Copilot's approach

To view the session logs, click View session in the pull request timeline.

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

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.

メモ

Copilot has its own development environment, including the ability to run automated tests and linters, to validate its changes before it pushes.

Stopping a Copilot session

You can stop Copilot 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:

  • 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