> For the complete documentation index, see [llms.txt](https://kb.packfiles.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.packfiles.io/using-warp/slash-commands/global/run.md).

# /run

## Description

Executes a [custom script](/using-warp/migration-hq/custom-scripts.md) defined in your project's `warp.yml` configuration file. Scripts run on a GitHub Actions runner agent and results are posted as a comment on the issue.

[View in Knowledge Base](https://kb.packfiles.io/using-warp/slash-commands/global/run)

## Examples

### Basic (no arguments):

```
/run notify_team
```

### With Arguments:

```
/run update_wiki --script_args wiki_page=migrations status=in_progress owner=chaserx
```

### With Boolean Flags:

```
/run cleanup --script_args target=logs dry_run
```

## Arguments

### script\_id (Required)

* The identifier of the script to run, as defined in your project's `warp.yml` configuration under the `scripts:` key.

**Value:**

* Must match a script identifier configured in `warp.yml`.

### --script\_args (Optional)

* Arguments to pass to the script. Provide space-separated `key=value` pairs after the `--script_args` flag. Boolean flags (without a value) are set to `"true"`.

**Value:**

* Space-separated `key=value` pairs.
* Arguments must match those defined in the script's `arguments` configuration in `warp.yml`. Unknown arguments are rejected.
* Required arguments (as configured in `warp.yml`) must be provided.

## Authorization

* When script policies are configured in `warp.yml` under `policies.scripts`, only the listed users and teams can execute the script.
* When no script policies are defined, all members of the repository’s organization can run all scripts.

See [Custom Scripts](/using-warp/migration-hq/custom-scripts.md) for configuration details.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://kb.packfiles.io/using-warp/slash-commands/global/run.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.