> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ref.tools/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations Overview

> Connect Ref Plans to coding agents and external services.

Ref Plans integrates with coding agents (where you send tasks for implementation) and context sources (where you pull planning context from).

## Cloud agents (API-based)

Cloud agents connect directly through API keys. Ref launches the agent and tracks its progress automatically — no manual intervention required. These agents can also be launched programmatically by an orchestrator agent via the [`LaunchAgent`](/plans/workflows/multi-agent) MCP tool as part of [multi-agent orchestration](/plans/workflows/multi-agent).

| Agent                                                  | Description                                                                                   |
| ------------------------------------------------------ | --------------------------------------------------------------------------------------------- |
| [Cursor Background Agents](/plans/integrations/cursor) | Launches a Cursor background agent via API key. Writes code, creates branches, and opens PRs. |
| [Devin](/plans/integrations/devin)                     | Launches a Devin session via API key. Writes code, creates branches, and opens PRs.           |
| [Warp OZ](/plans/integrations/warp-oz)                 | Launches a Warp OZ agent via API key. Writes code, creates branches, and opens PRs.           |

Cloud agents provide:

* **Automatic launch** — Ref starts the agent session for you
* **Status tracking** — Progress updates flow back to Ref automatically
* **Orchestration support** — Can be launched by an orchestrator agent via `LaunchAgent` with `harness: "cursor"`, `harness: "devin"`, or `harness: "warp-oz"`

Configure API keys in **Settings > Agent Settings** at [plan.ref.tools](https://plan.ref.tools).

## Launcher agents (webhook-based)

Launcher agents work by appending progress-reporting instructions (curl commands) to the task prompt. You initiate the agent session yourself, and the agent reports back to Ref by executing the webhook commands included in the prompt.

| Agent                                                  | Description                                        |
| ------------------------------------------------------ | -------------------------------------------------- |
| [Claude Code Web](/plans/integrations/claude-code-web) | Sends task to Claude Code in the cloud             |
| [Codex](/plans/integrations/codex)                     | Sends task to OpenAI Codex                         |
| Cursor Local                                           | Sends task to your local Cursor instance           |
| Copy & Paste                                           | Copies the task prompt for manual use in any agent |

Launcher agents require you to:

1. Click **Launch Agent** in the plan UI to generate the prompt
2. Start the agent session yourself (or paste the prompt)
3. The agent executes the embedded webhook commands to report progress back to Ref

## Context sources

Pull context from your project management and development tools into your plans:

| Source                                            | Description                                                                   |
| ------------------------------------------------- | ----------------------------------------------------------------------------- |
| [Linear](/plans/integrations/linear)              | Attach Linear tickets for context; agent can update ticket status             |
| [Asana](/plans/integrations/asana)                | Attach Asana tasks for context; agent can update task fields and add comments |
| [GitHub Issues & PRs](/plans/integrations/github) | Attach GitHub issues and PRs; track PRs linked to plans                       |
| [Slack](/plans/integrations/slack)                | Create and update plans from Slack threads via @mention                       |

## Custom MCP servers

Connect your own remote MCP server to make its tools available to ref-thread agents. Custom MCP servers are configured in Settings and can be attached per thread from the message composer — see [Custom MCP Servers](/plans/integrations/custom-mcp).

## Custom Launchers

Use [Custom Launchers](/plans/integrations/custom-launchers) to deep-link into Ref from any tool that can construct a URL. The `/new` URL can seed plan content and optionally start an agent thread immediately.

<CardGroup cols={2}>
  <Card title="Cursor Background Agents" icon="arrow-pointer" href="/plans/integrations/cursor">
    Launch Cursor background agents from your plans.
  </Card>

  <Card title="Devin" icon="hexagon-nodes" href="/plans/integrations/devin">
    Launch Devin sessions from your plans.
  </Card>

  <Card title="Warp OZ" icon="terminal" href="/plans/integrations/warp-oz">
    Launch Warp OZ agents from your plans.
  </Card>

  <Card title="Claude Code Web" icon="cloud" href="/plans/integrations/claude-code-web">
    Send tasks to Claude Code in the cloud.
  </Card>

  <Card title="Codex" icon="openai" href="/plans/integrations/codex">
    Send tasks to OpenAI Codex.
  </Card>

  <Card title="Linear" icon="circle-nodes" href="/plans/integrations/linear">
    Connect Linear tickets to your plans.
  </Card>

  <Card title="Asana" icon="list-check" href="/plans/integrations/asana">
    Connect Asana tasks to your plans.
  </Card>

  <Card title="GitHub" icon="github" href="/plans/integrations/github">
    Connect GitHub issues and PRs to your plans.
  </Card>

  <Card title="Slack" icon="slack" href="/plans/integrations/slack">
    Create and update plans from Slack threads.
  </Card>

  <Card title="Custom MCP Servers" icon="plug" href="/plans/integrations/custom-mcp">
    Connect your own remote MCP server.
  </Card>

  <Card title="Custom Launchers" icon="link" href="/plans/integrations/custom-launchers">
    Deep-link into Ref from any tool.
  </Card>
</CardGroup>