What to connect
The first eligible Validate run can use a Remyx-funded model allowance when available. Outrider runs in GitHub Actions with its configured provider.
Connect GitHub
For Validate, install the Remyx GitHub App on the repositories you want to evaluate. In Studio, connect or claim the installation and confirm that Validations are enabled. For Outrider, use the Studio Quickstart to authorize GitHub, choose a repository, and configure the workflow. Open Connectors in Studio · Quickstart
Manage GitHub repository access and turn on Validate for the connected installation.
Choose a model provider
A model provider supplies the model used for eligible tasks. The coding-agent backend determines how Outrider prepares code. The available combinations and credential requirements are documented separately. Model providers · Validate model selectionOther integrations
Use the catalog below to find available integrations, setup requirements, and any permissions or usage costs. An integration shown as planned or requiring team setup is not part of the standard self-service flow. Nav: Manage > Connectors | URL:/connectors
Each connector card shows a status chip — connected, not connected, enterprise, or coming soon — and connected cards offer Test connection, Replace credentials (for key-based connectors), and Disconnect.
Catalog
Enterprise connectors (MLflow, Databricks, Snowflake, AWS, GCP, Azure) are private-network setups done with the Remyx team — use the Contact us card.
Linear
What it feeds: draft-vs-discussion routing — open tickets flag interfaces under active work, which routes risky candidates to discussion instead of drafts. Decisions link back to issues, and@remyx mentions in comments get agent replies.
Setup: click Connect, authorize Remyx, then link Linear where you use it — as a project source, or as the durable store for two-tier gap analyses via the action’s linear-api-key input.
Jira
Same routing signal as Linear, for Jira Cloud teams. Sync uses the Jira Cloud v3 webhook API (offline_access + manage:jira-webhook scopes); inbound deliveries are verified against the Atlassian webhook identifier header. If auth errors appear after an extended period, disconnect and reconnect to refresh.
Slack
Inbox items, daily digests, and weekly portfolio summaries in your channels, plus a managed agent: mention@Remyx to get your digest, list agents’ output, or ask about a run. Install the app, pick a default channel, and /invite @Remyx.
Weights & Biases
What it feeds: two things. Gate evidence: eval runs and metrics feed the decision policy at the gate, and W&B Launch is a compute backend for experiment validation. And Validate runs: when a spec declareslogging.wandb or requires: [wandb], or the PR template and harness call for W&B, your key is injected into the measurement pods so the repo’s own wandb.init() lands in your project, tagged remyx-validate. The started comment says where results will land; the verdict links the dashboards. Never a Remyx key.
Setup: paste a W&B API key from wandb.ai/authorize (plus an optional entity and self-hosted URL). The key is validated against the W&B GraphQL viewer query before it’s saved. A Validate spec that logs to W&B on an account with no connection, a wrong entity, or an invalid project is refused before anything runs.
Hugging Face
Connects via OAuth so Remyx can read model and dataset metadata. Your own Hugging Face token lives on this card; Validate injects it into measurement pods so a test can pull gated models and datasets on your access, never Remyx’s.Modal
What it feeds: experiment-validation compute for the eval-template path: Remyx dispatches scored jobs to Modal Sandboxes (GPU-capable) on your account. Enter your Modal token ID and secret. See Evaluation. PR Validate runs on Remyx compute and does not use this connector.Permissions and credential handling
Review the detailed scopes, secret-handling rules, and installation controls before connecting a repository or provider.Security
- Credentials and OAuth tokens are encrypted at rest; keys are validated against their provider before being stored.
- Webhook payloads are verified for authenticity on every request.
- Disconnecting is immediate: agents and gates that reference the connection stop working until it’s reconnected. A Fix card in the Inbox (
model_key_push) appears when an agent’s provider key could not be pushed to its repo and needs a reconnect.
Model providers and coding agents
Outrider runs in your repository’s GitHub Actions environment. Its coding agent uses a compatible model provider, with the selected key stored in the repository’s Actions secrets. With--github-secrets-only or client-sealed credentials, Remyx does not retain a copy of that provider key.
Validate uses a connected provider key on the server to design or repair tests. It does not push that key to your repository, and a client-sealed key cannot be used for Validate. Calls made with your own model-provider key are billed by that provider; hosted validation compute is charged under the Validate billing rules.
Backboard R-CLI is a coding-agent backend with its own routing credential, not a model provider. For supported agent/provider combinations, API families, secret names, default models, timeout settings, and routing behavior, use the Model backends reference. The Validate model-selection reference explains how it chooses a provider.
Connect a model provider
Select the provider in Studio → Connectors. The connection flow validates credentials and stores them encrypted at rest. OpenRouter uses an OAuth flow to mint a revocable provider key. For a local Outrider installation that does not use the Remyx GitHub App, put the key directly into the repository’s GitHub Actions secrets. The following commands read a key from a local file; they do not print it to the terminal.Related
Model backends
How the LLM providers compare per run
Validate
Set up, the Validations switch, and the model it uses
Projects
Reference connected sources per project
Agents
What provisioning pushes to the repo
MCP Server
Use Remyx from your own MCP client