Apps and additional agents
Find launch targets supported by your CLI version and verify an editor is routed through Edgee.
Run edgee launch --help to see the targets included in your installed release. Install the target application first, then launch it through Edgee.
| Target | Tool |
|---|---|
cursor | Cursor |
copilot-vscode | GitHub Copilot in VS Code |
claude-desktop | Claude Desktop Beta |
codex-desktop | Codex Desktop Beta |
copilot-desktop | GitHub Copilot Desktop Beta |
intellij | GitHub Copilot in IntelliJ IDEA Beta |
copilot-cli | GitHub Copilot CLI |
omp | Oh My Pi |
Launch and verify
edgee launch cursor
Follow any first-launch prompts, including required local networking permissions. Send a request in the opened editor, then check Sessions or Logs in the selected Edgee organization. Merely opening the application does not prove requests are passing through Edgee.
See the dedicated Cursor and VS Code Copilot guides for their setup paths. Use aliases and wrappers to create an app-menu entry when supported.
If the editor does not connect
Check the target application is installed, read the launch error, and confirm the provider account is usable in that application. If an already-running editor retained its previous connection, close it and launch through Edgee again. Review Troubleshooting before changing keys or deleting application configuration.