Skip to main content
This guide mirrors the in-app Quickstart at studio.remyx.ai/start: connect two accounts, choose where the agent runs, fire a real run, and watch a draft PR open under remyx[bot]. Nothing here is scripted — every run is live. Each step’s CLI equivalent (where one exists) is called out below. If you prefer the terminal, install and authenticate once:

​
1. Connect your GitHub account

Open the Quickstart and click Connect GitHub. The connection is used to:
  • Fork the demo repo — created under your account, yours to delete
  • Install the agent workflow — one workflow file + repo secrets, via a setup PR
  • Open draft PRs & Issues — authored as remyx[bot], never as you
  • Revoke anytime — from GitHub settings or the Connectors page
Authorize in the tab that opens; the step completes itself when GitHub confirms (✓ GitHub connected).
No CLI equivalent — the GitHub authorization is a browser flow. From the terminal, remyxai outrider init detects a missing GitHub App install and prints the install link.

​
2. Connect your model provider

Runs use your own model key — connect one provider now; add or switch later under Connectors. Pick one of: The key is validated against the provider before it’s stored, encrypted at rest, and used only for your own runs. See Model backends for how the three compare on cost and speed.

​
3. Choose where the agent runs

Two tracks — like a demo with worked examples, except both are real runs:
Fork remyxai/peft — Remyx’s fork of the Hugging Face fine-tuning library, a codebase you may already know, so the diff speaks for itself. A set of papers is pre-matched, each with a curated draft branch already seeded into your fork. A run warm-starts from that branch (via start-from-ref) and refines it into a draft PR in minutes.Click Fork it & install the agent. Remyx forks the repo under your account, installs the Outrider workflow through a setup PR, and pushes your model key as a repo secret.
CLI equivalent

​
4. Run it

On the set example track, pick one of the pre-matched papers — for instance Riemannian Preconditioned LoRA (arXiv 2402.02347) or AdaMoLE: adaptive mixture of LoRA experts (arXiv 2405.00361) — each shown with its curated branch’s diffstat so you can inspect the change on GitHub before running. Or click Or let Outrider choose: exactly like a scheduled run, it audits the pool, selects the best-fit deliverable paper, and implements it from scratch (~15–20 min). On the your own repo track there’s nothing to pick — Outrider dispatches automatically once the agent is ready, selects the strongest anchored paper itself, and implements it. Everything it decides is in the run log.
If the candidate pool is still building for a fresh repo, the run starts automatically the moment it’s ready (the app retries for you).

​
5. Watch it land — then it’s always on

A warm-start run takes a few minutes: checkout of the curated draft, a review-and-refine pass, then the draft PR opens on your fork under remyx[bot]. An own-repo run takes 15–20 minutes and ends in one of four real outcomes: The repo is now a full agent: it shows up in Agents, the fleet Report, and your Inbox, and future runs happen on its schedule with you at every merge.
No remyxai equivalent for watching a run — it executes in your repo’s GitHub Actions, so the run log lives there (gh run watch gives you a terminal view).

​
What you just set up

Discovery grounded in the repo (the interest reads its code and history), ranked candidates with the evidence behind them, drafts that arrive as reviewable PRs — and an Inbox that only ever asks for decisions a human should make.

Inbox

Where drafts and decisions wait for you

Your agent's report

Runs, Direction, Activity trace, and Configuration for your new agent

Model backends

Anthropic, Z.ai, Moonshot — and the two-tier drafter/refiner pattern