Skip to main content
Task guide: Find and draft changes

​
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.
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 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:
--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 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.
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:
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, 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: