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

# Trigger a run

> Dispatch a one-shot Outrider run, route it at a provider, or switch the coding agent.

Task guide: [Find and draft changes](https://docs.remyx.ai/platform/agents/outrider-action.md)

```bash theme={null}
remyxai outrider trigger --repo OWNER/REPO
```

## Trigger a one-shot run

Once Outrider is installed on a repo, `trigger` fires a single `workflow_dispatch` run of the workflow through your local `gh`. Useful for testing or kicking a run between cron cycles without waiting for the schedule.

Four ways to say what to implement, in ascending order of override: nothing (the ranked pool), `--search-method`, `--pin-arxiv`, or `--brief`.

```bash theme={null}
# the normal selection pass over the interest's ranked pool
remyxai outrider trigger --repo owner/name

# search for a method family and implement the top hit
remyxai outrider trigger --repo owner/name --search-method "riemannian preconditioning LoRA optimizer"

# implement an exact paper (any published arXiv id, not only pool members)
remyxai outrider trigger --repo owner/name --pin-arxiv 2402.02347v3

# implement a brief you wrote: inline, or @path to a file
remyxai outrider trigger --repo owner/name --brief "add exponential backoff to the HTTP client"
remyxai outrider trigger --repo owner/name --brief @design.md
```

| Flag | Description | Default |
| - | - | - |
| `--repo` | Target repo as `owner/name` or a GitHub URL | *(detected from git remote)* |
| `--interest, -i` | Research Interest to run against | *(the repo's configured interest)* |
| `--search-method` | A free-text method query. Runs an engine search and implements the top hit, bypassing the ranked pool and the selection pass. Mutually exclusive with `--pin-arxiv` and `--brief` | — |
| `--pin-arxiv` | An exact arXiv id (e.g. `2402.02347v3`). Bypasses selection and implements that paper. It need not be in the candidate pool: the action looks it up in the Remyx catalog, then on arxiv.org. Mutually exclusive with `--search-method` and `--brief` | — |
| `--brief` | A design brief the agent implements directly: inline text, or `@path` to read a file. No arXiv anchor; the brief is the spec. Shorthand for `--mode brief` with the brief as the lead content. Mutually exclusive with `--pin-arxiv`, `--search-method`, `--lead-content` and `--lead-content-file`; combines with `--start-from-ref` and `--publish branch`. Refused on an install whose workflow lacks the `mode` and `lead-content` inputs (re-run `init --force`), rather than silently dispatched as a paper run | — |
| `--mode` | Run mode: `recommend` (the workflow default), `brief` (set for you by `--brief`), `smoke`, or any mode the installed action supports | *(workflow default)* |
| `--ref` | Git ref to dispatch the workflow on; this picks which branch the workflow *file* comes from, not what the agent builds on | *(repo default branch)* |
| `--start-from-ref` | Branch the agent **builds on** instead of implementing from scratch: a drafter branch, or a third party's stalled PR branch | — |
| `--lead-content` / `--lead-content-file` | Markdown fed to the agent as leading context (a gap analysis) in recommend mode; `--lead-content-file` reads it from disk. Mutually exclusive with each other and with `--brief`. Capped at about 60k characters by GitHub's dispatch payload limit | — |
| `--staged-synthesis` | Turn on the multi-pass staged-synthesis flow (what the two-tier refiner uses for its promotion pass) | off |
| `--publish` | `pr` opens a draft PR or Issue; `branch` pushes the drafter branch without opening anything, so you can review before publishing | *(workflow default, `pr`)* |
| `--fidelity-policy` | Pre-PR fidelity gate for this run: `block`, `advisory`, or `off`. `advisory` suits a human-vetted warm-start branch | *(workflow default)* |
| `--test-integration-policy` | Override the run's test-integration policy (`strict` / `soft` / `off`) | *(workflow default)* |
| `--wait-for-slot` | If a run is already pending on the repo, wait for it to start instead of dispatching (which would cancel it on an install with a flat concurrency group). Use when firing several dispatches at one repo | off |
| `--base-url` | Route the coding agent at an Anthropic-compatible endpoint of your own (a proxy, an on-prem gateway). Requires the workflow to declare a `base-url` input | — |
| `--agent` | Which coding-agent CLI runs the implementation on this dispatch (`claude`, `codex`, `backboard`) — a separate axis from `--provider`. An impossible agent/provider pair is rejected locally, before the dispatch is spent. The target workflow must declare an `agent` input; re-run `init --force` or `setup-local` on installs predating it | *(workflow default)* |
| `--agent-timeout` | Wall-clock seconds for each agent phase on this dispatch (preflight and implementation share the budget). Raise for very large monorepos or thinking-mode backends. Only Claude Code has a round cap, so on `codex` and `backboard` this is the only bound on spend. `--claude-timeout` is the old name and still works | *(workflow default)* |
| `--provider` | Route the coding agent at a specific model backend for this dispatch (`anthropic`, `openai`, `zai`, `moonshot`, `openrouter`). The target workflow must declare a `provider` dispatch input, which `setup-local` workflows do | *(workflow default)* |
| `--model` | Specific model to request from the provider (e.g. `claude-opus-4-8`, `glm-5.3`, `kimi-k3`, `gpt-5.4-mini`), forwarded as the selected agent's own model variable (`ANTHROPIC_MODEL`, `CODEX_MODEL`, …) | *(provider's default)* |

> [!NOTE]
>
> `trigger` needs an authenticated `gh` (run `gh auth login`). It refuses up front if no Outrider workflow is registered on the repo; install one first with `outrider init` or `setup-local`.
>
> Inputs the installed workflow doesn't declare are dropped with a warning and the dispatch retried, so older installs still run on their baked defaults. The exceptions are the inputs a dispatch cannot do without: `--brief` refuses rather than running a paper pass, and `--provider` without `--agent` refuses when the install's own agent cannot speak to that provider. `remyxai outrider init --repo owner/name --force` rewrites the workflow with the current inputs.

## Route a run at a different model provider

Outrider's coding runtime speaks whichever model-API family its coding agent speaks, so runs can route at any compatible provider. A `setup-local` workflow declares `agent`, `provider`, and `model` as dispatch inputs — the action's [`provider` input](https://docs.remyx.ai/platform/agents/backends#the-provider-input) resolves the credential, base URL, and auth style per run — so one workflow can A/B Anthropic against Z.ai's GLM or Moonshot's Kimi:

```bash theme={null}
# one run on z.ai's GLM; the workflow's own provider stays the default
remyxai outrider trigger --repo owner/name \
  --search-method "speculative decoding" --provider zai --model glm-5.3

# the same run on Moonshot's Kimi (raise the timeout for thinking-mode latency)
remyxai outrider trigger --repo owner/name \
  --search-method "speculative decoding" --provider moonshot --model kimi-k3 \
  --agent-timeout 3600
```

`--provider` names the API endpoint; `--model` picks the model from it. Omit either to fall back to the workflow's (or the provider's) default. See [Model backends](https://docs.remyx.ai/platform/agents/backends.md) for the full matrix — secrets, auth styles, recommended timeouts, and cost telemetry.

## Switch the coding agent for a run

`--agent` is the second axis: which coding-agent CLI does the implementing, independent of which model serves it.

```bash theme={null}
# Codex on OpenAI
remyxai outrider trigger --repo owner/name \
  --search-method "speculative decoding" --agent codex --provider openai --model gpt-5.4-mini

# Backboard's router — it addresses models as <provider>/<model>, so name one
remyxai outrider trigger --repo owner/name \
  --agent backboard --provider openrouter --model z-ai/glm-5.3
```

An agent speaks one API family and a provider serves one or more, so the CLI checks the pair locally before spending a dispatch — and names the agent that does serve your provider:

```
$ remyxai outrider trigger --agent codex --provider anthropic
Error: agent=codex speaks openai-responses, which Anthropic does not serve.
       Use --agent claude for this provider.
```

Omit `--agent` and the check still runs, against the agent the installed workflow bakes rather than the CLI's default. The pair table is vendored from the action's [published matrix](https://github.com/remyxai/outrider/blob/main/docs/agent-matrix.json), so the CLI and the action can't disagree about what's supported.

To confirm a pairing actually reaches the vendor before spending a real run, dispatch the action's wiring check — it resolves the routing and makes one trivial call, no clone and no artifact, in about 30 seconds:

```bash theme={null}
remyxai outrider trigger --repo owner/name \
  --mode smoke --agent codex --provider openai --model gpt-5.4-mini
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.