Antigravity Boost or Teamwork? Enterprise controls, versions and costs

Choose task scale first

Google's October 6, 2026 release notes announce Boost GA, Teamwork preview and enterprise controls. Teams already using Antigravity can choose separately for ordinary work, deep diagnosis and long projects.

/boost divides a complex engineering problem among agents with independent verification, suitable for concurrency bugs, algorithm optimization or difficult regressions. It focuses on resolving one interactive task deeply.

/teamwork-preview handles longer collaboration such as cross-module migration, multifile refactoring or complex research. It clarifies goals and allocates milestones. It remains preview, not Boost's GA status.

Enabled does not establish account eligibility

Docs describe paid-plan capabilities in Antigravity 2.0 and CLI. Enterprise controls need desktop 2.18.0+ or CLI 1.2.10+. Old clients, personal subscriptions and enterprise projects are different eligibility contexts.

Gemini Enterprise projects need an invoiced Cloud Billing account receiving valid monthly invoices. Supported editions include Standard, Plus, Standard Emerging Market and PAYG. Emerging Market is restricted to eligible customers, with regional conditions retained.

Users need appropriate licenses and Gemini Enterprise User permission. Editing settings does not automatically grant tool use, nor API enablement authorize every member. Have the organization administrator check conditions when an entry is absent.

Administrators control the two features separately

Configuration requires Gemini Enterprise Admin, roles/discoveryengine.agentspaceAdmin. Confirm target project and subscription location, not a test project's settings as team production state.

Open Gemini Enterprise in Cloud console, Settings, then AI developer tools. For an existing subscription without developer tools enabled, inspect that location's overall switch first.

Under Features select Edit, adjust Boost and Teamwork separately, then Save. Both default Enabled; restrict each according to team task scope.

Docs give no propagation delay or behavior for running tasks after disabling. Inspect saved settings and confirm access in an authorized new session. Do not promise immediate termination or suggest restarting at random.

More agents can cost more

Enterprise docs warn advanced multi-agent features may increase token use and charges. Enabled permits use; it supplies no extra free quota or zero-cost promise.

Use organization subscription, billing and spending settings. Preserve existing cost observation and let a small team evaluate a bounded task, comparing completion and usage rather than inferring bills from agent count.

Ordinary copy edits rarely need long-project collaboration. Reserve heavier modes for complex dependencies and independent verification value to judge whether added cost buys useful results. No performance or cost test occurred here.

Hypothetical cache bug versus system migration

This example was not executed: for an intermittent cache race with reproduction and expected behavior, describe the single issue to /boost with allowed changes, verification and stop conditions.

Migrating several modules between frameworks while preserving interfaces/tests better fits Teamwork milestones. Define delivery scope before collaboration rather than expanding a local issue into an endless project rewrite.

Neither mode replaces permissions. Subagents inherit relevant directory, terminal and sandbox scope; approval-required actions retain their treatment. Do not grant unrelated files, services or accounts simply to smooth coordination.

Investigate missing commands in order

Check client version and entry point, then plan/project, overall switch, Features and personal license/IAM. Record the missing condition to avoid repeated updates or account switching.

If ordinary sessions work but team commands are absent, give these conditions to the administrator. If a started task produces poor results, inspect delivery scope and validation separately from feature entitlement.

Networking, eligibility and billing differ. Exit changes grant no license, organization switch or quota. See the related enterprise billing/developer-tools answer in Sources.