For Anysphere's Cursor

Stuck in Cursor? Press the dot.

Cursor's AI-native editor moves fast — and so do the moments it asks for help.

See pricing

When Cursor needs a person.

01

When the agent loop won't terminate

Cursor's agent mode is excellent until it isn't. When it's burning context on the wrong file or chasing a non-existent type, a Relay engineer joins your screen, prunes the loop, and resets it on the right anchor.

02

When the refactor crosses a boundary the AI can't see

Renames across packages, migrations across React versions, framework swaps — Cursor handles a lot of it, but the spots where it breaks are the spots a person needs to be in the room.

03

When you're ready to ship

From local-running to production-deployed is its own job. Tests, infra, secrets, observability, the deploy itself. A Relay engineer takes the build the rest of the way.

Common questions

Do I have to leave Cursor to use Relay?
No. Press the dot from anywhere — including a Cursor session — and the engineer joins the screen share or chat without leaving your editor.
Will the engineer have my Cursor context?
Whatever you've put into the screen share, yes. We don't ingest your Cursor history, embeddings, or workspace state — you bring what you want them to see.
Does Relay support Cursor's agent mode?
Yes. The most common flavor of press from a Cursor builder is exactly that: an agent loop that needs a senior eye for ten minutes.

Press the dot.

A senior Relay engineer joins your Cursor session in seconds.

See how it works