Install the Remyx CLI, authenticate, and manage Research Interests, recommendations, and search from your terminal.
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.
Remyx authenticates API calls with a bearer token. Export it before running commands:
export REMYXAI_API_KEY=<your-key-here>
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.
Research Interests define what you care about. They drive the recommendation engine — each interest has its own context and daily recommendation cadence.
Shows today’s top recommendations grouped by Research Interest. Each entry includes the resource title, source type, relevance score, and why it was recommended.
Flat list of all recommendations (not grouped by interest). Supports more granular filtering.
Flag
Description
Default
--interest, -i
Filter by interest name or UUID
(all interests)
--limit, -n
Max results (1-50)
20
--period, -p
today, week, or all
all
--source-type, -s
Filter by source type (arxiv_paper, github_repo, etc.)
(all types)
--format, -f
text or json
text
--full
Show full reasoning text
—
# Papers for a specific interest from this weekremyxai papers list --interest "Retrieval-Augmented Generation" --period week# Only GitHub reposremyxai papers list --source-type github_repo
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.
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.
Flag
Description
Default
--repo
Target repo as owner/name or a GitHub URL
(detected from the current directory’s git remote)
--interest, -i
Research Interest UUID to wire in
(prompted / see --auto-interest)
--auto-interest
Auto-create a Research Interest from the repo (mutually exclusive with --interest)
—
--mode
auto (provision + merge setup PR + first run), review (provision + open setup PR to review), off (create the interest only)
auto
--anthropic-key
Anthropic API key to connect as the model provider (Claude Code). Falls back to $ANTHROPIC_API_KEY
(only used if no provider is connected)
--no-wait
Don’t block polling for App install / provisioning; print next steps and return
—
--dry-run
Print the plan and exit without making changes
—
--yes, -y
Skip the confirmation prompt
—
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.
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.
auto (open + merge setup PR + dispatch first run) or review (open the setup PR for you to merge)
auto
--anthropic-key
Anthropic key to set as the ANTHROPIC_API_KEY repo secret. Falls back to $ANTHROPIC_API_KEY, then prompts
—
--dry-run
Print the plan + rendered workflow and exit
—
--yes, -y
Skip the confirmation prompt
—
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.
See Automated discovery PRs for what the action does once installed, its configuration inputs, and how to review the PRs it opens.
Export the key in the same shell session you use for remyxai. Verify with:
echo $REMYXAI_API_KEY
If empty, set it:
export REMYXAI_API_KEY=<your-key-here>
Command not found: remyxai
The binary may not be on your PATH. Check where pip installed it:
pip show remyxai | grep Location
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.
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.