> ## Documentation Index
> Fetch the complete documentation index at: https://kb.packfiles.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Runner Agent

> How Warp does what it does.

### Overview

To perform the various tasks that make up the migration process, Warp employs GitHub hosted runners — pre-configured virtual machines provided by GitHub to run workflows. These are Warp’s Runner Agents.

For any Warp operation that takes more than a few seconds to execute, you should be able to open the **Actions** tab of the *Migration HQ* repository for your project and see the Warp Runner Agent running that operation:

<Frame>
  <img src="https://mintcdn.com/packfiles/2Rig8FdmZRZViVPt/content/media/images/image%20(60).png?fit=max&auto=format&n=2Rig8FdmZRZViVPt&q=85&s=7ac079873859b5bcb1156c87041e36a9" alt="" width="1103" height="95" data-path="content/media/images/image (60).png" />
</Frame>

Some of the operations performed by Warp’s Runner Agents include:

* Verifying the credentials stored in your vault file.
* Scanning the source for repositories.
* Migrating a repository from the source to the destination.

### Viewing a Runner Agent’s Logs

To view a Runner Agent’s logs, click on its entry. This will bring up the runner’s details page:

<Frame>
  <img src="https://mintcdn.com/packfiles/2Rig8FdmZRZViVPt/content/media/images/image%20(68).png?fit=max&auto=format&n=2Rig8FdmZRZViVPt&q=85&s=76e33d1030c37520245339d7f3365d63" alt="" width="1580" height="764" data-path="content/media/images/image (68).png" />
</Frame>

In the **runner.yml** section,  click the button marked **Packfiles Warp Runner ...** to view the Runner Agent’s collection of logs:

<Frame>
  <img src="https://mintcdn.com/packfiles/2Rig8FdmZRZViVPt/content/media/images/image%20(65).png?fit=max&auto=format&n=2Rig8FdmZRZViVPt&q=85&s=418f3ad57c4f2332be69c3f3d654c989" alt="" width="1143" height="446" data-path="content/media/images/image (65).png" />
</Frame>

Click on any log title to expand it and view its contents. For example, here’s the log for the **Set up job** process:

<Frame>
  <img src="https://mintcdn.com/packfiles/2Rig8FdmZRZViVPt/content/media/images/image%20(66).png?fit=max&auto=format&n=2Rig8FdmZRZViVPt&q=85&s=2e0326a39e7517725e7c13e6e58e0150" alt="" width="1129" height="728" data-path="content/media/images/image (66).png" />
</Frame>

### Example: Troubleshooting Using a Runner Agent’s Logs

In the event that Warp encounters a problem while migrating a repository, you’ll see a message like this in comments it the repository’s issue:

<Frame>
  <img src="https://mintcdn.com/packfiles/2Rig8FdmZRZViVPt/content/media/images/image%20(61).png?fit=max&auto=format&n=2Rig8FdmZRZViVPt&q=85&s=c72861df475e7f098397b5045e038da2" alt="" width="1128" height="231" data-path="content/media/images/image (61).png" />
</Frame>

If you see a message like this, expand the **Troubleshoot** section...

<Frame>
  <img src="https://mintcdn.com/packfiles/2Rig8FdmZRZViVPt/content/media/images/image%20(63).png?fit=max&auto=format&n=2Rig8FdmZRZViVPt&q=85&s=b71d983a34944853e065d2eb128079ad" alt="" width="1126" height="277" data-path="content/media/images/image (63).png" />
</Frame>

...then click the **Warp runner logs** link. You’ll be taken to the runner’s details page:

<Frame>
  <img src="https://mintcdn.com/packfiles/2Rig8FdmZRZViVPt/content/media/images/image%20(64).png?fit=max&auto=format&n=2Rig8FdmZRZViVPt&q=85&s=8e6cb44de6e6dad1f5fc005962621440" alt="" width="1580" height="764" data-path="content/media/images/image (64).png" />
</Frame>

To view the Runner Agent’s collection of logs, click the button marked **Packfiles Warp Runner ...**

<Frame>
  <img src="https://mintcdn.com/packfiles/2Rig8FdmZRZViVPt/content/media/images/image%20(65).png?fit=max&auto=format&n=2Rig8FdmZRZViVPt&q=85&s=418f3ad57c4f2332be69c3f3d654c989" alt="" width="1143" height="446" data-path="content/media/images/image (65).png" />
</Frame>

The search text field near the upper right corner of the page applies to all of the Runner Agent’s logs. A search for `Error` reveals the problem:

<Frame>
  <img src="https://mintcdn.com/packfiles/2Rig8FdmZRZViVPt/content/media/images/image%20(67).png?fit=max&auto=format&n=2Rig8FdmZRZViVPt&q=85&s=7b1adeac48bc6d270f1427ea07a4a04f" alt="" width="1158" height="765" data-path="content/media/images/image (67).png" />
</Frame>

The end of line 429 shows what happened: `Name cannot end in .wiki`.

A quick look at the issue’s body reveals the source of the problem: someone specified that the destination repository’s name as **PartsUnlimited.wiki**:

<Frame>
  <img src="https://mintcdn.com/packfiles/2Rig8FdmZRZViVPt/content/media/images/image%20(69).png?fit=max&auto=format&n=2Rig8FdmZRZViVPt&q=85&s=dfa79c4f2ba616ef874042fc3d4e7471" alt="" width="1009" height="298" data-path="content/media/images/image (69).png" />
</Frame>

ℹ️ GitHub repository names cannot end with **.wiki**; this is because it automatically creates a wiki for each repository using the repository’s name followed by the **.wiki** extension.

Fortunately, the solution is simple: rename the destination repository using the /rename-destination slash command so that it doesn’t end with **.wiki**.
