LOCUSTLocust with
Cursor, as one of your team
Locust runs Cursor as a teammate on your own computer, with Cursor Agent's own sign-in, on your Cursor account, beside teammates on other agents. Free and MIT, with no Locust account.
How Locust runs it
cursor-agent --output-format stream-json
Locust runs Cursor's command-line agent and reads its streamed events, so each step shows as it happens, beside your other teammates. It never reads the agent's screen. If it is not installed yet, Locust's first launch shows how to get it.
Before it acts
Asks you first
Nothing: Cursor's command line has no way to stop and ask Locust. Pick the mode before the turn instead.
Without asking
In Ask and Plan, Cursor's own read-only mode, with no MCP server started that a folder brings. In Edit, changes in the folder, and commands as Cursor's own settings allow. In Auto, everything.
Five modes, from Ask, which changes nothing, to Auto. Every agent, side by side: What Locust can stop.
What Locust adds to Cursor
- Keys you keep for a teammate reach its Cursor turns, encrypted on this computer until then.
- Hand a Cursor teammate's work to a teammate on Claude Code or Codex to check, before the run counts.
- Every teammate on its own agent and model, side by side, with one Board for what needs you, what is working and what is done.
- Blind compare: the same task on several agents, names hidden until you keep one.
- Hand-offs by name between teammates on different agents, and a checker you pick, on another AI if you like, who must approve before a run counts.
- A local record of every run, kept if the window closes, and Undo for a teammate’s turn.
- Your phone from anywhere, sealed end to end, and Discord, Slack or Telegram if you turn them on.
Locust with the others
Try Locust
Free and open source (MIT). Windows, Mac and Linux. No Locust account: it runs the agents you already have, signed in as you.