Requirements
- Python 3 and
pip - A Remyx API key (get one here)
Installation
PATH:
Authentication
Remyx authenticates API calls with a bearer token. Export it before running commands: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
Create an Interest
Create from a GitHub repo
--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
<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
--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
Delete an Interest
--yes to skip:
Recommendations
Get personalized resource recommendations based on your Research Interests.Daily Digest
List Recommendations
Refresh Recommendations
--wait to block until complete.
Check Refresh Status
papers refresh without --wait).
Search
Search across the Remyx resource index — papers, repos, models, and datasets with Docker availability filtering.Query
Get Resource Details
List Recent Resources
Catalog Statistics
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
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. Asetup-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
REMYXAI_API_KEY missing or invalid
REMYXAI_API_KEY missing or invalid
Export the key in the same shell session you use for If empty, set it:
remyxai. Verify with:Command not found: remyxai
Command not found: remyxai
The binary may not be on your On Linux,
PATH. Check where pip installed it:pip install without sudo puts the binary in ~/.local/bin. Either add that to your PATH or install with sudo pip install remyxai.Digest shows 'no new recommendations today'
Digest shows 'no new recommendations today'
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
- Set up automated discovery PRs on a repo with
remyxai outrider init - Browse commands and source in the Remyx CLI repo
- Connect the MCP server for AI-powered experiment management