Operator Insights

Reported by others2

1. 

   AK KulkarniProduct ManagementGoogle Labs

   Google's Stitch design-agent team. Daily Scheduled Tasks. Stitch repository.

   Google, published Dec 10, 2025Read the announcement (opens Google in a new tab)

   Observation

   Google's Stitch team runs a pod of daily Jules agents, each with one maintenance role.

   Takeaway

   Recurring, role-scoped maintenance is where scheduled Jules agents pay off. Google publishes no merge rate or review time, so measure both before you copy the pattern.

   What happened

   Google's Stitch team assigned daily Jules agents to specific maintenance roles through Scheduled Tasks. The roles covered performance tuning, security patches, accessibility, and test coverage. Google says Jules became one of the Stitch repository's largest contributors, leaving engineers to work on features.

   • Vendor case study (Google's own team)
   • No metrics published
   • No model named

   Deployment details

   Google's Stitch design-agent team. Daily Scheduled Tasks. Stitch repository.

   • Vendor case study (Google's own team)
   • No metrics published
   • No model named

   Workload

   Daily performance tuning, security patching, accessibility improvements, and test coverage

   Product version

   Jules Scheduled Tasks, launched December 10, 2025

1. Martin HellerNov 11, 2025InfoWorldInfoWorld's reviewer had Jules fix open bugs in two public repositories, and its self-review caught a stray file.

   

   Martin HellerContributing writerInfoWorld

   One reviewer. Free plan. Forks of websocket (Go) and qwen-code (TypeScript).

   Its own announcement, published Nov 11, 2025Read the review (opens the announcement in a new tab)

   Observation

   InfoWorld's reviewer had Jules fix open bugs in two public repositories, and its self-review caught a stray file.

   Takeaway

   The loop of compiling, testing, and self-review is what makes Jules more dependable than a bare model call. It still needs the human check Heller recommends keeping.

   What happened

   Heller asked Jules to pick an open bug report and fix it in two forked repositories. Jules fixed both. On qwen-code it hit build errors, fixed them, and its own code review flagged a JSON file that did not belong in the change, which the main thread then removed.

   • Public practitioner write-up (independent review)
   • Outcomes described per repository
   • Gemini 2.5 Pro

   Deployment details

   One reviewer. Free plan. Forks of websocket (Go) and qwen-code (TypeScript).

   • Public practitioner write-up (independent review)
   • Outcomes described per repository
   • Gemini 2.5 Pro

   Team

   One reviewer

   Workload

   Open bug reports in forks of two public repositories

   Product version

   Free plan (15 daily tasks, 3 concurrent) with the Jules Tools CLI

   Model

   Gemini 2.5 Pro