◉ANTIGRAVITY LABJP
Articles/Antigravity Basics
◉ Antigravity Basics/2026-06-18Intermediate

Choosing Among Desktop, CLI, SDK, and Managed Agents for the Same Job

Antigravity 2.0 has several surfaces: desktop, CLI, SDK, and the Managed Agents API. Which one should run a given task? Here is a framework for choosing the surface from the nature of the work.

Antigravity419Antigravity 2.016architecture20workflow design3

✦ Premium Article

When Antigravity 2.0 changed from a single editor into a platform with five surfaces, my first hesitation was not about any new feature but about a question: which surface should this job run on? Work it interactively on the desktop, fire it from the CLI, embed it in an app through the SDK, or throw it at the cloud via the Managed Agents API? Even for the same task — "fix a component" — the right surface shifts with the context.

As an indie developer running four sites in parallel, I first tried to do everything on the desktop and ran out of hands. Only once I started choosing the surface by the nature of the work did things settle. Here I lay out that choice as a decision framework.

First, the plain character of the four surfaces

Setting aside the enterprise Cloud path, the four surfaces an indie developer touches each suit a different shape of work.

SurfacePlain characterBest-fit work
DesktopInteractive; supervise parallel agents by eyeExploratory building; work that needs judgment
CLINon-interactive; embeds in scriptsRoutine processing, CI, nightly batch
SDKEmbeds an agent in your own appResident processing as a product feature
Managed Agents APISpins up an isolated environment in one callHeavy, risky, or to-be-isolated work

The point is that these are about fit, not rank. Desktop is not above and the API below. Apply the nature of the work and the fitting surface falls out on its own.

Measure the work on four axes

When choosing a surface, I measure the work on four axes.

Interactivity

Does a human need to decide mid-flight? If so, desktop. If the steps are fully fixed, you can push it toward the CLI or API. Force-automating work whose direction changes as you go just multiplies redos.

Scheduling

Do you want it to run unattended at a set time? Then put the CLI on cron, or use the SDK's scheduled execution. Desktop assumes a human in front of it, so it does not suit unattended operation.

Isolation

Do you want to contain the blast radius of a failure? Work that handles untrusted input or tries destructive operations goes to the isolated environment of the Managed Agents API. There is no need to run it in your local workspace.

Integration depth

Do you want the processing resident as part of your own product? If you are building a feature where an agent acts on user input, it is the SDK, full stop. The CLI and desktop cannot be built into a product.

✦

Thank you for reading this far.

Continue Reading

What follows includes implementation code, benchmarks, and practical content we hope you'll find useful. This site runs without ads — server and development costs are supported entirely by members like you. If it's been helpful, we'd be truly grateful for your support.

WHAT YOU'LL LEARN
✦A four-axis frame for choosing a surface: interactivity, scheduling, isolation, integration depth
✦A small router that returns a surface from task attributes, plus minimal CLI and SDK launch examples
✦The cross-surface trap I hit running all four in indie development, and how I now choose
Secure payment via Stripe · Cancel anytime
✦

Unlock This Article

Get full access to the rest of this article. Buy once, read anytime. This site is ad-free — your support goes directly toward keeping it running.

or
Unlock all articles with Membership →
Share

Thank You for Reading

Antigravity Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • ✦Copy-paste ready implementation code
  • ✦New advanced guides published daily
  • ✦$5/mo or $10 for lifetime access
View Membership →

Related Articles

◉ Antigravity2026-11-12
When "Always Proceed" Still Asks for Approval, Decide How Loose to Go by Command Type, Not Setting Name
You picked Always Proceed and the agent still asks before running terminal commands. Before hunting for the cause, sort commands into read-only, local-write, and delete-or-send, and decide your own line. A small classifier script included.
◉ Antigravity2026-10-31
Ask It to Only Read on Day One: A Five-Step Ladder for What to Hand Antigravity
What to ask Antigravity on your first day, and what to hold back. A five-step ladder that widens the agent's scope from least to most breakable, plus a small shell script that counts what actually changed before and after a session.
◉ Antigravity2026-10-28
When Antigravity Says Failed to Fetch: Decide the First Three Places to Look
A short triage order for Failed to Fetch in Antigravity: check whether the destination is reachable, whether you are still signed in, and whether a proxy or VPN sits in the middle. Includes copy-paste terminal checks and what each result means.