Skip to main content
Nav: Manage > Connectors | URL: /integrations Every experiment generates artifacts across multiple tools: a PR in GitHub, a ticket in Linear, a thread in Slack. Without linking them, context is fragmented and the experiment record is incomplete. Connectors link Remyx to the tools your team already uses. Experiments connect to PRs, tickets, and Slack conversations, and changes flow bidirectionally via webhooks. Each experiment becomes a single source of truth regardless of where the work happens.

​
Available Connectors

The Connectors page organizes integrations by category. Use the category dropdown to filter: Enterprise connectors (MLflow, Databricks, Snowflake, AWS, GCP, and Azure) are available by contacting the Remyx team. Each connector card shows its logo, a description, and a connection status chip. Connected integrations show a green Connected badge and a gear icon for settings.

​
GitHub

What it does:
  • Links PRs to experiments with status sync via webhooks
  • Provides repo file tree access for launch context generation
  • Enables the Claude Code implementation pipeline
  • Provisions and authors automated discovery PRs as a bot identity
Setup:
  1. Click Connect on the GitHub card
  2. Install the Remyx GitHub App on your organization or account
  3. Select repositories to grant access to
The connector is a GitHub App. 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 automated discovery-PR workflow).Tokens are scope-gated: Remyx layers discussions:write and actions:write onto the base set only when your installation actually granted those permissions. If you didn’t grant a permission, it’s never requested on the minted token.

​
The remyx-ai[bot] identity

Because the connector is a GitHub App, actions Remyx takes on your repo are authored by remyx-ai[bot], a distinct identity of its own. This is what opens the setup PR and the recommendation PRs when you turn on automated discovery PRs, so it’s clear at a glance which PRs originated from Remyx. The integrations page shows the App as the connected GitHub card; disconnecting it clears the installation. Beyond opening PRs and issues, the bot now answers @remyx-ai mentions on the pull requests and issues opened by automated discovery PRs. Mention it in a comment and it replies with a grounded, read-only answer about the change. It reads the PR/issue context to respond but never edits code or pushes commits in that flow. See Deep Research for how the grounded answers are assembled.

​
Linear

What it does:
  • Auto-creates Linear issues when experiments are created
  • Syncs status changes bidirectionally
  • Supports label actions (ship, abandon) to update experiment state
  • @remyx mentions in comments trigger the AI agent
Setup:
  1. Click Connect on the Linear card
  2. Authorize Remyx when prompted
  3. Link a Linear project in Project Settings
Webhook events:

​
Jira

What it does: Same bidirectional sync as Linear, adapted for Jira Cloud:
  • Auto-creates Jira issues linked to experiments
  • Status transitions sync both directions
Setup:
  1. Click Connect on the Jira card
  2. Authorize Remyx when prompted
  3. Link a Jira project in Project Settings
Jira sync uses the Jira Cloud v3 webhook API, authorized with the offline_access and manage:jira-webhook scopes. Inbound webhook deliveries are verified against the Atlassian webhook identifier header before Remyx acts on them.If you encounter auth errors after an extended period, disconnect and reconnect at Connectors to refresh the connection.

​
Slack

What it does: Adds a managed AI agent to your Slack workspace. Mention @Remyx in any channel to:
  • Get your latest research digest
  • List and filter experiments
  • Create new experiments
  • Log decisions
  • Ask questions about experiment status
Setup:
  1. Click Connect on the Slack card
  2. Install the Remyx AI app to your workspace
  3. Select a default channel for digest delivery
  4. In Slack, invite the bot: /invite @Remyx
Scheduled digests: Scheduled digest delivery is coming soon. For now, use @Remyx show me today's digest to get recommendations on demand.

​
Claude Code

This is where you connect your Anthropic API key. Remyx runs Claude Code for you in a sandboxed container; the key is encrypted and used only when an implementation runs. What it powers:
  • The autonomous implementation pipeline — Remyx generates a PR for a scoped experiment.
  • Automated discovery PRs — when you provision Outrider, Remyx sets this key as the repo’s ANTHROPIC_API_KEY secret so the action can implement and self-review changes.
Setup:
  1. Click Connect on the Claude Code card.
  2. Paste an Anthropic API key (sk-ant-...) from console.anthropic.com.
Requires Anthropic API credits. This uses the Anthropic API, billed separately from a Claude Pro or Max subscription. Add credits at console.anthropic.com/billing.
Use Remyx from your own MCP client instead. The Claude Code card also offers a local option: point your own Claude Code, Claude Desktop, or Cursor at the Remyx MCP server (authenticated with your Remyx API key) to manage experiments and discover resources from your editor.
See the MCP Server reference for the full tool list; get your Remyx API key at Account > API Access.

​
Weights & Biases

What it does: Pulls your W&B runs into the experiment detail view as external validation data, so tracked training and evaluation runs sit alongside the experiment’s hypothesis and decision. Setup:
  1. Click Connect on the Weights & Biases card.
  2. Paste a W&B API key from wandb.ai/authorize.
The key is validated against the W&B GraphQL viewer query at connect time. If the key can’t resolve a viewer, the connection is rejected before it’s saved.
W&B is also a compute backend for scored validation runs (W&B Launch); see Evaluation.

​
HuggingFace

What it does:
  • Connects via OAuth so Remyx can read model and dataset metadata and pull it into experiment detail.
  • Holds your HuggingFace token. It moved off the Account page and now lives on this connector card.
Setup:
  1. Click Connect on the HuggingFace card.
  2. Authorize Remyx via HuggingFace OAuth when prompted.
If you previously set a HuggingFace token on the Account page, reconnect here; the token is now managed through this connector.
What it does: Makes Modal a connectable compute provider for validation runs. Once connected, Remyx can dispatch scored validation jobs to your Modal account. Setup:
  1. Click Connect on the Modal card.
  2. Enter your Modal endpoints and credentials in the connection modal.
Modal-backed validation is wired into the evaluation flow; see Evaluation for how validation runs are scored.

​
Security

  • All OAuth tokens are encrypted at rest
  • Webhook payloads are verified for authenticity on every request
  • Connections can be revoked at any time from the Connectors page

​
Troubleshooting

Check that your project has a linked Linear project or Jira board in Project Settings. Ticket creation requires knowing which project to create issues in.
Verify the webhook subscription exists in your external tool. For Linear: Settings > API > Webhooks. For GitHub: Settings > Webhooks on the repo. If missing, disconnect and reconnect the integration.
Disconnect and reconnect at Connectors to refresh the connection.
Verify: "type": "http" (not "sse"), URL is https://mcp.remyx.ai/mcp, API key is valid. Check at Account > API Access.
Ensure the bot is invited to the channel (/invite @Remyx) and the connection shows as active at Connectors.

MCP Server

Full MCP tool reference

Project Settings

Link Linear/Jira projects to projects

Automated discovery PRs

What the GitHub App provisions and authors as remyx-ai[bot]