Turn your next AI change into review-ready code.
Outrider finds changes that fit your goals and repository, then uses your coding agent to build review-ready code. Candidates that don’t clear the checks can stop before reaching review.
Four contributions merged upstream. Read the case study ↗
Start from your goal or a specific change.
Use a brief to specify the work, or discover a candidate matched to your priorities.
Give Outrider an issue, design doc, Colab, or inline spec. No paper required.
--brief @design.md
Name an exact arXiv id for a repeatable run.
--pin-arxiv 2410.20305v2
Give Outrider a method family. It finds the top matching paper.
--search-method \ "riemannian preconditioning LoRA"
Scheduled discovery against your repository's research brief.
# no command needed
One command to provision Outrider
$ remyxai outrider init --repo owner/name --auto-interestFull setup guide ↗Install the CLI, authenticate, and add a model key first. The guide covers all three.
Discover → implement → check → decide
Start with the change
Use alerts, search, a pinned paper, or your own brief. Outrider checks the change against your repo, its history, and a real call site before it writes code.
→Build it on a branch
The coding agent runs in a fresh runner, implements the change in your repo, writes tests, and keeps the work scoped to the integration.
→Check the implementation
Outrider checks fidelity, repo conventions, lint, and targeted tests before the work is ready for review.
→Review the result
Outrider opens a PR, files an Issue, keeps the work on a branch, or skips. Your team decides what goes any further.
Outrider checks the implementation before review. Use Validate to measure the change against your team’s criteria.
// SHIPPED_UPSTREAM
Riemannian-preconditioned LoRA
Merged August 3, 2026Tests and benchmark results accompanied the implementation, including a result below the baseline.
"this PR is already quite mature"peft maintainer · first review
Inspect the merged PR →Super-Tuning and Supra
Merged August 21, 2026Coordinated with the maintainer before implementation and revised through two review rounds. Mixed benchmark results remained visible.
"The PR looks good from my perspective"peft maintainer · final approval
Inspect the merged PR →EfficientViM
Merged September 11, 2026All 12 reference checkpoints were reproduced, with numerical parity checks and tests.
Inspect the merged PR →AbsTopK bidirectional SAE
Merged October 2, 2026The contribution added the method, tests and documentation, then addressed maintainer feedback.
Inspect the merged PR →The PEFT v0.21.0 release notes include two Remyx contributions. Other upstream drafts remain in review. Read the case study →
Every run has an explicit outcome
Outrider can prepare a PR, keep work on a branch, open an issue or stop. Your team reviews the work and decides what ships.
The change fits the repo and clears the checks. Outrider opens a PR with the implementation, tests, references, license context, and review notes.
The idea is relevant but needs a better integration point or maintainer judgment. Outrider files an Issue and preserves the attempted work for discussion.
Push the implementation without opening a PR or Issue. Use branch mode to inspect several candidates before choosing one to put in front of maintainers.
Nothing clears the fit, dedup, or safety gates. No maintainer-facing artifact is created, and the run records why it stopped.
Use evidence from earlier runs
With repo state enabled, Outrider records what fit, what was rejected, and why. Later runs can use that history.
Call sites and integration shapes that prior runs reached cleanly.
Rejected mechanism shapes, the reason they failed, and the conditions that could change that result.
Merged PRs, coordination Issues, and prior Outrider artifacts help prevent repeated work.
As new findings arrive, Outrider can evaluate them against a repo history that is getting more specific.
Before review, every PR is checked three ways
The default chain runs after the draft is created and stays in the same workflow.
Compares the draft to the reference implementation when one exists, or to the paper when it does not. The run records what is covered, deferred, or different.
Shapes the PR around the repo's recent merged work, contribution docs, and existing templates.
Runs lint and targeted tests on the changed files. Passing work moves to ready-for-review; failures stay visible for a human to take over.
Choose the coding agent and the model provider
The agent is an Outrider input. Your provider key stays in repo secrets, and calls go from your runner to the provider.
agent: claude | codex | backboard
# your key, your bill, your choice
Runs in GitHub Actions. Nothing merges on its own
The coding agent runs in a fresh runner. Credentials stay out of the agent subprocess, workflow edits are blocked, and every merge still requires a human.
- same-repo installs use a repo-scoped bot token for GitHub writes
- model provider keys stay in your repo's Actions secrets;
--github-secrets-onlyseals the key from your machine so Remyx never receives a readable copy - .github/workflows/** is always blocked from agent edits
- dependency, CI, hook, container, and shell changes are flagged for review
- a credential match in outbound content aborts the run
- teams can add their own path blocklist
- nothing auto-merges
Your first Outrider run is one command away
Start from your own brief or let Outrider find a change. Free to install and runs in GitHub Actions.