Skip to main content
The Remyx CLI is the command-line companion to Remyx Studio. Manage Research Interests, get personalized recommendations, search across papers, repos, and models, and install automated discovery PRs on a repo — all from your terminal. Source and latest command definitions live in the official repo.

Requirements

Installation

Verify the executable is on your PATH:

Authentication

Remyx authenticates API calls with a bearer token. Export it before running commands:
The client uses this variable when calling https://engine.remyx.ai/api/v1.0. Do not commit keys; use your shell profile, .env (with a loader), or your CI secret store.
Your CLI auth is always a single personal key (rmxu_) in REMYXAI_API_KEY. When Outrider provisions a repo (outrider init / setup-local, or interests with --automate review/auto), it writes a scoped automation key (rmxa_) into the repo’s secrets as REMYX_API_KEY. Your personal key stays on your machine. See API key scopes for the difference.

Command Overview

Run remyxai <group> --help for all options in a group.

Research Interests

Research Interests define what you care about. They drive the recommendation engine — each interest has its own context and daily recommendation cadence.

List Interests

Shows all your Research Interests with name, context preview, daily count, and active status.

Create an Interest

Run remyxai interests create with no flags for an interactive prompt that walks you through each field.

Create from a GitHub repo

Builds an interest from a repo’s profile (languages, topics, README, dependencies) instead of free text. Pass --automate review or --automate auto to also provision Outrider on that repo in the same step, the same flow as outrider init.

Create from a project’s experiments

Builds an interest from a project’s experiments. The <PROJECT> argument accepts a project name or UUID. The interest tracks the project by default, so new experiments keep it current; pass --no-auto-update to take a one-time snapshot instead.

Get Interest Details

The --interest flag accepts either a name (case-insensitive) or a UUID.

Update an Interest

Updating the context invalidates the pre-ranked recommendation pool. Run remyxai papers refresh afterward to get fresh results immediately.

Toggle Active Status

Toggles between active and inactive without deleting the interest or its recommendation history.

Delete an Interest

Prompts for confirmation. Pass --yes to skip:

Recommendations

Get personalized resource recommendations based on your Research Interests.

Daily Digest

Shows today’s top recommendations grouped by Research Interest. Each entry includes the resource title, source type, relevance score, and why it was recommended.

List Recommendations

Flat list of all recommendations (not grouped by interest). Supports more granular filtering.

Refresh Recommendations

Triggers an async recommendation refresh. By default, refreshes all active interests. Use --wait to block until complete.

Check Refresh Status

Poll the status of an async refresh task (from papers refresh without --wait).
Search across the Remyx resource index — papers, repos, models, and datasets with Docker availability filtering.

Query

Get Resource Details

Returns detailed information for a specific resource by arXiv ID, including full abstract, Docker status, Dockerfile contents, and reference summary.

List Recent Resources

Browse recently added resources with pagination.

Catalog Statistics

Shows aggregate stats: total assets, Docker availability counts, category breakdown, and citation classification coverage.

Outrider

Install automated discovery PRs on a GitHub repo without leaving the terminal. The CLI drives the same “set it up for me” flow as the web app — your local git is never touched.

Install on a repo

This drives the Remyx engine so the Remyx GitHub App (remyx-ai[bot]) sets the repo secrets, writes the workflow, opens a bot-authored setup PR, and — in auto mode — merges it and fires the first run. No personal gh token is needed; only your REMYXAI_API_KEY.
Connect the GitHub and Claude Code (Anthropic API key) integrations in Connectors first; outrider init uses those connections. If the GitHub App isn’t installed on the repo, the command surfaces the install link, and you can pass --anthropic-key to set the Anthropic key the first time.

Install without the GitHub App

For organizations that can’t grant a third-party GitHub App yet (e.g. a pending security review), setup-local does the same provisioning using your own authenticated gh CLI instead of the Remyx App — nothing new to security-review. The running Action opens PRs with the repo’s built-in GITHUB_TOKEN.
setup-local needs an authenticated gh (run gh auth login, or set $GITHUB_TOKEN with repo + workflow scopes) and admin on the target repo. The only runtime Remyx dependency is the REMYX_API_KEY the workflow uses.

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.
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.

Route a run at a different model provider

Outrider runs Claude Code, and it can route those calls at any Anthropic-Messages-compatible provider. A setup-local workflow declares provider and model as dispatch inputs and picks the right auth environment variable per run, so one workflow can A/B Anthropic against an alternate such as z.ai’s GLM:
--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 auth-header details.

Set a provider’s API key on a repo

set-provider-secret writes a provider’s API key into the repo’s secrets safely. It reads the key from a file, strips the trailing newline, and sidesteps the gh secret set --body - truncation trap that otherwise stores a literal - and breaks every run with a 401.
See Automated discovery PRs for what the action does once installed, its configuration inputs, and how to review the PRs it opens.

Quick Reference


Troubleshooting

Export the key in the same shell session you use for remyxai. Verify with:
If empty, set it:
The binary may not be on your PATH. Check where pip installed it:
On Linux, pip install without sudo puts the binary in ~/.local/bin. Either add that to your PATH or install with sudo pip install remyxai.
Run remyxai papers refresh --wait to trigger a fresh ranking. If recommendations show for --period week but not today, they were generated on a previous day. Refreshing will surface the latest resources.

Next Steps