---
title: Cline Favicon Install Guide
description: Add a favicon with Cline: plan the wiring in Plan mode, connect a generator from the MCP marketplace for the bytes, then approve the head and manifest edits in Act mode.
canonical: https://favicontools.com/cline/favicon-install
---

# Cline Favicon Install Guide

Cline is an open-source agent inside VS Code with two things that suit favicon work: a Plan/Act split, so you agree the wiring before a single file changes, and a built-in MCP marketplace, so you can give it a tool that emits real image files. It approves each write with you. What it won't do is conjure the PNG bytes itself.

## Why it matters

- **Plan before it touches files** — Use Plan mode to have Cline lay out exactly which files it will edit and how, then switch to Act. It's the cheapest way to catch a wrong path before it's written.
- **Get the bytes from MCP** — Cline ships an MCP marketplace. Add a favicon generator as a server and it can request a real icon set and receive actual files, the one step the model can't do alone.

## Playbook

1. **Line up the files** — Connect a generator over MCP, or drop an exported kit into the project first, so Cline is wiring around files that exist rather than inventing filenames.
2. **Agree the plan** — In Plan mode, have it enumerate the head and manifest edits and the exact paths. Approve only once the filenames match what's on disk.
3. **Act, approving each write** — Switch to Act and approve the edits, then have Cline request each icon path against the dev server to confirm a 200 and an image content type.

## Checklist

- Record the icon convention in a .clinerules file so later sessions don't re-add a starter favicon.
- If you wired a generator over MCP, note the server so regenerating is one instruction.
- Confirm the manifest icons array matches the filenames and sizes that shipped.

## FAQ

### Can Cline make a favicon?

It can wire every line of markup and, via MCP, drive a tool that produces the files. But the model itself can't emit image bytes. Give it a generator over MCP or place the files yourself, and let Cline handle the wiring and verification.

### Why use Plan mode for something this small?

Because the common favicon failure is a link tag pointing at a filename that was never created. Plan mode surfaces the exact paths Cline intends to write before it writes them, so you catch the mismatch for free.

### Where should the files go?

public/ for Vite and most SPAs, the app directory for Next.js App Router icon conventions, with favicon.ico at the root. Cline can read the repo and confirm which convention applies before it wires the tags.