Linear
Use Cloud Agents directly from Linear by delegating issues to Cursor or mentioning @Cursor in comments.
Get started
Installation
You must be a Cursor admin to connect the Linear integration. Other team settings are available to non-admin members.
- Go to Cursor integrations
- Click Connect next to Linear
- Connect your Linear workspace and select team
- Click Authorize
- Complete any remaining Cloud Agent setup in Cursor:
- Connect a repository provider and select a default repository
- Enable usage-based pricing
- Confirm privacy settings
Account linking
First use prompts account linking between Cursor and Linear. A repository provider connection is required for PR creation.
How to use
Delegate issues to Cursor or mention @Cursor in comments. Cursor analyzes issues and filters out non-development work automatically.
Delegating issues
- Open Linear issue
- Click assignee field
- Select "Cursor"
Mentioning Cursor
Mention @Cursor in a comment to assign a new agent or provide additional instructions, for example: @Cursor fix the authentication bug described above.
Workflow
Cloud Agents show real-time status in Linear and create PRs automatically when complete. Track progress in Cursor dashboard.
Follow-up instructions
You can respond in the agent session and it'll get sent as a follow-up to the agent. Simply mention @Cursor in a Linear comment to provide additional guidance to a running Cloud Agent.
Configuration
Configure Cloud Agent settings from Dashboard → Cloud Agents.
| Setting | Location | Description |
|---|---|---|
| Default Repository | Cursor Dashboard | Primary repository when no project repository configured |
| Default Model | Cursor Dashboard | AI model for Cloud Agents |
| Base Branch | Cursor Dashboard | Branch to create PRs from (typically main or develop) |
Configuration options
You can configure Cloud Agent behavior using several methods:
Issue description or comments: Use [key=value] syntax, for example:
@cursor please fix [repo=anysphere/everysphere]@cursor implement feature [model=claude-3.5-sonnet] [branch=feature-branch]
Issue labels: Use parent-child label structure where the parent label is the configuration key and the child label is the value.
Project labels: Same parent-child structure as issue labels, applied at the project level.
Supported configuration keys:
repo: Specify target repository (e.g.,owner/repository)branch: Specify base branch for PR creationmodel: Specify AI model to use