Cursor's long-running background agents reach scale with multi-repo workspaces
Cursor's long-running background agents — first shipped in early 2026 — have reached the scale where multi-repo agentic workspaces are routine. Users report running 8-16 concurrent agents across separate codebases for several hours unattended.
The multi-repo workspace pattern is the killer feature: an agent can edit across a frontend repo, a backend repo, and a shared types package in a single coherent session. Refactors that span repos are now a one-prompt operation.
The trade-off is cost — sustained background agents consume more inference than interactive prompts. Cursor's revenue growth in Q2 2026 is driven primarily by users moving from light-touch suggestions to heavy-touch background runs.