Skip to main content
Nav: Manage > Connectors | URL: /connectors Every source feeds a specific part of the next decision: GitHub sets the ranking baseline, a model provider powers the drafts, Linear and Jira flag interfaces under active work, W&B feeds the gate. Connect each account once here; reference it per-project under Projects → Sources. 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.

​
GitHub

What it feeds: the ranking baseline — every merge and revert re-weights the candidate pool — plus the write path for everything agents author. Setup:
  1. Click Connect on the GitHub card.
  2. Install the Remyx GitHub App on your organization or account.
  3. Select the repositories to grant access to.
The connector is a GitHub App, not a plain OAuth grant. Remyx authenticates as the App and mints short-lived, repo-scoped tokens on demand; the App’s private key never leaves the Remyx engine. The base token covers contents, pull-requests, issues, and workflow (needed to install the agent workflow), and permissions like discussions:write are layered on only when your installation actually granted them.

​
The remyx[bot] identity

Because the connector is a GitHub App, everything Remyx does on your repos is authored by remyx[bot] — setup PRs, draft PRs, Issues — never as you, so it’s clear at a glance which artifacts an agent originated. Commits show as Verified. The bot also answers @remyx-ai mentions on agent-opened PRs and Issues with grounded, read-only replies; see Briefs.
The in-app Quickstart uses a repo-scoped OAuth connection (it needs fork rights for the demo repo); agent setup outside the quickstart runs on the App. If both exist, the App is preferred.

​
Model providers: Anthropic (Claude), Z.ai (GLM), Moonshot AI (Kimi)

What they feed: the agents themselves. Runs execute in your repo’s GitHub Actions using your own model key, pushed to the repo as a secret at provisioning time — Anthropic as ANTHROPIC_API_KEY, Z.ai as ZAI_API_KEY, Moonshot as MOONSHOT_API_KEY. Setup: click Connect on the provider’s card and paste an API key from that provider’s console. The key is validated against the provider before it’s stored and encrypted at rest; it’s used only for your own runs, billed to your provider account. Connect one to get started; connect several to choose a backend per agent (or per dispatch), or to run the two-tier drafter/refiner with different tiers on different providers. See Model backends for the full comparison.
Each provider bills usage to its own account — make sure the account behind the key has API credit. (For Anthropic specifically, API credits are separate from a Claude Pro/Max subscription.)
Prefer your own MCP client? You can also point Claude Code, Claude Desktop, or Cursor at the Remyx MCP server with your Remyx API key — see the MCP Server reference.

​
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: gate evidence — eval runs and metrics feed the decision policy at the gate, and W&B Launch is a compute backend for scored validation runs. 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.

​
Hugging Face

Connects via OAuth so Remyx can read model and dataset metadata. Your Hugging Face token (for gated models in validation runs) lives on this connector card. What it feeds: validation compute — Remyx dispatches scored validation jobs to Modal Sandboxes (GPU-capable) on your account. Enter your Modal token ID and secret. See Evaluation.

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

Model backends

How the three LLM providers compare per run

Projects

Reference connected sources per project

Agents

What provisioning pushes to the repo

MCP Server

Use Remyx from your own MCP client