The phone is a control surface, while the real project remains on the Mac
Spacesuit's official listing describes a mobile companion for Google Antigravity sessions running on a Mac. It can bring project conversations, prompts and task activity to an iPhone or iPad through a companion app and private iCloud relay. The meaningful story is a control boundary: the mobile view reaches work elsewhere rather than relocating the development environment to the phone.
This source-based spotlight is not a release announcement or a practical security test. It examines the documented controls and prerequisites, including the requirement that the Mac remain awake with Spacesuit and Antigravity running. A remote interface can reduce distance from a task without reducing the consequences of what that task does.
What it does
The listing names existing-project browsing, continuing conversations and creating a conversation in a selected workspace. A prompt can be sent, a follow-up queued while the agent is busy, and supported tasks stopped or continued. Model selection reflects what is available on the Mac, not a separate mobile entitlement to every model.
Supported reasoning, code and tool activity can be inspected. Live Activities expose running-task information on the Lock Screen and Dynamic Island. Those are useful awareness surfaces, while the compact status should not be assumed to contain every changed file, error or approval condition. We have not tested the exact activity shown for a particular Antigravity version.
The companion relays commands and responses using the same private iCloud account on both devices. Antigravity connection credentials remain on the Mac, according to the developer. Internet access and the required applications are explicit dependencies. The app is independent and is not affiliated with or endorsed by Google, which matters when interpreting a familiar product name in a third-party control surface.
Before you install
For a developer, the sensible first example is a disposable project with a bounded, observable change. Confirm the workspace, send the instruction and compare the mobile response with the actual files on the Mac. We have not tested task accuracy, duplicate execution, interruption or recovery. A completed-looking conversation is not an independent validation of the resulting code.
The queue deserves particular attention. A follow-up written before the current task finishes may depend on an assumption that later proves wrong. Queuing is a convenience, not proof that the next instruction has reviewed the final state. Keep a clear point at which the work is inspected before a chain of consequential changes continues.
Stopping also has a specific meaning to verify. A stop request and confirmed interruption are different states, and earlier file changes may remain. The listing does not establish universal rollback. Version history, project checks and appropriate permissions remain relevant even when the action begins on a small screen.
Price and access
The retained US App Store offer lists a free download. Some features require Spacesuit Unlimited, available through an annual subscription or one-time lifetime purchase. Custom themes, title fonts and app icons are named, while the complete free-tier boundary and exact regional prices are not established in the retained description.
Confirm the current purchase and compatibility information before upgrading. Antigravity access and any underlying model or service costs are separate from the companion. An annual plan renews automatically unless cancelled, while the lifetime option has a different access model. Neither purchase should be interpreted as a promise of compatibility with every future underlying application change.
Our take
The strongest proposition is continuity with a known work session. A developer away from the desk may value reading a response or checking a narrowly scoped task without reconstructing the whole project on another device. That is a more precise claim than saying a phone replaces the development workstation.
We have not tested reliability, accessibility, privacy, security or compatibility. Our take is to validate one complete harmless exchange and inspect the actual Mac result before adopting the remote route. The best evidence is a clear connection between the selected workspace, requested action and observed outcome, not simply a smooth-looking conversation.
Private iCloud and Mac-held credentials are specific developer statements. They should not be expanded into an assertion that no project information reaches the phone or that every connected device is automatically authorised appropriately. Review the actual account, device access and visible status arrangement for the work involved.
For independent professionals, convenience is useful when it supports a deliberate boundary around client material and production systems. A quick prompt can still affect real files. Keep the remote task small enough to understand and return to a fuller review when the decision requires it.
The qualified verdict is a well-defined companion concept with important dependencies honestly stated. Spacesuit can be considered as a route to an existing Antigravity environment, while the original workspace, its permissions and the human review process remain central to whether the resulting work is safe and correct.
A good first trial should therefore include a return to the original desktop view. The remote summary and the actual workspace need to tell the same story before convenience becomes a dependable working routine.
