Host Cursor as a background agent that never clocks out
Cursor is a coding agent that works on your GitHub repo: it writes code, opens pull requests and replies to review comments while you get on with something else. Its cloud sessions run on a worker, and that worker has to be awake for the agent to pick up a task the moment you hand one over.
Sokko keeps that worker running for you. Deploy Cursor from the dashboard and its worker comes up on its own private machine, usually in about 44 seconds, ready and waiting. It restarts itself if it crashes, and you pick a US or EU region so the work happens close to you. This is Cursor headless and always on, so a task you start at midnight is done before morning.
What Cursor does
Works straight on your repo
Point it at a GitHub repo and it writes code, opens pull requests and answers review comments. You review and merge; it keeps chipping away at the next task.
Runs headless, no page to babysit
On Sokko there is no web page or terminal to open. You start and steer sessions from Cursor itself, and the worker keeps running quietly behind the scenes.
Uses your own Cursor plan
It runs on your Cursor API key and your Cursor subscription, so there is no separate model step to set up. Your usage stays on the account you already pay for.
Runs sessions side by side
One Cursor agent can run several workers at once, so a few tasks on the same repo move in parallel instead of waiting in line.
How it worksDeploy Cursor in four steps
Pick a plan
Plans start at Cookie, $12 a month, for the always-on machine the worker lives on.
Connect a GitHub repo
Tell the agent which repo to work in. That is the codebase it reads, writes to and opens pull requests against.
Add your Cursor API key
Grab a key from Cursor under Dashboard, then Settings, then API Keys, and paste it in the Secrets tab. It reaches the worker securely and runs against your own Cursor plan.
Choose how many workers
Decide how many workers this agent should run. One is plenty to start; add more when you want several sessions on the repo going at the same time.
What people run on it
Clear the small-fix backlog
Hand it the tidy-up jobs nobody gets to: renames, small bugs, dependency bumps. It opens a pull request for each, and you just review and merge.
Ship while you sleep
Kick off a task at the end of the day and read the pull request in the morning. The worker never stops, so long jobs finish overnight.
Several tasks on one repo at once
Run a handful of workers on the same codebase so separate pieces of work move together, then merge them as each one lands.
Questions people ask
How much does it cost to host Cursor on Sokko?
Plans start at $12 a month (Cookie) for one always-on worker. Cursor usage itself runs on your own Cursor API key and subscription, so that stays on the account you already pay for.
Is there a web page or terminal to open?
No. On Sokko, Cursor runs headless: there is no page or terminal. You start and steer sessions from Cursor itself, on the app or at cursor.com, and Sokko keeps the worker running behind the scenes.
Do I need a separate model provider key?
No. Cursor runs on your Cursor API key and your Cursor subscription, so there is no extra model step. Add the Cursor key once and you are set.
Can it run more than one session at a time?
Yes. One Cursor agent can run several workers side by side, so a few tasks on the same repo move in parallel instead of one after another.
Do I have to manage a server?
No. There is no machine to patch and no restart script to write. If the worker crashes it comes back on its own, and you choose a US or EU region when you deploy.