Skip to main content
Cursor connects to Ona environments using the same Ona extension as VS Code. All VS Code features (environment details, rebuild, port forwarding, automations) work in Cursor.
When reaching out to support, specify that you are using Cursor as your editor.

​
Prerequisites

  1. Cursor installed on your machine.
  2. The Ona extension installed in Cursor.
  3. The Remote - SSH extension installed in Cursor.

​
Opening an environment

Select Cursor from the editor selector dropdown by clicking the dropdown arrow next to the editor button on the action bar.
Editor dropdown showing Cursor option in the action bar
Cursor opens via the cursor:// URI handler. On first use, Cursor prompts you to install the Ona extension and authenticate. This is the same flow as VS Code setup.

​
Cursor AI works over SSH

Cursor’s AI features work in Ona environments as they do locally:
  • Tab: inline code completions
  • Composer: multi-file AI edits
  • Chat (⌘L / Ctrl+L): context-aware code chat
  • ⌘K / Ctrl+K: inline code generation and editing
Cursor AI communicates with Cursor’s cloud services directly over the SSH connection. No Ona-specific configuration is needed.

​
Extension and settings

Extensions configured via customizations.vscode.extensions in your devcontainer.json apply to Cursor. See VS Code and forks for details.

​
Troubleshooting

​
”Open Cursor” button does nothing

The cursor:// URI handler is not registered on your system, or Cursor is not installed.
  • Linux: Verify a Cursor desktop entry exists in ~/.local/share/applications or /usr/share/applications. If missing, reinstall Cursor.
  • All platforms: Refresh the browser page, or test in a different browser to rule out browser-specific issues.

​
Connection issues

The VS Code troubleshooting guide applies to Cursor, including log export (Ona: Export all logs) and authentication issues.

​
General issues

If you encounter unexpected problems:
  1. Check the Ona output view for error messages.
  2. Check your network settings. VPN or firewall settings can interfere with the connection.
  3. When sharing reports with support:
    • Use Developer: Set Log Level... command to set the level to Trace.
    • Use the Ona: Export all logs command from the problematic window.