Cursor
Use Cursor as an agent provider with Verun — prerequisites, selecting the agent, and Verun-specific configuration.
Cursor is a GUI-based AI code editor that Verun can integrate with as an agent provider. Unlike CLI-based agents, Cursor operates through its own interface while Verun manages the worktree and task context.
Overview
Cursor provides AI-powered code editing through a desktop application. When used with Verun, it works within the isolated worktree for each task, benefiting from the same parallel execution and git isolation.
Prerequisites
- Cursor installed and running
- An active Cursor account or API key
- The Cursor command-line tool available in your PATH
Verify Cursor is available:
cursor --versionSelecting Cursor in Verun
- Open a task from the task list.
- Click Start Session.
- In the session settings, select Cursor from the provider dropdown.
- Choose a trust level.
- Click Start.
Alternatively, set Cursor as the default in .verun.json:
{
"agent": "cursor"
}Configuration
Cursor uses its own project configuration (.cursorrules, .cursor/) for project-specific instructions. Place these in your project root — they are available inside each worktree.
Verun-specific settings via .verun.json:
{
"agent": "cursor",
"setup": ["npm install"],
"ports": [3000]
}Known Limitations
- Cursor is a GUI application, so the integration differs from CLI-based agents. Some features like terminal command execution may behave differently.
- Cursor must be running and authenticated before starting a Verun session.
- Large repository indexing may take longer compared to CLI-only agents.