Outrider — GitHub Action

remyx-quickstart-sharable-1080p30-10mb.mp4

Turn any brief — an arXiv paper, a search query, or your own design doc — into a review-ready draft PR. Outrider runs as a GitHub Action, wires the implementation into a real call site in your repo, and returns a PR whose body already carries the evidence a maintainer needs to review it: references cited, license flagged, tests written, honest scope discipline in the self-review, alignment with your repo's own conventions.

- uses: remyxai/outrider@v1
  with:
    interest-id: ${{ vars.REMYX_INTEREST_ID }}

Each dispatch runs the coding agent in a fresh, ephemeral runner — candidates don't share state, testing variance stays low, and you can dispatch dozens per week without context pollution. Backends are pluggable: Anthropic Opus for the shipping commit, z.ai's GLM-5.2 at ~20× lower cost for scouting and branch-mode exploration.

Trigger patterns

Four ways to specify what Outrider should implement — same harness downstream:

Trigger	Where the intent comes from	How to fire
Alerts	System-sourced. The ranker picks from arXiv against your ResearchInterest on a weekly cron.	Scheduled — no command needed
Search	Semi-sourced. You supply a method-family query; the ranker returns the top arXiv hit.	--search-method "riemannian preconditioning LoRA"
Pin	Reproducible. You name an exact arXiv id.	--pin-arxiv 2410.20305v2
Brief	Operator-sourced. You write the design brief directly — an issue body, a Colab notebook, a hand-authored spec. No arXiv anchor required.	--brief @design.md or --brief "add exp backoff to the HTTP client"

Every pattern produces the same output shape: a draft PR with implementation + tests + license section + convention-aligned body + honest scope citations. What differs is only where the "why" comes from.

Bring your own context — even when it's underspecified. The scaffolding fills in what the brief doesn't (references cited, license flagged, tests, convention alignment) so a two-line issue body still yields a review-ready PR.

What you get

• Draft PRs wired to an existing call site, with a self-review noting what was implemented vs. left out
• Issues when preflight, validators, or self-review route the intent to discussion instead
• Branch-only mode (publish: branch) — pushes to the fork without opening a PR or Issue; explore N candidates before committing to any one
• No duplicate work — a paper isn't re-recommended once Outrider or a maintainer Issue references it
• A selection narrative in the step summary — why this candidate, or why nothing this run

Model backends

Backend	Cost / full run	Best for
Anthropic Opus	~$2–3	Finalize a draft PR
z.ai GLM-5.2	~$0.05–0.10	Draft PR
Moonshot Kimi-K3	~$1	Finalize a draft PR

Route per-dispatch via a provider input — see docs/backends.md for the auth-header matrix and the switching workflow template. Rule of thumb: GLM for the exploration ladder, Opus for the candidate you commit to ship.

Quickstart

pip install remyxai
remyxai outrider init --repo owner/name --auto-interest

Installs the action, writes the workflow, sets the secrets (REMYX_API_KEY, ANTHROPIC_API_KEY). Scheduled cron handles the weekly cadence from there.

Trigger an ad-hoc run:

# Paper-anchored — exact arXiv id or a method-family search
remyxai outrider trigger --repo owner/name --pin-arxiv 2410.20305v2
remyxai outrider trigger --repo owner/name --search-method "riemannian preconditioning LoRA optimizer"

# Brief-anchored — a design brief you supply directly, inline or from disk
remyxai outrider trigger --repo owner/name --brief "add exponential backoff to the HTTP client"
remyxai outrider trigger --repo owner/name --brief @design.md

--pin-arxiv implements the exact paper; --search-method searches for the top hit; --brief runs the paper-less flow where the design brief you supply IS the spec. See remyxai-cli for bulk-install and per-dispatch routing.

Setting up by hand instead of via the CLI? See docs/manual-install.md.

Examples

Case study: three recent contributions to huggingface/peft

Three parameter-efficient fine-tuning methods surfaced from arXiv, drafted on the smellslikeml/peft fork, and shepherded upstream to huggingface/peft:

Riemannian Preconditioned LoRA	Super-Tuning & Supra	Scaling DoRA (factored norm + fused kernel)
arXiv:2402.02347 — Zhang & Pilanci	arXiv:2607.09287 — Ilin, Zmushko & Richtárik	arXiv:2603.22276 — Zelenin & Zhuravlyova
huggingface/peft#3382	huggingface/peft#3518	pending license clarification
merged 2026-08-03 — +401/6, 32.7d review	in review — +1309/24, coord #3450	internal draft — smellslikeml/peft#18

Full case study — per-method deep dives, PR-shape cohort comparison, coordination-issue-first workflow — at docs/case-studies/peft.md.

More examples

Each PR below shows the match (paper → repo) and the shape (how the wiring landed):

• OLMo-core #13 — Preemptive training instability monitor (arXiv:2606.28116). Match: train/callbacks/ has the reactive StabilityMonitorCallback; the preemptive variant registers alongside. Shape: MechanismMonitorCallback with QK spectral entropy + MoE routing entropy, gated by a parameter-free rolling one-sided z-score; 12 tests.
• OpenRLHF #14 — MRPO step-level reward penalty (arXiv:2606.31825v1). Match: PPO advantages already carry per-step weighting. Shape: MRPO's decay factor slots into RemoteExperienceMaker.compute_advantages_and_returns as a second multiplier, opt-in flag, default-off byte-identical.
• ag2 #9 — Adaptive Context Elasticizer (arXiv:2606.31564v1). Match: MiddlewareFactory already extends the LLM-call pipeline. Shape: new elastic middleware alongside HistoryLimiter / TokenLimiter, per-instance abstraction cache for reversibility.
• lerobot #9 — Dense Embodied Chain-of-Thought supervision (arXiv:2606.30552v1). Match: the annotator has staged language modules (plan / vqa). Shape: new EcotReasoningModule wired in as phase 4.5.
• atropos #16 — Deterministic reward floor for reward-hacking mitigation (arXiv:2606.27291v1). Match: atroposlib/envs/reward_fns/ exposes RewardFunction + @registry.register. Shape: new RewardFloor implementing the paper's 6-gram + date-range rules with a -1.0 cap; 28 tests.

Documentation

• Configuration reference — full inputs, outputs, status codes
• Customization — tailor Outrider to your repo + signals it reads
• Architecture — selection taxonomy, pipeline, refinement chain
• Guardrails — what the agent can and can't modify
• Security — the agent-harness defense-in-depth model (prompt-injection & credential-leak controls)
• Model backends — full backend/auth matrix + per-dispatch switching template
• Environments — describe workflow-attached tooling via ENVIRONMENTS.md
• Weekly summary mode — opt-in rolling digest comments

License

Apache 2.0. See LICENSE.