Remote Control for self-hosted git server

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor for iOS

Describe the Bug

We have a private self-host using https://about.gitea.com/ through a VPN. I’m not able to put any agent using remote control or cloud options. Using cursor CLI worker functionality, the agent appears to the iOS; however, it’s not possible send prompts to it

Steps to Reproduce

run agent worker start --debug on terminal

Select the agent that appears on IOS and try to send some prompt.

It appears as draft but not able to run it.

Expected Behavior

It should be possible to run prompts remotely on worker

Screenshots / Screen Recordings

Captura de tela 2026-07-03 155844.png
Captura de tela 2026-07-03 155844.png407×895 45.8 KB

Operating System

Windows 10/11

Version Information

IDE:
Version: 3.9.16 (system setup)
VS Code Extension API: 1.105.1
Commit: 042b3c1a4c53f2c3808067f519fbfc67b72cad80
Date: 2026-06-27T06:41:01.941Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

CLI:
CLI Version 2026.07.01-41b2de7
Model Auto
Subscription Tier Pro
OS linux (x64)
Terminal windows-terminal
Shell zsh
User Email [email protected]

IOS: 1.1.0

Additional Information

Can’t share the hosted URL since is private and protected by VPN

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey, thanks for moving this into a separate thread.

This is clear even without extra tests. If the agent shows up in the app, it means the worker-to-cloud connection is fine. The failure is specifically on sending.

The mobile create and send flow relies on a connected, supported source control provider GitHub or GitLab. Self-hosted Gitea isn’t treated as supported there. Because of that, Send doesn’t dispatch the request, it keeps it as a Draft, and you can’t run it.

The fix we merged recently only targets gitlab.com and it doesn’t cover self-hosted servers like Gitea or self-hosted GitLab. We don’t have self-hosted support for this flow right now, so I can’t share an ETA.

We’re tracking this issue on our side. If there’s an update for self-hosted support, I’ll post it in this thread.