mattvollmer · Sep 2, 2026 · Aug 31, 2026 · Aug 31, 2026 · Aug 31, 2026 · Aug 31, 2026
@@ -0,0 +1,38 @@
+---
+title: Agent Relay for Cursor
+---
+
+> [!NOTE]
+> Agent Relay for Cursor is in [early access](../../install/releases/feature-stages.md#early-access-features) and is currently in closed preview with select customers.
+
+[Agent Relay](./index.md) connects [Cursor Cloud Agents](https://cursor.com/cloud) to self-hosted Coder workspaces.
-[Agent Relay](./index.md) connects [Cursor Cloud Agents](https://cursor.com/cloud) to self-hosted Coder workspaces.
+[Agent Relay](./index.md) connects [Cursor Cloud Agents](https://cursor.com/cloud) to self-hosted Coder Workspaces.
-[Agent Relay](./index.md) connects [Cursor Cloud Agents](https://cursor.com/cloud) to self-hosted Coder workspaces.
+[Agent Relay](./index.md) connects [Cursor Cloud Agents](https://cursor.com/cloud) to self-hosted Coder Workspaces.
+Cursor also refers to this self-hosted worker model as [bring-your-own-machine (BYOM)](https://cursor.com/docs/cloud-agent/bring-your-own-machine).
+Developers keep using the Cursor client and cloud agent workflow they already know.
+The agent's tool calls run inside a Coder workspace on infrastructure you control instead of a Cursor-managed environment.
+
+Cursor's agent orchestration and AI inference remain cloud-hosted.
+Coder doesn't proxy or observe model inference.
+Coder provides the workspace where the agent executes, and logs that correlate the Cursor session and user to that workspace.
+
+## How it works
+
+1. A developer selects a Cursor worker pool mapped to a Coder organization and workspace template, then starts a Cursor agent session.
+1. Agent Relay claims the pending Cursor request and asks the Coder control plane to provision a workspace from the mapped template for that user.
+1. A Cursor worker process inside the workspace connects to the corresponding Cursor cloud session and executes the agent's tool calls.
+1. When the session ends, Agent Relay manages workspace teardown.
+
+Each Cursor agent session gets its own ephemeral workspace.
+
+## Requirements
+
+- A licensed Coder deployment
+- A Cursor Enterprise plan
+
+## Get started
+
+Talk to your [Coder account team](https://coder.com/contact) or email [sales@coder.com](mailto:sales@coder.com) to get access to Agent Relay for Cursor.
+
+## Learn more
+
+- [Agent Relay](./index.md)
+- [Architecture](../../admin/infrastructure/architecture.md)
@@ -0,0 +1,56 @@
+---
+title: Agent Relay
+---
+
+Agent Relay connects a cloud-hosted AI coding agent's hosted sessions to self-hosted [Coder workspaces](../../user-guides/workspace-management.md).
+Developers keep the cloud agent's client and workflow.
+Coder provides the workspace where the agent's tool calls run.
+
+## What Agent Relay does
+
+Agent Relay watches for pending agent sessions from a supported provider.
+When a session starts, Agent Relay provisions a Coder workspace from a mapped template and connects the session to a worker process inside that workspace.
+The worker executes the agent's tool calls, such as reading files, running commands, and using development tools, against the resources available in that workspace.
+Agent Relay manages the workspace for the life of the session and tears it down when the session ends.
+
+<img src="../../images/guides/ai-agents/agent-relay-stack.png" alt="Agent Relay architecture diagram" style="border: none;">
+
+## What Agent Relay is and isn't
+
+Agent Relay changes where a cloud agent's tool calls execute.
+It doesn't change where the agent's orchestration or AI inference run.
+Those stay with the cloud provider.
+
+Agent Relay is not:
+
+- A replacement for [Coder Agents](../agents/index.md), Coder's own AI workflow infrastructure that runs its native agent loop inside the Coder control plane and calls out to your configured LLM provider for inference.
+- A proxy or observability layer for a provider's AI inference.
+  Coder has no access to model selection or token usage for sessions that run through Agent Relay.
+- A self-hosted deployment of a cloud provider's control plane.
+  The provider's orchestration stays cloud-hosted.
+
+## Business value
+
+- Developers keep using the cloud agent client and workflow they already know.
+- Platform and security teams control the infrastructure where agent sessions execute and which internal resources those sessions can reach.
+- Agent sessions run in workspaces built from the same templates, networking, and governance controls as the rest of your Coder deployment.
+- Each session gets its own workspace, provisioned on demand and deleted when the session ends.
+
+## Current state
+
+Agent Relay is in [early access](../../install/releases/feature-stages.md#early-access-features) and is in closed preview with select customers.
+
+## Supported providers
+
+[Cursor](./cursor.md) is the first provider Agent Relay supports.
+Coder built Agent Relay to support additional cloud-hosted agent providers as they add support for self-hosted execution.
+
+## Get started
+
+If you want access to Agent Relay or want updates on the support status for your cloud-hosted agent provider of choice, talk to your [Coder account team](https://coder.com/contact) or email [sales@coder.com](mailto:sales@coder.com).
+
+## Learn more
+
+- [Agent Relay for Cursor](./cursor.md)
+- [Coder Agents](../agents/index.md)
+- [Architecture](../../admin/infrastructure/architecture.md)
@@ -1135,6 +1135,20 @@
 						}
 					]
 				},
+				{
+					"title": "Agent Relay",
+					"description": "Connect supported cloud-hosted AI agents to self-hosted Coder workspaces with Agent Relay.",
+					"path": "./ai-coder/agent-relay/index.md",
+					"state": ["early access"],
+					"children": [
+						{
+							"title": "Agent Relay for Cursor",
+							"description": "Run Cursor's cloud agent sessions inside self-hosted Coder workspaces with Agent Relay.",
+							"path": "./ai-coder/agent-relay/cursor.md",
+							"state": ["early access"]
+						}
+					]
+				},
 				{
 					"title": "AI Governance",
 					"description": "Govern AI usage at scale with AI Governance: Agent Firewall, AI Gateway, and reporting.",

@@ -9,6 +9,7 @@
 > Several Coder terms share the word "agent" but mean different things:
 >
 > - [Coder Agents](#coder-agents) is the AI product for delegating development work to coding agents.
+> - [Agent Relay](#agent-relay) connects a cloud-hosted AI agent provider's hosted sessions to self-hosted workspaces. It is not Coder Agents.
 > - A [workspace agent](#workspace-agent) is the process that runs inside a workspace to provide SSH, port forwarding, the web terminal, and other services.
 > - [`coder_agent`](#coder_agent) is the Terraform resource in a template that declares a workspace agent.
 
@@ -26,6 +27,13 @@
 This feature requires a Premium license.
 Refer to [Agent Firewall](../ai-coder/agent-firewall/index.md).
 
+### Agent Relay
+
+A feature that connects a supported cloud-hosted AI agent provider's hosted sessions to self-hosted [workspaces](#workspace).
+The provider's orchestration and AI inference stay cloud-hosted; a worker process inside the workspace executes the agent's tool calls.
+In [early access](../install/releases/feature-stages.md#early-access-features).
+Refer to [Agent Relay](../ai-coder/agent-relay/index.md).
+
 ### AI Gateway
 
 An LLM gateway in `coderd` that authenticates users, forwards traffic to providers such as OpenAI and Anthropic, audits prompts and tool invocations, and centralizes MCP administration.
@@ -148,7 +156,7 @@
 The Go SDK that the CLI and dashboard use and that you can use for automation.
 Refer to the [`codersdk` package](https://pkg.go.dev/github.com/coder/coder/v2/codersdk).

 ### Coding agent

 An AI agent that reads and writes code on a developer's behalf, such as Claude Code or Coder Agents.
 Refer to [AI in Coder](../ai-coder/index.md).

@@ -1,15 +1,14 @@
 # Workspaces
 
-A workspace is the environment that a developer works in. Developers in a team
-each work from their own workspace and can use
-[multiple IDEs](./workspace-access/index.md).
+A workspace is the environment where a developer or a coding agent works.
+Developers and agents in a team each work from their own workspace and can use [multiple IDEs](./workspace-access/index.md).
 
 A developer creates a workspace from a
 [shared template](../admin/templates/index.md). This lets an entire team work in
 environments that are identically configured and provisioned with the same
 resources.

 ## Creating workspaces

 You can create a workspace in the UI. Log in to your Coder instance, go to the
 **Templates** tab, find the template you need, and select **Create Workspace**.
@@ -78,7 +77,7 @@
  `include_agent_metadata:cpu_usage`. Repeat the key to request multiple
  metadata items. Keys match case-insensitively.

 ## Updating workspaces

 After updating the default version of the template that a workspace was created
 from, you can update the workspace.
@@ -88,7 +87,7 @@
 If the workspace is running, Coder stops it, updates it, then starts the
 workspace again.

 ### Updating via the CLI

 Update a workspace through the command line:

@@ -123,7 +122,7 @@

 ![Bulk workspace actions](../images/user-guides/workspace-bulk-actions.png)

 ## Starting and stopping workspaces

 By default, you manually start and stop workspaces as you need. You can also
 schedule a workspace to start and stop automatically.
@@ -150,7 +149,7 @@
 though the exact behavior depends on the template. For more information, see
 [Resource Persistence](../admin/templates/extending-templates/resource-persistence.md).

 ## Repairing workspaces

 Use the following command to re-enter template input variables in an existing
 workspace. This command is useful when a workspace fails to build because its