Jules vs Paseo

Jules 18

Closed service. The newest API or product change is the changelog entry of 9 March 2026, 241 days before 5 November (0). The changelog's 29 October 2026 entry announces the wind-down and an export route through the CLI, which is a notice, not an API change. No package releases, commits or tags in the 90 days, and the jules-sdk repository's last commit is 18 March 2026 (0). A public changelog and a Discord channel. The 18 October issue and pull request counts came from shields.io badges and are struck (8 of 15, a partial held). The official TypeScript SDK and MCP packages last published 0.2.0 on 9 March 2026, per the 18 October registry reading, and no official MCP registry entry could be read (5). The SDK has a CI workflow on pull requests whose results couldn't be read, and two runtime dependencies. The CLI wrapper downloads a closed binary on install and declares no licence (5). 0 + 0 + 8 + 5 + 5 = 18.

Paseo 75

v0.15.3 and commits on 7 November 2026 (30). More than three releases in 90 days (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current builds (15). CI on push (10). 30 + 20 + 0 + 15 + 10 = 75.

Jules 13

Hosted reading. No status page for Jules was found (0). With no page there is no incident history to read (5, the score for no readable history). The plans page, re-read on 5 November, publishes task quotas with numbers, 15, 100 and 300 tasks a rolling 24 hours and 3, 15 and 60 concurrent, and list pageSize is capped at 100, but no request rate figures were found (8 of 15). 429 is listed as a status and the auth page says a quota error may mean rate limits, with no Retry-After or backoff guidance, and session creation has no request ID (0). No SLA found (0). The API is v1alpha and labelled experimental, and the changelog of 29 October 2026 says Jules turns read-only after 11 November (0). 0 + 5 + 8 + 0 + 0 + 0 = 13.

Paseo 50

Local software. Desktop builds, an Android APK, a Docker image and a Nix package (20). ci.yml on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). CHANGELOG.md (15). Version 0.15.3 (0). 20 + 15 + 0 + 15 + 0 = 50.

Jules 30

Published rubric. No payment protocol (0). Plans and their Jules limits are public without a login, and Jules sits inside the Google AI plans. The prices render per locale and weren't read, and there's no per-task price (10). A free plan of 15 tasks a day with a Google account, and no card step in the sign-up docs, until new tasks stop after 11 November 2026 (20). A person signs in, accepts the privacy notice, installs the GitHub app and creates the key in the web app (0). 0 + 10 + 20 + 0 = 30.

Paseo 60

Free self-hosted software with nothing to buy, so 0 for a protocol and 20 each for public pricing, a free tier and onboarding with no sign-up, 60.

Jules 51

Editorial half. Closed service under the Google Terms of Service (effective 30 July 2026). The SDK is Apache-2.0, but npm lists @google/jules-mcp as ISC while its README says Apache-2.0, and @google/jules declares no licence (12). The FAQ says private repositories aren't used for training. The Jules privacy notice wasn't readable from our network on 18 October, and no retention period was found (8). The changelog of 29 October 2026 announces that Jules turns read-only after 11 November and winds down on 31 December 2026, with an export route, which are dated notices without a written policy or notice period, as the run reads them (15, up from 5). No subprocessor or data location statement found (0). 12 + 8 + 15 + 0 = 35.

Paseo 68

Apache 2.0 for everything but third-party components (30). No telemetry and agents run on your machine (22 of 30). CHANGELOG.md, no deprecation policy (10). States no telemetry (20). 30 + 22 + 10 + 20 = 82.

Jules 76

API reading. A public Google discovery document for v1alpha, revision 20261015, with 13 methods and 33 typed schemas, per the 18 October check. It sits on the API's own host and wasn't requested again (25). docs/llms.txt and a Markdown twin of every docs page (10). Discovery descriptions are one line per method, the field tables on the jules.google reference pages render empty, and the MCP tool descriptions say when to use each tool but two name tools that don't exist (jules_sync, jules_select) (8). Enums for automationMode and state, fields marked Required, Optional, Output only or Input only, and pageSize bounded 1 to 100 (11). curl examples on every endpoint page and an error table with the JSON body, without a catalogue of reasons (12). A versioned path and a dated public changelog, but archive and unarchive are in the discovery document without docs or a changelog entry (10). 25 + 10 + 8 + 11 + 12 + 10 = 76.

Paseo 65

Harness reading. Public docs, a CLI and plugin examples in the repository (65).

Jules 64

API and MCP reading, per the 18 October check. Responses can be sized with pageSize, the standard fields parameter and a create_time filter that fetches only new activities. The MCP server has 8 tools, and query_cache takes a token budget (20). Token pagination on every list and filters on sessions, activities and sources (16). Google's error JSON with status and an ErrorInfo reason, plus a documented status table (14). No idempotency key on session creation and no readOnlyHint or destructiveHint annotations on the MCP tools, with requirePlanApproval as the only gate before work starts (4). Only prompt is required and a session without a source runs repoless. One official SDK, in TypeScript, plus the MCP server and CLI (10). 20 + 16 + 14 + 4 + 10 = 64.

Paseo 70

Harness reading. A self-hosted daemon that agents can use to create worktrees, launch other agents and talk to them, scriptable from the CLI (70).