Remyx AI CLI

Install Outrider on a repo, and Remyx handles the loop end-to-end: discovers newly-published arXiv methods matching your team's work, implements them as draft PRs, and validates each against the paper's reference before it lands.

Install

pip install remyxai
export REMYXAI_API_KEY=<your-key>   # from engine.remyx.ai/account

Quickstart

Install Outrider on a repo — server-side, no local git touched:

remyxai outrider init --repo your-org/your-repo --auto-interest

By default this installs the two-tier setup: a daily drafter that
explores candidates as fork branches, plus a weekly refiner that promotes
the strongest draft into a ready-for-review PR (crons stay off — drive runs
with remyxai outrider trigger or your own dispatcher). The Remyx GitHub App
authors everything (remyx-ai[bot]).

Agents and model providers

Two independent axes. --agent picks the coding-agent CLI that does the work;
--provider picks the model behind it.

Agent	`--agent` value	Speaks
Claude Code	`claude` (default)	Anthropic Messages
OpenAI Codex	`codex`	OpenAI Responses
Backboard R-CLI	`backboard`	its own router

Provider	`--provider` value	Example models
Anthropic	`anthropic`	`claude-opus-4-8`
OpenAI	`openai`	`gpt-5.4-mini`
Z.ai	`zai`	`glm-5.3`
Moonshot AI	`moonshot`	`kimi-k3`
OpenRouter	`openrouter`	`z-ai/glm-5.3`

Not every pair is valid — an agent speaks one API family and a provider serves
one or more — so trigger rejects an impossible 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.

Leave --agent unset and nothing changes: existing installs keep the Claude
Code path they have today. Both tables come from the action's published
compatibility matrix, vendored into this package, so they cannot drift from
what the action actually supports.

Unset, each tier follows your connected provider — no vendor is assumed.
One provider covers both tiers; tune per tier, or opt out of two-tier entirely:

# Both tiers on one provider
remyxai outrider init --repo your-org/your-repo --auto-interest --provider moonshot

# Mix providers per tier (cheap drafter + capable refiner)
remyxai outrider init --repo your-org/your-repo --auto-interest \
  --drafter-provider zai --drafter-model glm-5.3 \
  --refiner-provider anthropic

# Plain single-file workflow instead of two-tier
remyxai outrider init --repo your-org/your-repo --auto-interest --single-tier

# A non-default agent, per dispatch
remyxai outrider trigger --repo your-org/your-repo \
  --agent codex --provider openai --model gpt-5.4-mini

--agent is on trigger, setup-local and init. One caveat on init: it
provisions server-side, so the flag only takes effect once the engine supports
the agent axis — the CLI reads the provisioned workflow back and tells you
plainly if it was ignored, rather than reporting success. setup-local --agent
works on any engine today.

Flag	Applies to	Default
`--provider` / `--model`	both tiers	your connected provider / each tier's default
`--drafter-provider` / `--drafter-model`	daily drafter only	shared provider / tier default
`--refiner-provider` / `--refiner-model`	weekly refiner only	shared provider / tier default
`--single-tier`	—	off (two-tier is the default)
`--force`	—	off (re-provision a repo that's already installed)

Provider keys

Every tier needs its provider's API key in the repo, or the first run fails
auth in under a second. init handles both halves:

every provider you've connected at engine.remyx.ai/integrations is pushed
server-side by the engine — one per tier, so mixing providers needs nothing
local;
a tier pointed at a provider you haven't connected is pushed by init
from this shell — ANTHROPIC_API_KEY, ZAI_API_KEY, or MOONSHOT_API_KEY
(via gh).

A tier with no key either way stops the command before anything is
provisioned; --dry-run reports the same routing. Setting a key on a repo
after the fact:

remyxai outrider set-provider-secret --repo owner/name \
  --provider moonshot --key-from ~/moonshot-key

Changing the tier config of a repo that's already installed needs --force —
plain re-runs report "already enabled" and leave the workflow files alone:

remyxai outrider init --repo your-org/your-repo --interest <uuid> \
  --refiner-provider moonshot --refiner-model kimi-k3 --force

Trigger a run — three modes of specificity:

# 1. default — Remyx picks from the ranked pool; Outrider's audit augments via agentic search
remyxai outrider trigger --repo your-org/your-repo

# 2. --search-method — override the pool with a free-text query, implement the top hit
remyxai outrider trigger --repo your-org/your-repo \
  --search-method "riemannian preconditioning LoRA optimizer"

# 3. --pin-arxiv — exact paper, bypasses selection entirely
remyxai outrider trigger --repo your-org/your-repo --pin-arxiv 2402.02347v3

Refinement runs build on work that already exists — yesterday's drafter
branch, or a third party's stalled PR branch — with a written gap analysis as
leading context:

remyxai outrider trigger --repo your-org/your-repo \
  --start-from-ref outrider/deim-draft \
  --lead-content-file gap-analysis.md \
  --staged-synthesis --fidelity-policy advisory

--start-from-ref is what the agent builds on; --ref only picks which
branch the workflow file itself comes from. When firing several dispatches at
one repo, add --wait-for-slot: the workflow's concurrency group holds exactly
one pending run, so back-to-back dispatches otherwise cancel each other.

Documentation

Topic	Doc
Pipeline: discovery → implementation → validation	docs/pipeline.md
Method-targeted runs + team-scale patterns	docs/method-targeted-runs.md
Research Interests: three ways to create one	docs/research-interests.md
Install paths, credentials, bulk-install	docs/install-paths.md
Full command reference	docs/commands.md

Development

git clone https://github.com/remyxai/remyxai-cli
cd remyxai-cli
pip install -e .
pytest tests/

Links

Outrider — the GitHub Action this CLI installs
engine.remyx.ai — web app, account settings, API key
Issues — bug reports and feature requests

Package profile

remyxai

Dependencies

Details

Package description