Jules

Plan

1. SupportsWork planning: Supports

   Work planning, supports. Jules writes a step-by-step plan for each task before coding, and Suggested Tasks turns #TODO comments into proposed work on up to five repositories. The backlog itself stays in an issue tracker.

Build

1. Codebase context: Supports

   Codebase context, supports. Each Jules task clones the repository and reads AGENTS.md and the README. Repository memory retains corrections for later tasks. Jules provides no standing team code index or search.

2. JulesCoreCoding: Core

   Coding, core. This is Jules's primary role. It writes and changes code for a delegated task in a cloud VM and publishes a branch or pull request for human review.

3. Agent runtime: Supports

   Agent runtime, supports. Work happens in the jules.google.com web app, the Jules Tools CLI and its terminal dashboard, or through the API. Jules does not run in the developer's editor or on their machine.

4. Tool execution: Core

   Tool execution, core. Jules installs dependencies and runs builds, tests, and Playwright in its VM. It calls six vetted MCP servers, including Linear and Supabase. GitHub issues, schedules, the API, and a GitHub Action can start work.

Validate

1. Debugging: Supports

   Debugging, supports. Jules fixes bugs described in a task or issue and reads failing build logs from Render deployments, but it is not a production debugging or error-tracking tool.

2. Testing: Supports

   Testing, supports. Jules runs tests in its VM and renders frontend changes with Playwright. A critic agent reviews each change, while the team's CI remains the test of record.

3. TouchesCode review: Touches

   Code review, touches. Jules responds to comments on its pull requests, and its critic checks its changes. It does not review other people's pull requests.

4. Application security: Touches

   Application security, touches. Jules can run a scheduled security-focused task that opens fix pull requests, but it offers no scanning, policy, or vulnerability management of its own.

Ship

1. Source control: Touches

   Source control, touches. Jules publishes branches and pull requests through the Google Labs Jules GitHub app and works only with GitHub repositories; GitHub stays the system of record.

2. CI/CD: Touches

   CI/CD, touches. CI Fixer repairs failing GitHub Actions checks on Jules' pull requests. The Render integration fixes failed deployments. Your CI/CD platform owns the pipelines.

Operate

1. Observability: Touches

   Observability, touches. Jules provides no monitoring or alerting. Incidents reach it only as tasks someone writes.