Jules vs Unstoppable

Jules

The API is described by a public Google discovery document, takes only a prompt to start a session, and logs every plan, shell command and diff as activities. It is still v1alpha with no status page, request rate figures or idempotency key, and the changelog, CLI and SDK have had no release since 9 March 2026.

Unstoppable

Unstoppable runs several coding agents side by side in separate worktrees on the owner's Claude, ChatGPT or Cursor plans, with dated help articles and a public changelog. It has no API, MCP server or documented command an outside agent can call, every chat starts in Full access, and its pages disagree on which parts need a paid plan.

Jules

1. Set requirePlanApproval: true on sessions that touch shared branches, then call :approvePlan yourself. API sessions otherwise run their plan without review
2. Session creation has no request ID. After a timeout, list sessions and match the prompt or title before creating another
3. Poll activities with a create_time filter and cache them. Activities never change once written
4. Read the request fields from the discovery document at https://jules.googleapis.com/$discovery/rest?version=v1alpha. The field tables on jules.google render empty
5. Budget against the daily task quota of 15, 100 or 300 by plan. New sessions are refused until the rolling 24 hours reset

Unstoppable

1. Don't plan to drive Unstoppable from another agent. It has no documented API, MCP server or CLI. Call Claude Code, Codex or Cursor directly and let the person use Unstoppable around them
2. Inside Unstoppable, check the approval mode before acting. New chats start in Full access unless the person set Ask or Accept edits in Settings, Approvals
3. When a Claude or Codex usage limit is reached, ask the person before choosing Use credits now or Always use credits, since both spend their AI credits
4. Keep each task in its own worktree and let the person review the diff and press Create PR, rather than pushing to a shared branch