Connect Cursor to Town
Coding tasks handed to a cloud agent from a sentence, progress checked from chat, and hand-off notes drafted when the fix lands. Connected with your Cursor API key.
Bram checked on the day's Cursor agents and had the reviewer hand-offs drafted before the checks finished.
See it work: a routine built on your coding agents
Get every finished fix in front of a reviewer
Kick off the fix. The hand-off drafts itself.
Open Integrations in Town
Go to Integrations in your Town workspace (free to create) and find Cursor.
Paste your Cursor API key
Create an API key in your Cursor dashboard and paste it into Town's token field. Nothing to install — the agents run in Cursor's cloud.
Put your agents to work
Done — hand off a fix from chat, check on any run, and get the reviewer hand-off drafted when the work lands.
Just ask your Townie
Cursor writes the code. Town runs the loop around it: kickoffs from your inbox, check-ins from chat, hand-offs drafted when the work lands.
“Fix the bug this customer hit.”
You approve the kickoff; a Cursor agent writes the fix and opens the PR.
“How's the checkout refactor going?”
Answered from the agent's live status and conversation, in plain English.
“Tell the agent to use the new endpoint.”
A follow-up sent mid-run with your approval, no editor open.
Cursor integration FAQ
Town's Cursor integration connects Cursor's cloud agents — the coding agents Cursor runs in its own environment — through an API key you create in your Cursor dashboard. Your Townie can kick off an agent on a repository, check its status, results, and conversation, send follow-ups, stop a run, and list your available repositories and models. Kickoffs and follow-ups are held for your approval.
Your code stays in Cursor and your repositories — Town talks to Cursor's API, scoped to what your API key can reach, and never clones or stores your codebase. Anything that starts or steers an agent waits for your approval first. Read more about how Town approaches security.
By default, no. Starting an agent and sending it follow-ups are held for your approval, the agent's changes arrive as a pull request so your team's normal review still applies, and you can stop any run from Town.
What your API key can reach: the repositories connected to your Cursor account, your cloud agents with their status, results, and conversation history, and the models available for runs. Under the hood these are Town's Cursor tools: create a cloud agent, send a follow-up, stop a run, get an agent's status and conversation, and list agents, repositories, and models.
Cloud agents are part of Cursor's paid offering, and their usage is billed by Cursor to your account — check your Cursor plan. On the Town side, the connection works on every plan, and Town is free to start.
Cursor's editor and agents write the code. Town runs the loop around them: a bug report becomes an agent kickoff, progress gets checked from chat, and the reviewer hand-off is drafted when the work lands, all without opening an editor.
What is Cursor?
Cursor is the AI code editor, and its cloud agents take coding tasks end to end — reading the repository, writing the change, and opening the pull request from Cursor's own managed environment.
Cursor writes the code; Town runs everything around it. Connected, a sentence becomes a kickoff, any run answers from chat, and the reviewer hand-off drafts itself when the fix lands.
