How does Google Jules authenticate to GitHub?

The Jules GitHub App, installed per repository.

Who is the author of commits made by Google Jules?

Pull requests are opened by `google-labs-jules[bot]`.

Where does Google Jules run code, and what are its limits?

A temporary Google Cloud VM created for the task and destroyed afterwards. Quotas by plan: 15 tasks per day and 3 concurrent on the free tier, up to 300 per day and 60 concurrent on Ultra.

Reference · Google · updated 27 September 2026

How Google Jules connects to GitHub

A bot account and a per-task VM, with hard daily quotas. Here is what its public documentation says about authentication, commit attribution, the sandbox it runs in, how you hand it work, and the limits you will hit.

Auth	The Jules GitHub App, installed per repository.
Attribution	Pull requests are opened by `google-labs-jules[bot]`.
Sandbox	A temporary Google Cloud VM created for the task and destroyed afterwards.
Task intake	The Jules web UI, a `jules` label on an issue, the jules-action for GitHub Actions, and a CLI.
Limits	Quotas by plan: 15 tasks per day and 3 concurrent on the free tier, up to 300 per day and 60 concurrent on Ultra.

Unverified: The bot account name is observed in public repositories; the documentation does not spell it out.

Where it hurts

Every cloud agent in this series invents its own identity and attribution model, because the host gives them nothing to stand on. The consequences are the same across vendors: agents share a person's token or an org-wide app installation, so a fleet hits secondary rate limits as one user; attribution lives in free-text trailers the host never reads; and rules like "a human must approve changes under this path" are left to the agent to enforce on itself.

What githug Gateway changes

Its own credential. Google Jules gets a short-lived identity scoped to the person who launched it, with its own rate budget and audit log, instead of sharing a token.
Its trailers become fields. The co-author, session and disclosure trailers it already writes are parsed and stored with the commit, so reviewers can filter on them.
Your rules run on the server. Path approval, required tests, disclosure and token budgets are checked at push and reported back as a status check.

Running Google Jules against a real repo?

Paste this to your coding agent. A human approves one code on github.com; the agent does the rest.

Set up githug for owner/repo: run `curl -fsSL https://githug.ai/install | sh`, then `hug init --repo owner/repo --json`. Show me any code or link it prints and wait for it to finish.

Quickstart · Set it up yourself · free during the beta

How Google Jules connects to GitHub

Where it hurts

What githug Gateway changes

Running Google Jules against a real repo?

Sources

Other agents in this series