Jules favicon install runbook
Jules is Google's asynchronous agent: it clones your repo into a cloud VM, writes a plan, waits for you to approve it, then executes and opens a pull request. That approval gate is where you get favicons right. Say 'reference the existing icons, don't invent files' before it runs, not after. As with every agent, it can wire the markup but not render the image.
Fix it at the plan gate
Jules shows a plan before it touches anything. That's your one clean chance to scope the change to the head and manifest and rule out invented filenames.
It runs in a cloud VM
Jules works from a clone of your repo, so a source logo it needs should be committed, and its result comes back as a PR to review rather than a live site.
URL finder for Jules
Paste your Jules preview link or production domain. We'll grab every favicon, let you choose one, and push it back to the generator.
Paste a domain and tap Scan to see every icon we can harvest.
We will open the generator with your selected favicon pre-loaded as the base image.
Playbook
Follow these beats whenever your builder regenerates UI so favicon coverage stays ahead of AI edits.
1Commit the source or the files
Add the exported kit, or commit the source logo, so the cloud VM has it. Jules won't produce the binaries and shouldn't be asked to fetch them from a prompt.
2Approve a scoped plan
When Jules proposes its plan, check it references the icons you provided and edits only the head and manifest. Tighten it before approving, not after the PR lands.
3Review the PR
Open the PR and confirm the .ico and .png files are in the diff alongside the markup, then load the deployed page in a private window.
Checklist
Drop this straight into your deployment doc.
Use the plan-approval step to scope the change and forbid invented icon files.
Confirm the image binaries are in the PR, not just the link tags.
Commit the source image so the VM isn't relying on a URL from the prompt.
Jules favicon FAQ
Can Jules generate the favicon image?
No. Jules edits files and runs commands in a cloud VM but can't render image bytes. Provide the icons (committed to the repo) and let Jules wire the head and manifest and open the PR.
How do I keep Jules from inventing icon files?
Use the plan gate. Before Jules executes, it shows what it intends to do; approve it only once the plan references the real files you committed and scopes the edit to the head and manifest.
Why is the icon missing after Jules' PR merged?
Check the PR included the image files, not only the markup. Because Jules works from a repo clone, a source that lived only in the prompt, or binaries hit by an ignore rule, leaves the tags pointing at files that were never committed.
Jules install guide
Add /jules/favicon-install to project README files, onboarding docs, and launch checklists so nobody skips the favicon step.