Techvoyage
Home
Google Antigravity 2: Browser & Schedule Automation

Guide to Browser and Scheduler in Antigravity 2

Discover how the /browser and /schedule commands elevate Google Antigravity 2 into a powerful AI automation platform.

Jun 7, 2026 - 5 MIN READ

The /browser and /schedule commands in Google Antigravity 2 redefine how we interact with AI. These two commands transform Antigravity into a proactive automation platform that can interact with the live web and run recurring workflows.

Browser Run

The /browser command forces the use of the Chrome browser to complete a task. Users remain in control over when and how agents access the web during the workflow. Screenshots and video clips are taken during the process.

Use Case:

The following are the output from the agent:

Antigravity was capable of opening the page and submitting the form. When a login is required, the agent will wait until you have logged in to the website.

The /browser command is useful when we need the most recent documentation from the web, change logs, testing web applications, or checking API statuses to complete a task.

Schedule Task

Antigravity 2 has built-in functionality for scheduling tasks. We will test it out by auto-entering a timesheet every 10 minutes.

Click on 'Scheduled Tasks':

Click on '+ New' button to create a new scheduled task:

Fill in the form and schedule the task to run every 10 minutes:

The task was triggered, but it resulted in an error.

We tried adding 'env' values to the sidecar.json file, which is located at .gemini/config/sidecars/auto-timesheet-entry, but we still received the same error.

    "env": {
        "GEMINI_MODEL": "gemini-3.5-flash",
        "GOOGLE_CLOUD_PROJECT": "your-gcp-project-id"
    }

Inspecting the scheduled task logs located at .gemini/antigravity/sidecar_data/, we can see [schedule] Triggering command: "agentapi" [new-conversation].

The response to our issue posted in the Build with Google AI Forum suggests an API key is required for agentapi. We tried using the API key, but still had no luck.

We tried again with the command, /schedule, directly in the conversation box.

Tasks scheduled using the /schedule command will not appear under the 'Scheduled Tasks' menu item.

The cron task did get triggered.

Final thoughts

The /browserand /schedule commands in Antigravity 2 are not just isolated features, combining them creates a powerful tool. For example, scheduling an agent to use /browser to navigate to news and information websites every Monday morning at 6:00 AM, synthesise the info, and deliver a comprehensive daily briefing.

Other commands, such as /grill-me (mentioned in the article Antigravity 2 in Action: AI Agents, Skills, and MCP), can be used when designing new scheduled tasks. It prompts the agent to ask users to clarify ambiguities and catch edge cases before finalising the design.