Outrider configuration

​

Manual setup

​

Review the installation

​

Manual install

name: Outrider
on:
  schedule:
    - cron: '0 14 * * 1'   # Mondays 14:00 UTC; pick any cadence
  workflow_dispatch:
    inputs:
      mode:
        description: 'recommend (default), brief, smoke, weekly-summary'
        required: false
        default: ''
      pin-arxiv:
        required: false
        default: ''
      search-method:
        required: false
        default: ''
      lead-content:
        description: 'A gap analysis in recommend mode; the whole spec in brief mode'
        required: false
        default: ''
      publish:
        description: 'pr (default) or branch'
        required: false
        default: 'pr'
      claude-timeout:
        description: 'Seconds per agent phase (the name remyxai outrider trigger sends; agent-timeout is the same ceiling)'
        required: false
        default: '1500'
concurrency:
  group: outrider-${{ inputs['pin-arxiv'] || inputs['start-from-ref'] || github.run_id }}
  cancel-in-progress: false
jobs:
  recommend:
    runs-on: ubuntu-latest
    timeout-minutes: 55
    permissions:
      contents: write
      pull-requests: write
      issues: write
      # discussions: write   # only for mode: weekly-summary
    env:
      REMYX_API_KEY: ${{ secrets.REMYX_API_KEY }}
      ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}   # or ZAI_API_KEY, MOONSHOT_API_KEY, ...
    steps:
      - uses: remyxai/outrider@v1
        with:
          interest-id: 'YOUR-INTEREST-UUID-HERE'
          mode: ${{ inputs.mode }}
          pin-arxiv: ${{ inputs.pin-arxiv }}
          search-method: ${{ inputs.search-method }}
          lead-content: ${{ inputs.lead-content }}
          publish: ${{ inputs.publish }}
          claude-timeout: ${{ inputs.claude-timeout }}

​

From the CLI

pip install remyxai

# authenticate the CLI with your Remyx API key
export REMYXAI_API_KEY="YOUR_REMYX_API_KEY"

# install Outrider on the repo and auto-create a Research Interest from it
remyxai outrider init --repo owner/name --auto-interest

remyxai outrider setup-local --repo owner/name --auto-interest

​

From the UI

​

By hand

​

Identity and install

​

Steer Outrider from your repo

• REVIEW.md (or .github/REVIEW.md) is the highest-precedence signal: your review conventions, test bar, scope stance, benchmark expectations and anti-patterns, threaded into the drafter and the downstream fidelity and convention passes. A template is in the action repo at docs/REVIEW-template.md.
• Agent instruction files, in this order: CLAUDE.md, AGENTS.md, .cursorrules, .github/copilot-instructions.md, CONTRIBUTING.md, CONTEXT.md. Lint and house-style rules are read from the repo’s own config (ruff, pre-commit, black, flake8) rather than hardcoded.
• ENVIRONMENTS.md (or ENVIRONMENT.md), written by the workflow, tells the agent how to set up and run the repo’s environment.
• Discussions, ranked by overlap with the candidate paper. A fork without Discussions falls back to its parent repo’s.
• Recent merged PRs supply the PR-body template and contributor conventions the convention pass applies; .github/ISSUE_TEMPLATE/ shapes Issues.
• Direction signals gate the strictest pick shape, a new capability your repo lacks: a README roadmap heading, a recurring theme in CONTEXT.md, or an open maintainer-authored [RFC] Issue. Without at least one, extension-shaped candidates are rejected.
• Not re-recommending a paper. A paper is treated as discharged when an Outrider-opened Issue exists for it (open or closed), or a maintainer-opened Issue links its arXiv id. Reopen the Issue to put it back in play.

​

Configuration

​

Outputs

steps:
  - uses: remyxai/outrider@v1
    id: outrider
    with:
      interest-id: ${{ vars.REMYX_INTEREST_ID }}
  - name: Ping the channel when a draft is ready for review
    if: steps.outrider.outputs.chain_draft_dropped == 'true'
    run: echo "ready: ${{ steps.outrider.outputs.pr_url }}"

​

Concurrency

​

Guardrails

• Fixed block: .github/workflows/** is always off-limits. An agent editing its own workflow file is the one change that compounds silently across future runs. commit_and_push strips any workflow edit before the push and lists the dropped paths in the step summary. guardrails-blocklist adds your own globs on top, and blocklist matches always win.
• Risky surface (flag, not block): a diff that touches dependency manifests or lockfiles, CI pipelines, git hooks, container or shell scripts is forced to draft even under draft-mode: never, labelled risky-surface, and gets a “review before landing” section in the PR body listing the files. A new method that genuinely needs a dependency still opens, just flagged.
• Integration checks (post-session, pre-push): at most 3 new .py files per run, and at least one newly added function or class must be invoked from another changed file; an import alone doesn’t count. Violations terminate the run before any push (rejected_path_violations); orphan code downgrades the run to an Issue.
• Canary: the agent must echo a per-run canary token in its final commit. A missing or wrong canary is the fingerprint of an injection that hijacked the agent’s output, and downgrades routing from PR to Issue (issue_opened_canary_missing).
• Validators: stub density, the test-integration gate, a self-review orphan check, a diff-risk score gate, and an outbound secret scan that aborts the run rather than redacting (aborted_secret_in_payload). Each has its own Issue-route or abort status.

​

Costs

• Model usage: on Anthropic, a full PR-route run with the inline chain is about $5–6; recommend-only (chain: false) is $1–3. Other backends scale with their per-token rates, which differ by an order of magnitude between a budget model and a flagship one, so compare backends on your own repo rather than on a rule of thumb: every run reports its own cost_usd, and Reports → Costs breaks spend down by agent, provider and model. A run that skips after the selection pass costs less still: it reads the repo to verify fit, then exits.
• GitHub Actions: minutes on ubuntu-latest. A run takes a few minutes to around twenty depending on the backend, the repo, and whether the chain runs; provisioned installs cap each agent phase at 60 minutes and the job at 90.
• Remyx API: included.

​

Weekly digest

​

Next steps