Research investigation R1111 / comparison
Antigravity Swarm shares a workspace by default; Cursor documents worktree isolation separately
Shared context, task ownership and separate checkouts address different coordination problems. The sampled documentation does not establish automatic checkout isolation for every worker or conflict-free integration in either product.
The sample comprises five primary records across two products, not a complete inventory of either system. It separates documented coordination from checkout isolation rather than ranking performance. Source rights are citation-only.
The sample comprises five primary records across two products, not a complete inventory of either system. It separates documented coordination from checkout isolation rather than ranking performance. Source rights are citation-only.
- Dataset ID
- spd:cursor-projects-vs-antigravity-swarm-what-is-shared-and-what-stays-isolated-52f2a74b
- Stable URL
- /research/cursor-projects-vs-antigravity-swarm-what-is-shared-and-what-stays-isolated-52f2a74b
- Version
- Live
- Coverage
- Live collection
- Records
- 0
- Fields
- 7
- Updated
| Entity | Metric | Value | Unit | Observed | Source | Transform |
|---|
Measurement technique
How to read this report
- 01Synthesize five supplied primary records: Cursor’s multiplayer announcement, original Projects introduction, Projects documentation, worktree documentation and Antigravity’s Swarm documentation. No runtime execution was performed; reusing saved evidence is not a new collection or experiment.
- 02Retain the requested evidence cutoff of 2026-11-11T16:30:52.230Z. The packet records snapshot retrieval at 16:31:59.841Z, after that cutoff, so exact cutoff-state equivalence cannot be certified.
- 03Plan an evidence_matrix with six scenario rows, separate product columns, source attribution and distinctions between explicit documentation, conditional configuration and unspecified behavior. Do not score undocumented behavior as an absent capability.
- 04Operator scope: Cursor documents multiple teammates with individual coordinators and membership requirements. Swarm describes coordination around the invoking conversation; equivalent cross-teammate membership controls are unspecified on the sampled page.
- 05Context: Cursor distinguishes shared Project knowledge from personal preferences and skills, with approval required to copy personal preferences into Project rules. Swarm workers begin with clean conversation contexts and public task briefs.
- 06Ownership: Cursor’s task board exposes ownership, agent activity and associated PRs. Swarm briefs define ownership, prohibited edits and completion criteria. Neither description establishes filesystem-enforced exclusive ownership.
- 07Communication: Cursor routes cross-teammate messages through restricted side chats labeled as untrusted agent input. Swarm uses a shared board for worker-to-worker communication, with direct user messages to workers as an off-board exception.
- 08Checkout isolation: Cursor’s separate worktree feature documents separate checkouts and configurable setup, without establishing universal use by Projects workers. Swarm defaults to a shared workspace and permits separate working copies when assigned by the coordinator. Sources: https://cursor.com/docs/configuration/worktrees and https://antigravity.google/docs/swarm/ . Step-by-step configuration is outside this synthesis’s scope and neither product was executed to validate these paths or their
Sources
Evidence
2 publishers supporting 0 records. Expand a publisher to inspect its cited pages.