Project MonetRequest demo
Home/Blog/Coder Agent Relay: Cursor Self-Hosted Execution Explained

Automation · Project Monet Briefing

Coder Agent Relay: Self-Hosted Execution for Cursor Cloud Agents

Coder Agent Relay keeps Cursor's agent loop and inference in the cloud while moving tool execution into customer-controlled Coder workspaces.

Published 2026-09-05 · Updated 2026-09-05 · By Project Monet Editorial Team

Diagram showing Cursor cloud reasoning connected through Coder Agent Relay to a self-hosted Coder workspace for tool execution

01

What Coder Agent Relay is

Coder Agent Relay is a new architecture for teams that want to keep using cloud-hosted coding agents while moving the agent's execution environment onto infrastructure they control. Coder introduced Agent Relay on September 2, 2026, with Cursor Cloud Agents as the first supported provider.

The important boundary is that Agent Relay does not self-host the entire AI stack. Cursor continues to run the agent loop, planning and model inference in its cloud. The worker that executes tool calls runs inside a Coder workspace on customer-controlled infrastructure.

02

How the architecture works

Coder describes Agent Relay as a bridge between an external cloud-hosted agent provider and a self-hosted Coder workspace. When a task starts, the provider keeps orchestration and inference while a worker inside the Coder workspace executes file operations, terminal commands and other tools.

Cursor's own self-hosted Cloud Agent documentation independently confirms the same split: Cursor runs the agent loop, inference and planning, while the connected worker performs file edits, terminal commands, computer-use tools and local MCP operations.

03

What stays inside your infrastructure

The execution environment can live in infrastructure the organization already governs, such as its cloud, VPC or on-premises environment. That lets teams apply their existing workspace templates, identity controls, network policy and access boundaries to agent execution.

Coder highlights controls such as RBAC, audit logging, Agent Firewall and identity mapping. These are architectural capabilities rather than an automatic security guarantee: the result still depends on how Coder, Cursor, credentials, networking and workspace policy are configured.

04

What is not self-hosted

Agent Relay should not be described as a fully self-hosted Cursor stack. The external provider still runs the reasoning loop and inference. Tool results are sent back to the provider so the next inference step can continue.

Teams that require the full agent runtime to remain under their control should evaluate Coder Agents instead. Coder documents Coder Agents as its separate self-hosted architecture, where the agent loop runs in the Coder control plane and model access is configured by the customer.

05

Availability and pricing

At the time of publication, Coder Agent Relay is in private or closed preview with select customers and design partners. Coder has published architecture material and directs interested organizations to request access.

No public standalone Agent Relay price or general-availability date was verified in the primary sources reviewed for this article. Treat commercial entitlement, rollout timing and future provider support as account-specific until Coder publishes broader details.

06

Who Agent Relay is for

Agent Relay is most relevant to organizations that want Cursor's cloud-agent experience but need command execution to happen inside infrastructure they already govern. That can matter for private source control, internal package registries, restricted networks, centralized audit requirements or regulated workloads.

For smaller teams whose main goal is simply to use Cursor Cloud Agents quickly, the added infrastructure may be unnecessary. The value rises when execution location, identity attribution, network policy and auditability are mandatory requirements.

07

Why this architecture matters

Coding agents increasingly do more than read repositories: they install dependencies, run commands, modify files, access internal services and produce artifacts. Separating the reasoning layer from the execution layer gives enterprises another way to adopt cloud agent products without placing every action in vendor-managed compute.

Coder Agent Relay is therefore best understood as a controlled-execution layer for a cloud-hosted agent, not as a local model runner or a fully self-hosted AI system. That distinction is central to evaluating whether it satisfies a team's security and deployment requirements.

Sources

Primary and supporting sources

Facts were rechecked against the linked sources immediately before publication. Pricing, product availability and rollout status can change.

Project Monet

Useful signals. Clear decisions. Better digital work.

Project Monet turns relevant shifts in AI, creator tools and the web into practical context—and builds focused websites for businesses ready to grow.

Request a free homepage concept