Skip to main content

​
Overview

Cursor appears in Config -> Connections under the Dev Tools category. Genesis uses a shared-scope API Key connection to authenticate with Cursor Cloud when the enhancement coding-agent launcher runs in cloud mode. After setup, Genesis tests the connection by calling GET /v1/models on the configured API base URL (default https://api.cursor.com).
The Cursor connection powers the cloud adapter for Support and Enhancements. Pair it with genesis_enhancements.cursor_agent.* settings in Advanced Settings or genesis-config.yaml.

​
Setup workflow

1

Open the Cursor connector

Go to Config -> Connections, choose Dev Tools, then select Cursor.
2

Create a shared connection

Save the connection with Shared scope. The cloud adapter rejects personal-scope Cursor connections.
3

Enter API credentials

Paste a Cursor enterprise service-account API key. Override API Base URL only when testing against a non-production endpoint.
4

Test and save

Run the built-in connection test, verify the success message, then save the connection. Record the connection name — you reference it from genesis_enhancements.cursor_agent.connection_name.
5

Enable the cloud launcher

In Advanced Settings or genesis-config.yaml, set genesis_enhancements.cursor_agent.enabled to true, genesis_enhancements.cursor_agent.adapter to cloud (or auto when no local runner command is configured), genesis_enhancements.cursor_agent.connection_name to the saved connection name, and genesis_enhancements.cursor_agent.target_repo_url to the GitHub repository Cursor agents should modify.
If your deployment uses outbound allowlists or external access controls, allow Genesis to reach api.cursor.com (or your configured API base URL).

​
Connection fields

​
api_key

​
Launcher settings that use this connection

Configure these genesis_enhancements.cursor_agent fields alongside the connection:

​
What it enables

When the cloud adapter is configured, Genesis can:
  • launch Cursor Cloud agents from the Software Factory page and from enhancement reports on Support and Enhancements,
  • poll agent status, branch name, pull request URL, and agent URL through the Cursor Cloud API,
  • start agent runs from genesis_enhancement_action with START_CURSOR_AGENT and inspect them with GET_CURSOR_AGENT_STATUS.
Local runner mode (adapter: local or auto with CURSOR_AGENT_RUNNER_COMMAND set) does not use this connection.

​
Claude Code backend

Genesis can run the same coding-agent workflow through Claude Code instead of Cursor Cloud. Select the provider-neutral backend with genesis_enhancements.coding_agent.backend: claude_code and enable it with genesis_enhancements.coding_agent.claude_code.enabled: true. The Claude Code backend clones genesis_enhancements.coding_agent.claude_code.target_repo_url, cuts each run’s worktree from target_base_ref (default main), and uses the configured connection_name for the model credential. Configure git_connection_name separately for the GitHub App identity that pushes the branch and opens the pull request. Claude Code runs locally in a child process with a per-run worktree. Their run evidence is persisted under the run root, while the default worktree directory (worktree_root: /opt/genesis-agents-start-cursor-agent) is ephemeral on EKS. See Advanced Settings for all Claude Code limits and timeouts, and Connections for the supported credential profiles.