> ## Documentation Index
> Fetch the complete documentation index at: https://docs.remyx.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Connectors
> Connect GitHub, Linear, Jira, Slack, and Claude Code to your Remyx workspace
**Nav:** Manage > Connectors | **URL:** [`/integrations`](https://engine.remyx.ai/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:
| Category | Connectors |
| -------------------------- | ------------------------------------------------------------- |
| **Communication** | Slack |
| **Project Management** | Linear, Jira |
| **Code & Version Control** | GitHub |
| **AI Development** | Claude Code |
| **Coming Soon** | HuggingFace, Statsig, LaunchDarkly, W\&B, LangChain, and more |
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](/platform/experiments/outcomes#origin-section) generation
* Enables the Claude Code implementation pipeline
* Provisions and authors [automated discovery PRs](/platform/discover/outrider) 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**, not a personal access token. Remyx authenticates as the App and mints short-lived, repo-scoped tokens on demand; the App's private key never leaves the Remyx engine. Requested scopes include `contents`, `pull-requests`, `issues`, and `workflow` (needed to install the Outrider recommendation workflow).
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, not your personal account and not `github-actions[bot]`. This is what opens the setup PR and the recommendation PRs when you turn on [automated discovery PRs](/platform/discover/outrider), 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.
***
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](/platform/admin/project-settings)
**Webhook events:**
| Linear Event | Remyx Action |
| ------------------------------- | ------------------------- |
| Issue status changed | Experiment status updated |
| Label added (`ship`, `abandon`) | Decision state updated |
| Comment with `@remyx` | AI agent responds |
| Issue deleted | Ticket link removed |
***
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 via v3 webhook API
**Setup:**
1. Click **Connect** on the Jira card
2. Authorize Remyx when prompted
3. Link a Jira project in [Project Settings](/platform/admin/project-settings)
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](/tutorials/get-started/implement-an-experiment) — Remyx generates a PR for a scoped experiment.
* [Automated discovery PRs](/platform/discover/outrider) — 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](https://console.anthropic.com/settings/keys).
**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](https://console.anthropic.com/settings/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.
```json theme={null}
{
"mcpServers": {
"remyx": {
"type": "http",
"url": "https://mcp.remyx.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_REMYX_API_KEY"
}
}
}
}
```
See the [MCP Server reference](/resources/mcp-server) for the full tool list; get your Remyx API key at [Account > API Access](/platform/admin/account#api-access).
***
## 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](/platform/admin/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.
***
## Related
Full MCP tool reference
Link Linear/Jira projects to projects
What the GitHub App provisions and authors as `remyx-ai[bot]`