Atlas AI Resources

Guide

Google Jules: a guide to plans, tasks, and scheduled runs

By Atlas AI Resources · Published November 13, 2026

Jules is Google's asynchronous coding agent. You give it a GitHub repository and a task, it writes a plan, and then it works in a cloud virtual machine while you do something else. This page starts with our own advice for a first setup, then summarizes what the Jules docs say about tasks, environments, scheduled and suggested tasks, the command line and API, and plan limits.

1. Our advice: a first safe setup

2. Per the docs: how a task runs

3. Per the docs: environments and snapshots

4. Per the docs: scheduled and suggested tasks

5. Per the docs: CLI and API

6. Per the docs: plans and limits

The plans page lists three tiers. Limits count over a rolling 24 hours, and the docs say they may change.

Paid plans currently go through a Google AI subscription on personal Google accounts ending in @gmail.com, and there's an interest form for business users. Family plan members each get their own limits, and Jules requires users to be 18 or older. At the limit, the new task button is disabled, but you can still review and manage existing tasks.

7. How this compares

Jules follows the same basic pattern as other cloud coding agents: an isolated machine, a prepared environment, and a branch or pull request that waits for a person. Its plan-first step is the part that stands out. See our OpenAI Codex Cloud guide, GitHub Copilot cloud agent guide, and Cursor Cloud Agents guide. Whichever you use, keep the real gate in your repository settings (branch protection and required reviews), not in the prompt.

Related: OpenAI Codex Cloud guide · GitHub Copilot cloud agent guide · Cursor Cloud Agents guide · Claude Code guide · Scheduling AI agent routines · Keeping AI agents safe from prompt injection · Parallel agent campaigns · Devin guide