# Runner Agent

### 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:

<figure><img src="/files/egkaJb6HObkCdsD1VQvf" alt=""><figcaption></figcaption></figure>

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:

<figure><img src="/files/ZwWC8hbiPom2otiRWVAq" alt=""><figcaption></figcaption></figure>

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

<figure><img src="/files/2fWhP60o06phNcpHC5cR" alt=""><figcaption></figcaption></figure>

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

<figure><img src="/files/vox54VnYsPXX9Gyu8ruN" alt=""><figcaption></figcaption></figure>

### 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:

<figure><img src="/files/q6k9eLfiDpS8HTfxxpcI" alt=""><figcaption></figcaption></figure>

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

<figure><img src="/files/tAeNN5IYjDx2L0b0znXZ" alt=""><figcaption></figcaption></figure>

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

<figure><img src="/files/vanWPoLZX681I4esgqTg" alt=""><figcaption></figcaption></figure>

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

<figure><img src="/files/2fWhP60o06phNcpHC5cR" alt=""><figcaption></figcaption></figure>

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:

<figure><img src="/files/6i6OOs7Gw7jVYMNmYNNe" alt=""><figcaption></figcaption></figure>

The end of line 429 shows what happened: `Name cannot end in .wiki`.&#x20;

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**:

<figure><img src="/files/jwnDkFVkmCi4SsL88Hg5" alt=""><figcaption></figcaption></figure>

ℹ️ 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**.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://kb.packfiles.io/using-warp/migration-hq/runner-agent.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
