When reaching out to support, specify that you are using Cursor as your editor.
Prerequisites
- Cursor installed on your machine.
- The Ona extension installed in Cursor.
- The Remote - SSH extension installed in Cursor.
Opening an environment
Select Cursor from the editor dropdown by clicking the dropdown arrow next to the Open button on the action bar. Cursor opens via thecursor:// 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
- Agent: multi-file AI edits
- Chat (⌘L / Ctrl+L): context-aware code chat
- ⌘K / Ctrl+K: inline code generation and editing
Extension and settings
Extensions configured viacustomizations.vscode.extensions in your devcontainer.json apply to Cursor. See VS Code and forks for details.
Troubleshooting
Cursor does not open
Thecursor:// URI handler is not registered on your system, or Cursor is not installed.
- Linux: Verify a Cursor desktop entry exists in
~/.local/share/applicationsor/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
- Check the
Onaoutput view for errors. - Check your network settings. VPN or firewall can interfere.
- When sharing reports with support:
- Set log level to Trace via
Developer: Set Log Level... - Use
Ona: Export all logsfrom the problematic window.
- Set log level to Trace via