Aider favicon install runbook
Aider is a terminal pair-programmer that lives in git: every edit it makes becomes its own commit, worked out from a map of your repo. That makes the favicon wiring clean and reviewable, but Aider only edits text, and images aren't text. Add the real icon files yourself, then let Aider write the head, the manifest, and the commit around them.
It edits text, you supply the images
Aider will never author a PNG or ICO. Generate the kit and place the files first; adding them with /add is what tells Aider they exist.
Every edit is a commit
Aider auto-commits each change, so the head markup lands in git cleanly. But the binary icons are staged by you, not the model. Watch that they make it into the same history.
URL finder for Aider
Paste your Aider 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.
1Generate and drop in the files
Export the full set into your static directory before you start, so the files are on disk when Aider maps the repo.
2Point Aider at the markup files
Use /add on the HTML head, layout, or manifest, then ask it to reference the icons you placed, following the repo's existing convention.
3Confirm the icons are in git too
Aider commits its text edits automatically; run git status afterwards to be sure the image files were staged and aren't sitting untracked next to a commit that references them.
Checklist
Drop this straight into your deployment doc.
Stage the icon files yourself. Aider's auto-commit covers its own edits, not binaries you dropped in.
Note in a CONVENTIONS.md that icons are generated assets, so Aider leaves them alone on later runs.
Check the auto-commit's diff references only files that exist, then load the page in a private window.
Aider favicon FAQ
Can Aider make a favicon?
No. Aider is a code editor driven by an LLM, so it edits text files and commits them, but it cannot render image bytes. Generate the icons with a real tool, add them with /add, and let Aider handle the head and manifest.
Did Aider commit my icon files?
It commits the text edits it makes automatically, but image files you placed by hand are only committed if they were staged. Run git status after the session. Untracked icons next to a commit that references them is the most common reason a deploy still shows the default.
Where should the files go?
Wherever your framework serves static assets: public/ for Vite and most SPAs, the app directory for Next.js App Router icon conventions. Aider can read the repo map and tell you which applies, then write the links to match.
Aider install guide
Add /aider/favicon-install to project README files, onboarding docs, and launch checklists so nobody skips the favicon step.