Jules vs AOSplane

The short version

Both can begin with a GitHub issue and end with a pull request a person reviews. Jules uses its own agent in a VM. AOSplane uses Claude Code or Codex, and runs scope, review, and QA before that person is the first reviewer. The same loop accepts a Linear issue or a Jira ticket.

Jules also listens to a label. AOSplane listens to Linear and Jira Cloud as well as the console and the API. The GitHub repository is where the pull request lands in both cases.

How a Jules task starts

The getting-started guide says you connect GitHub, pick a repository and a branch, and write a prompt. You can add environment setup. “Give me a plan” produces a plan you review and approve before Jules changes code. The VM clones the repo, installs dependencies, and edits files. Jules looks for AGENTS.md at the repository root.

The running-tasks guide adds a second door. Label a GitHub issue “jules”, with the Jules GitHub app installed on that repo, and Jules comments on the issue. When it finishes, the comment links the pull request. Publishing a branch makes you the branch owner and Jules the commit author. You can open the pull request from Jules, or from the branch yourself.

Approving a plan before code is a real step on Jules. AOSplane’s Plan first step is the same shape and a different author: the product manager writes the spec, each acceptance criterion has a check, and you approve it in the console. The session’s agent only then writes code. QA runs those checks. The draft opens after they pass. Agents cannot push.

What caps the spend

AOSplane checks the organization, the project, and the agent before a task starts. The tightest limit is a hard cap on that task. Over it, the task does not start. The cost of the task is part of what arrives with the pull request. Jules’s getting-started guide does not describe a per-task cap. It also does not describe connecting an Anthropic or OpenAI key. The run, as documented, is Jules’s.

What the changelog says about the calendar

On 29 October 2026 Jules published a turndown note. It says Jules winds down on 31 December 2026, that you have until 11 November 2026 to finish sessions, and that after 11 November 2026 Jules turns read-only until the end of the year. Code, branches, and pull requests stay on GitHub. The export covers what lives in Jules: settings, environment variables, scheduled tasks, connected repos, memories, setup scripts, and each session’s prompt, plan, activity log, and patches. The note tells you to install the Jules CLI and sign in. It names Google Antigravity as a place those lessons are going. This page does not describe Antigravity.

AOSplane does not import that export. A repository Jules already pushed to GitHub can be linked to an AOSplane project and used for a new task. The Jules session history does not come with it.

Side by side

When Jules is the better place to spend the day

• You have a session to finish, and the changelog’s date for finishing sessions is 11 November 2026.
• You want the export of Jules settings and session history before the service is read-only.
• The branches and pull requests you care about are already on GitHub, which Jules says it does not take with it.

When AOSplane is the better fit

• The next pull request should already have been scoped, reviewed, and QA-tested, on Claude Code or Codex.
• The ticket can be a Linear issue or a Jira ticket, and the gate is the same. Claude Code on a Linear ticket.
• That task should have a hard spend cap. How the cap is set.
• The team is an agency with one project per client. How that split works.

Read how the same gate runs from Linear or Jira. Pricing starts with a self-serve Free plan.

The turndown dates are from Jules’s changelog of 29 October 2026. Setup is from Getting started and Running tasks. All three were read on 11 November 2026 and may have changed. Jules is not an AOSplane product.