Cursor

Connect Cursor and your assistant can work with Cursor cloud agents — kicking off coding agents on your repositories, checking their progress, and seeing what repositories and models are available.

What’s included

With Cursor connected, your assistant can:

See your agents — list and view your cloud agents and their status
Run coding work — create and manage cloud agents on your repositories
Browse your setup — list accessible repositories and available models

Connecting Cursor

Cursor connects with a Cursor API key. Most people use a user API key; Enterprise teams can also use a service-account key (Dashboard → Settings → API Keys → Service Accounts in Cursor).

In Cursor, open Dashboard → API Keys and create a user API key
In Town, go to Integrations
Find Cursor and click Add account, keep or edit the label, then click Continue
Paste your Cursor API key
Return to Town

Your assistant can only act on the repositories your Cursor account (and API key) can access. You can revoke the key anytime from Cursor settings.

What your assistant can do

Capability	What it does	Makes changes?
List and view cloud agents	Check the status and output of agents	No
List repositories	See which repositories are accessible	No
List models	See available models	No
Create and manage cloud agents	Kick off and manage coding agents	Yes

Use cases

Delegate a fix — “spin up a Cursor agent to fix the failing test in my repo.”
Progress checks — “how’s that cloud agent doing?”
Bug-to-agent routines — turn a triaged bug report into a cloud agent run.

Good to know

Cloud agents make real changes in your repositories — set the tool to Ask each time in routines that create agents.

Integrations overview — How integrations give your assistant context
GitHub — Pair with GitHub for repository context