# docs/user/project-settings.md · screen/t3code-personal

[View on GitCafe](https://git.cafe/screen/t3code-personal/blob/bf40fa786c521b552eb554bbd4f2c75c4123cd03/docs/user/project-settings.md)

Repository: [screen/t3code-personal](https://git.cafe/screen/t3code-personal)

Visibility: public

Requested revision: bf40fa786c521b552eb554bbd4f2c75c4123cd03

Requested commit: bf40fa786c521b552eb554bbd4f2c75c4123cd03

Commit: bf40fa786c521b552eb554bbd4f2c75c4123cd03

Blob: 604de45258b09086490bf03639584a5d89abe952

Size: 1478 bytes

[Immutable source](https://git.cafe/screen/t3code-personal/blob/bf40fa786c521b552eb554bbd4f2c75c4123cd03/docs/user/project-settings.md?format=markdown)

```
# Customize a project icon

T3 Code selects a project icon automatically. It checks `t3.json`, common favicon and app icon
paths, and icon links in project HTML files. If it does not find an image, it chooses a built-in
icon from the saved project name. In web and desktop, this icon stays the same when the sidebar
shows a repository label such as `owner/repo`.

To choose a different icon or emoji:

1. Open **Settings** and select **Projects**.
2. Select the project.
3. Next to **Project icon**, select **Choose icon**.
4. Search the full Lucide icon set and choose a color, or switch to **Emoji** and choose or paste
   an emoji.

To use an image from the project instead, select **Choose file**, search for an image, and select
it.

T3 Code supports SVG, PNG, ICO, JPEG, GIF, AVIF, and WebP files. The selected path applies to
each checkout in the project group and appears on your connected clients.

To use automatic detection again, select **Automatic**.

## Keep the default branch current

Turn on **Automatically pull** in a project's settings to keep its default-branch checkout current.
T3 Code checks in the background and when the server starts. It uses the branch's configured
upstream and only performs a fast-forward pull when the checkout has no working-tree changes,
untracked files, or local commits.

The pull is skipped if the checkout is on another branch, has no upstream, or contains local work.
Pull failures do not prevent the server from starting.

```