Showcase


Products
Google, product by product →Google ships more than one product — each judged line competes in its own arena on the same stories as everyone else.
| Line | Arena | Rank | PA Score | Agent-ready |
|---|---|---|---|---|
| Gemini | AI Assistants | #7/9 | 17/100 | 9/100 |
| Antigravity | AI Coding Agents | #5/13 | 37/100 | 55/100 |
| Gemini CLI | AI Coding Agents | #12/13 | 21/100 | 38/100 |
| Gemini Notebook (NotebookLM) | AI Research Agents | #6/6 | 7/100 | 0/100 |
| Julesthis page | Software Factory | #7/9 | 23/100 | 29/100 |
| Agent Development Kit | Agent Frameworks & SDKs | #4/9 | 35/100 | 46/100 |
| Firebase | Backend as a Service | #3/4 | 35/100 | 43/100 |
| Angular | Frontend Frameworks | #3/5 | 28/100 | 12/100 |
Not yet judged (4 — no arena where they compete): Google AI Studio · Flow · Gemini in Chrome · Gemini Code Assist
Verified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Autonomous implementation — end-to-end implementation by the agent — multi-file changes, task completionAutonomous implementationevidence →
End-to-end implementation by the agent — multi-file changes, task completion
Human oversight — keeping a human in the loop — approvals, checkpoints, interruptsHuman oversightevidence →
Keeping a human in the loop — approvals, checkpoints, interrupts
Intent to spec — stories about intent to spec in this arenaIntent to specevidence →
Stories about intent to spec in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limitsevidence →
Free-tier ceilings, usage caps, and rate limits before you have to pay
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Repo integration — stories about repo integration in this arenaRepo integrationevidence →
Stories about repo integration in this arena
Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gatesevidence →
Quality gates on changes — review flow, required checks, merge protection
Scale parallelism — running many jobs at once — concurrency, fleets, queueingScale parallelismevidence →
Running many jobs at once — concurrency, fleets, queueing
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 4 free · 0 paid · 0 enterprise · 35 not stated in evidence
Follow the green: where the map greys out is where Jules stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Webhooks · Scoped API keys · Machine-readable spec · Versioning policy · Official CLI · Full data export · Go from a mockup or design to a working implementation without an engineering handoff · Query generated documentation for any public or private repository · Connect issue trackers like Jira, Linear, ClickUp, or Monday.com so agents can manage tickets directly
Subscribe to events via webhooks
—0/10
Build against official SDKs
✓7/10
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
n/an/a
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
~5/10
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
—0/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
✓8/10
unlocks → MCP client
Operate the product with natural-language commands
✓8/10
Plug MCP servers into this product so it can use their tools
—0/10
Get AI-generated insights and suggestions from my data inside the product
~6/10
Set up automations that run autonomously in the background
~6/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Autonomous implementation — end-to-end implementation by the agent — multi-file changes, task completionAutonomous implementation
End-to-end implementation by the agent — multi-file changes, task completion
End to end feature delivery
Have an agent automatically clone the repo, install dependencies, and configure its own working environment
✓8/10
Interactive takeover
Have an agent safely execute code and install dependencies inside an isolated sandbox
✓8/10
Human oversight — keeping a human in the loop — approvals, checkpoints, interruptsHuman oversight
Keeping a human in the loop — approvals, checkpoints, interrupts
Approval controls
Model control
Intent to spec — stories about intent to spec in this arenaIntent to spec
Stories about intent to spec in this arena
Natural language task intake
Plan approval
Assign a coding task to an agent directly from an existing issue or ticket
✓8/10
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits
Free-tier ceilings, usage caps, and rate limits before you have to pay
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Repo integration — stories about repo integration in this arenaRepo integration
Stories about repo integration in this arena
Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gates
Quality gates on changes — review flow, required checks, merge protection
Ci remediation
Diff review
Pr review automation
Readiness checks
Have security alerts automatically validated and remediated with an opened pull request
—0/10
Scale parallelism — running many jobs at once — concurrency, fleets, queueingScale parallelism
Running many jobs at once — concurrency, fleets, queueing
Concurrent execution
Deployment flexibility
Run an agent headlessly inside CI/CD pipelines and shell scripts
~5/10
Sorted by importance (agentic first) (high → low) · 73/73 stories · click a row’s chevron for the rationale and evidence
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Xcommunity | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | 0/10 | ||
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | fullfree | 8/10 | Xcommunity | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Xcommunity | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Xcommunity | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Xcommunity | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partial | 5/10 | Cclaimed | |
Connect a GitHub repository so an agent can access the code and open pull requests against it C Version control integration | developer | Repo integration — stories about repo integration in this arenaRepo integration | 3 | full | 9/10 | Xcommunity | |
Review a diff of an agent's changes and approve it before it becomes a pull request C Diff review | developer | Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gates | 3 | full | 9/10 | Xcommunity | |
Assign a coding task to an agent directly from an existing issue or ticket C Ticket driven tasking | developer | Intent to spec — stories about intent to spec in this arenaIntent to spec | 3 | full | 8/10 | Xcommunity | |
Have an agent autonomously diagnose and fix a reported bug C End to end feature delivery | developer | Autonomous implementation — end-to-end implementation by the agent — multi-file changes, task completionAutonomous implementation | 3 | fullfree | 8/10 | Xcommunity | |
Have an agent safely execute code and install dependencies inside an isolated sandbox C Sandbox execution | developer | Autonomous implementation — end-to-end implementation by the agent — multi-file changes, task completionAutonomous implementation | 3 | full | 8/10 | Xcommunity | |
Review and approve an agent's implementation plan before any code changes are made C Plan approval | developer | Intent to spec — stories about intent to spec in this arenaIntent to spec | 3 | full | 8/10 | Cclaimed | |
Add a context file describing my codebase conventions so agents generate more relevant plans and code C Knowledge context | developer | Repo integration — stories about repo integration in this arenaRepo integration | 3 | full | 7/10 | Cclaimed | |
Describe a feature or bug in plain language and have it automatically turned into a scoped implementation task C Natural language task intake | developer | Intent to spec — stories about intent to spec in this arenaIntent to spec | 3 | partial | 6/10 | Xcommunity | |
Have an agent implement a requested feature end-to-end, including writing tests C End to end feature delivery | developer | Autonomous implementation — end-to-end implementation by the agent — multi-file changes, task completionAutonomous implementation | 3 | partial | 6/10 | Xcommunity | |
Run many agent tasks concurrently to scale delivery throughput C Concurrent execution | engineering-lead | Scale parallelism — running many jobs at once — concurrency, fleets, queueingScale parallelism | 3 | partialfree | 6/10 | Xcommunity | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 5/10 | Cclaimed | |
Watch what a running agent is doing in real time, including its current status C Visibility monitoring | developer | Human oversight — keeping a human in the loop — approvals, checkpoints, interruptsHuman oversight | 3 | partial | 5/10 | Xcommunity | |
Set tiered autonomy levels controlling what an agent can do without manual confirmation C Approval controls | engineering-lead | Human oversight — keeping a human in the loop — approvals, checkpoints, interruptsHuman oversight | 3 | partial | 4/10 | Cclaimed | |
Have failed CI workflows automatically diagnosed and fixed with a proposed pull request C Ci remediation | engineering-lead | Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gates | 3 | partial | 3/10 | Cclaimed | |
Have every pull request automatically reviewed with AI-generated inline comments C Pr review automation | engineering-lead | Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gates | 3 | none | 0/10 | ||
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ||
Connect issue trackers like Jira, Linear, ClickUp, or Monday.com so agents can manage tickets directly C Project management integration | product-manager | Repo integration — stories about repo integration in this arenaRepo integration | 3 | none | untested | none yet | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Configure an agent to automatically open a pull request when its task completes C Diff review | developer | Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gates | 2 | full | 8/10 | Xcommunity | |
Get notified when an agent completes a task or needs my input C Visibility monitoring | developer | Human oversight — keeping a human in the loop — approvals, checkpoints, interruptsHuman oversight | 2 | full | 8/10 | Xcommunity | |
Have an agent automatically clone the repo, install dependencies, and configure its own working environment C Environment setup | developer | Autonomous implementation — end-to-end implementation by the agent — multi-file changes, task completionAutonomous implementation | 2 | full | 8/10 | Xcommunity | |
Use a managed cloud offering to run agents without operating my own backend infrastructure C Deployment flexibility | developer | Scale parallelism — running many jobs at once — concurrency, fleets, queueingScale parallelism | 2 | full | 8/10 | Xcommunity | |
Send follow-up instructions to an active agent session to steer its work without restarting C Interactive takeover | developer | Autonomous implementation — end-to-end implementation by the agent — multi-file changes, task completionAutonomous implementation | 2 | full | 7/10 | Xcommunity | |
Approve a task's scope and contract before an agent is allowed to modify the repository C Plan approval | engineering-lead | Intent to spec — stories about intent to spec in this arenaIntent to spec | 2 | partial | 6/10 | Cclaimed | |
Grant an agent access to my repositories with a one-click install, without complex setup C Version control integration | developer | Repo integration — stories about repo integration in this arenaRepo integration | 2 | partial | 6/10 | Xcommunity | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 5/10 | Tprobed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 5/10 | Xcommunity | |
Run an agent headlessly inside CI/CD pipelines and shell scripts C Headless automation | developer | Scale parallelism — running many jobs at once — concurrency, fleets, queueingScale parallelism | 2 | partial | 5/10 | Xcommunity | |
Take over an in-progress agent task in my editor, terminal, or browser to finish or redirect the work C Interactive takeover | developer | Autonomous implementation — end-to-end implementation by the agent — multi-file changes, task completionAutonomous implementation | 2 | partial | 5/10 | Xcommunity | |
Trigger an agent from CI/CD pipelines to fix a broken build or failing test C Ci remediation | developer | Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gates | 2 | partial | 5/10 | Xcommunity | |
Configure an agent to auto-approve all its actions instead of confirming each one C Approval controls | developer | Human oversight — keeping a human in the loop — approvals, checkpoints, interruptsHuman oversight | 2 | partial | 4/10 | Cclaimed | |
Have an agent automatically generate and run tests to validate its own code changes before proposing them C End to end feature delivery | ai-native user | Autonomous implementation — end-to-end implementation by the agent — multi-file changes, task completionAutonomous implementation | 2 | partial | 4/10 | Xcommunity | |
See and manage plan-based daily task and concurrency limits for agent workflows G Usage quotas | engineering-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 2 | partialfree | 4/10 | Xcommunity | |
Tag an agent in a chat thread to discuss and delegate a bug or task C Chat integration | developer | Repo integration — stories about repo integration in this arenaRepo integration | 2 | partial | 4/10 | Xcommunity | |
Bring my own LLM or API key so agents run on the model of my choice C Model flexibility | engineering-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 2 | none | 0/10 | ||
Convert user feedback submissions into structured tasks with proposed scope C Natural language task intake | product-manager | Intent to spec — stories about intent to spec in this arenaIntent to spec | 2 | none | 0/10 | ||
Create agent sessions on behalf of other users in my organization C Concurrent execution | engineering-lead | Scale parallelism — running many jobs at once — concurrency, fleets, queueingScale parallelism | 2 | none | 0/10 | ||
Go from a mockup or design to a working implementation without an engineering handoff C End to end feature delivery | product-manager | Autonomous implementation — end-to-end implementation by the agent — multi-file changes, task completionAutonomous implementation | 2 | none | 0/10 | ||
Have each task prompt automatically routed to the most suitable underlying model C Model control | ai-native user | Human oversight — keeping a human in the loop — approvals, checkpoints, interruptsHuman oversight | 2 | none | 0/10 | ||
Have incoming issues automatically triaged with severity suggested and routed to the right owner C Pr review automation | ai-native user | Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gates | 2 | none | 0/10 | ||
Have security alerts automatically validated and remediated with an opened pull request C Security remediation | engineering-lead | Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gates | 2 | none | 0/10 | ||
License an enterprise deployment with SSO and commercial support for organization-wide rollout G Enterprise licensing | engineering-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 2 | none | 0/10 | ||
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | 0/10 | ||
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | 0/10 | ||
Self-host agent infrastructure locally, in containers, or on my own VMs C Deployment flexibility | engineering-lead | Scale parallelism — running many jobs at once — concurrency, fleets, queueingScale parallelism | 2 | none | 0/10 | ||
Attach a marked-up screenshot or mockup to a task so the agent implements the correct visual change C Natural language task intake | developer | Intent to spec — stories about intent to spec in this arenaIntent to spec | 2 | none | untested | none yet | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Run a readiness report that evaluates how ready my repository is for autonomous agents C Readiness checks | engineering-lead | Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gates | 2 | none | untested | none yet | |
Approve key agent decisions from my phone while agents continue working C Approval controls | product-manager | Human oversight — keeping a human in the loop — approvals, checkpoints, interruptsHuman oversight | 1 | partial | 6/10 | Xcommunity | |
Automatically fix failing agent-readiness criteria in my repository C Readiness checks | engineering-lead | Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gates | 1 | none | 0/10 | ||
Query generated documentation for any public or private repository C Knowledge context | developer | Repo integration — stories about repo integration in this arenaRepo integration | 1 | none | 0/10 | ||
Switch away from automatic model selection to a specific model of my choice C Model control | engineering-lead | Human oversight — keeping a human in the loop — approvals, checkpoints, interruptsHuman oversight | 1 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | none | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 55 stories with headroom
What would move Jules’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
No evidence that Jules can connect to or consume external MCP servers as tool providers; the only MCP-related evidence (jules-comm-19) describes someone building an MCP server that calls INTO the Jules API, which is the reverse integration direction, not Jules plugging in MCP servers for its own tool use.
Review quality gates — quality gates on changes — review flow, required checks, merge protectionHave every pull request automatically reviewed with AI-generated inline comments
nonemoves PA Scoreimpact 30
Jules is documented as a task-execution agent that clones repos, makes code changes, and creates its own PRs for approval — not as a bot that automatically reviews incoming pull requests with inline comments.
Repo integration — stories about repo integration in this arenaConnect issue trackers like Jira, Linear, ClickUp, or Monday.com so agents can manage tickets directly
nonemoves PA Scoreimpact 30
Evidence only shows Jules integrating with GitHub (repos, issues, PRs) and provides an API for custom workflows, but there is no mention of Jira, Linear, ClickUp, Monday.com, or any issue-tracker integration beyond GitHub.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
Missing: any documentation of data export, open format support, or account portability/deletion workflow.
Openness — open source, data portability, and self-hosting storiesSelf-host the core product
nonemoves PA Scoreimpact 30
Jules is explicitly a cloud-based VM service (Google-hosted) with no evidence of any self-hosting option; community even notes cloud-only design as a drawback compared to local tools like Claude Code.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
No evidence in the pack addresses data usage/training opt-out policies, privacy controls, or any statement about whether user code/data is used to train AI models; the docs focus on functionality (VM execution, PR creation, API) rather than data governance.
Agenticness — how well agents can access and operate the productPoint an agent at llms.txt or agent-oriented docs
nonemoves agent-readyimpact 30
Probes show no llms.txt, docs.md, or machine-readable API spec exist at expected paths, and no evidence Jules can be pointed at such agent-oriented documentation formats; Jules does support AGENTS.md for repo context but that's a different mechanism than consuming llms.txt-style docs.
Agenticness — how well agents can access and operate the productUse an official CLI
nonemoves agent-readyimpact 30
Evidence shows Jules offers a web app, GitHub integration, and a REST API for custom workflows, but no official CLI tool is documented or mentioned anywhere in the evidence pack.
Showing the top 8 of 55 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map5 surfaces · 39 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Hacker News31 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Perform bulk operations across many items at once
- Have an agent automatically generate and run tests to validate its own code changes before proposing them
- Have an agent autonomously diagnose and fix a reported bug
- Have an agent implement a requested feature end-to-end, including writing tests
- Have an agent automatically clone the repo, install dependencies, and configure its own working environment
- Take over an in-progress agent task in my editor, terminal, or browser to finish or redirect the work
- Send follow-up instructions to an active agent session to steer its work without restarting
- Have an agent safely execute code and install dependencies inside an isolated sandbox
- Approve key agent decisions from my phone while agents continue working
- Watch what a running agent is doing in real time, including its current status
- Get notified when an agent completes a task or needs my input
- Describe a feature or bug in plain language and have it automatically turned into a scoped implementation task
- Assign a coding task to an agent directly from an existing issue or ticket
- Do everything through the API that I can do in the UI
- See and manage plan-based daily task and concurrency limits for agent workflows
- Tag an agent in a chat thread to discuss and delegate a bug or task
- Connect a GitHub repository so an agent can access the code and open pull requests against it
- Grant an agent access to my repositories with a one-click install, without complex setup
- Trigger an agent from CI/CD pipelines to fix a broken build or failing test
- Configure an agent to automatically open a pull request when its task completes
- Review a diff of an agent's changes and approve it before it becomes a pull request
- Run many agent tasks concurrently to scale delivery throughput
- Use a managed cloud offering to run agents without operating my own backend infrastructure
- Run an agent headlessly inside CI/CD pipelines and shell scripts
docs29 stories
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Test against a sandbox environment without touching production data
- Perform bulk operations across many items at once
- Have an agent automatically generate and run tests to validate its own code changes before proposing them
- Have an agent autonomously diagnose and fix a reported bug
- Have an agent implement a requested feature end-to-end, including writing tests
- Have an agent automatically clone the repo, install dependencies, and configure its own working environment
- Take over an in-progress agent task in my editor, terminal, or browser to finish or redirect the work
- Send follow-up instructions to an active agent session to steer its work without restarting
- Have an agent safely execute code and install dependencies inside an isolated sandbox
- Configure an agent to auto-approve all its actions instead of confirming each one
- Approve key agent decisions from my phone while agents continue working
- Set tiered autonomy levels controlling what an agent can do without manual confirmation
- Watch what a running agent is doing in real time, including its current status
- Get notified when an agent completes a task or needs my input
- Describe a feature or bug in plain language and have it automatically turned into a scoped implementation task
- Review and approve an agent's implementation plan before any code changes are made
- Approve a task's scope and contract before an agent is allowed to modify the repository
- Assign a coding task to an agent directly from an existing issue or ticket
- See and manage plan-based daily task and concurrency limits for agent workflows
- Add a context file describing my codebase conventions so agents generate more relevant plans and code
- Connect a GitHub repository so an agent can access the code and open pull requests against it
- Grant an agent access to my repositories with a one-click install, without complex setup
- Review a diff of an agent's changes and approve it before it becomes a pull request
- Run many agent tasks concurrently to scale delivery throughput
- Use a managed cloud offering to run agents without operating my own backend infrastructure
jules.google24 stories
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Test against a sandbox environment without touching production data
- Define rules that trigger actions automatically on events
- Have an agent autonomously diagnose and fix a reported bug
- Have an agent implement a requested feature end-to-end, including writing tests
- Take over an in-progress agent task in my editor, terminal, or browser to finish or redirect the work
- Configure an agent to auto-approve all its actions instead of confirming each one
- Approve key agent decisions from my phone while agents continue working
- Set tiered autonomy levels controlling what an agent can do without manual confirmation
- Watch what a running agent is doing in real time, including its current status
- Get notified when an agent completes a task or needs my input
- Describe a feature or bug in plain language and have it automatically turned into a scoped implementation task
- Review and approve an agent's implementation plan before any code changes are made
- Approve a task's scope and contract before an agent is allowed to modify the repository
- Assign a coding task to an agent directly from an existing issue or ticket
- Tag an agent in a chat thread to discuss and delegate a bug or task
- Connect a GitHub repository so an agent can access the code and open pull requests against it
- Grant an agent access to my repositories with a one-click install, without complex setup
- Have failed CI workflows automatically diagnosed and fixed with a proposed pull request
- Configure an agent to automatically open a pull request when its task completes
- Review a diff of an agent's changes and approve it before it becomes a pull request
- Use a managed cloud offering to run agents without operating my own backend infrastructure
Jules docs20 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Take over an in-progress agent task in my editor, terminal, or browser to finish or redirect the work
- Send follow-up instructions to an active agent session to steer its work without restarting
- Configure an agent to auto-approve all its actions instead of confirming each one
- Set tiered autonomy levels controlling what an agent can do without manual confirmation
- Do everything through the API that I can do in the UI
- Tag an agent in a chat thread to discuss and delegate a bug or task
- Have failed CI workflows automatically diagnosed and fixed with a proposed pull request
- Trigger an agent from CI/CD pipelines to fix a broken build or failing test
- Configure an agent to automatically open a pull request when its task completes
- Run many agent tasks concurrently to scale delivery throughput
- Use a managed cloud offering to run agents without operating my own backend infrastructure
- Run an agent headlessly inside CI/CD pipelines and shell scripts
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
9 of 11 testable claims verified · 0 contradicted → integrity 82/100
13 distinct capability claims found in Jules’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
9
Verified
2
Unverified
0
Contradicted
28
Undersold
Verified (10)
“Jules requires access to your repositories to operate”
Connect a GitHub repository so an agent can access the code and open pull requests against itfullproof ↗
“Assign a coding task to Jules directly from a GitHub issue using the 'jules' label”
Assign a coding task to an agent directly from an existing issue or ticketfullproof ↗
“Jules runs in a VM, cloning the repo, installing dependencies, and modifying files itself”
Have an agent automatically clone the repo, install dependencies, and configure its own working environmentfullproof ↗
“Jules runs in a VM, cloning the repo, installing dependencies, and modifying files itself”
Have an agent safely execute code and install dependencies inside an isolated sandboxfullproof ↗
“You get notified when a task finishes or needs your input”
Get notified when an agent completes a task or needs my inputfullproof ↗
“Jules produces a diff of changes you can browse and approve”
Review a diff of an agent's changes and approve it before it becomes a pull requestfullproof ↗
“Jules creates a pull request of its changes that you can approve, merge, and publish”
Configure an agent to automatically open a pull request when its task completesfullproof ↗
“A public API lets you build custom workflows, automate bug fixing/code review, and embed Jules into other tools”
Drive the product through a documented public APIfullproof ↗
“An automationMode API field controls whether a PR is auto-created after a task, off by default”
Configure an agent to automatically open a pull request when its task completesfullproof ↗
“Plan tiers define daily task and concurrency limits for power users and agent-heavy workflows”
See and manage plan-based daily task and concurrency limits for agent workflowspartialproof ↗
Unverified (2)
“Jules generates an implementation plan that you can review and approve before code changes happen”
Review and approve an agent's implementation plan before any code changes are madefullproof ↗
“Jules automatically detects and uses an AGENTS.md file in the repo root for context”
Add a context file describing my codebase conventions so agents generate more relevant plans and codefullproof ↗
Undersold (28)
Run the product headlessly / in CI for automationfullproof ↗
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Delegate tasks to a built-in AI assistant inside the productfullproof ↗
Operate the product with natural-language commandsfullproof ↗
Test against a sandbox environment without touching production datapartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
Have an agent automatically generate and run tests to validate its own code changes before proposing thempartialproof ↗
Have an agent autonomously diagnose and fix a reported bugfullproof ↗
Have an agent implement a requested feature end-to-end, including writing testspartialproof ↗
Take over an in-progress agent task in my editor, terminal, or browser to finish or redirect the workpartialproof ↗
Send follow-up instructions to an active agent session to steer its work without restartingfullproof ↗
Configure an agent to auto-approve all its actions instead of confirming each onepartialproof ↗
Approve key agent decisions from my phone while agents continue workingpartialproof ↗
Set tiered autonomy levels controlling what an agent can do without manual confirmationpartialproof ↗
Watch what a running agent is doing in real time, including its current statuspartialproof ↗
Describe a feature or bug in plain language and have it automatically turned into a scoped implementation taskpartialproof ↗
Approve a task's scope and contract before an agent is allowed to modify the repositorypartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Tag an agent in a chat thread to discuss and delegate a bug or taskpartialproof ↗
Grant an agent access to my repositories with a one-click install, without complex setuppartialproof ↗
Have failed CI workflows automatically diagnosed and fixed with a proposed pull requestpartialproof ↗
Trigger an agent from CI/CD pipelines to fix a broken build or failing testpartialproof ↗
Run many agent tasks concurrently to scale delivery throughputpartialproof ↗
Use a managed cloud offering to run agents without operating my own backend infrastructurefullproof ↗
Run an agent headlessly inside CI/CD pipelines and shell scriptspartialproof ↗
Claims outside our story set (2)
Real capability claims found in Jules’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“You can create and manage API keys (up to 3 at a time) from the web app settings”
source ↗“Priority access to the latest underlying models, starting with Gemini 3 Pro”
source ↗
Business model
Free tier with daily/concurrent task limits on an older Gemini model; higher limits and newer Gemini models are bundled into paid Google AI Pro/Ultra subscriptions.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
