Settings reference

Settings opens as a dialog over your workspace — you do not navigate away, and closing it puts you back exactly where you were. Open it from the foot of the navigation rail or from the top bar. The dialog can be dragged by its title bar.

It reopens on the section you used last.

Sections come in two groups: the first four belong to you and follow you between projects; the group headed Project belongs to the project that is open.

UI Style

Appearance. Light or dark, and default or compact spacing — the two combine, so dark + compact is a valid choice. Interface font and content font are picked separately, so the text you read can be set apart from the text you navigate by.

Zoom scales the whole interface, with a reset next to it. In the desktop application this is the browser engine's own zoom; in a browser or an installed web app it is applied with CSS instead. Either way it is stored per device rather than with your other preferences — a comfortable size on a laptop is the wrong size on a monitor.

LLM Providers

The chat models Zero can reach. Providers are listed down the left, grouped: cloud vendors first, then Your servers — anything you run yourself. The heading only appears when there is something to separate.

The selected provider has two tabs, and the tab you were on survives switching provider:

• Models — which of that provider's models appear in your pickers. Nothing is offered until you enable it. Search, filter by family and sort across the list; each row carries the model's description, family, release date, capability tags and a cost indicator, with one Latest badge per provider. Superseded models are folded into a collapsible Older versions block rather than deleted — a chat that used one still names it.

• API Keys — the keys for this provider. Several can be stored; exactly one is active. Each row shows when it was added, when it was last used, and a Check key button that asks the vendor whether the key is still good.

  The verdict has three states, not two. "Not checked" covers both never checked and could not tell — a timeout or a rate limit is not evidence that a key is bad, and marking a working key red because the network was down is the worst of the available mistakes.

A provider that needs no key — a server of your own — has no key section at all, and is ready as soon as it answers. See Connect an LLM provider.

Integrations

Credentials for services that are not chat models — image, video and speech generation, transcription, web search.

Laid out like LLM Providers: services down the left, the selected one on the right, behind a Credentials tab. Each service declares its own fields, so some want a single key and others a pair.

The services themselves — what each one can do, and which models it offers — are browsed in the Integrations tab opened from the nav rail. This section is only where their credentials live. See Integrations and generation.

Chats

What a new chat starts with: the provider and model it opens on, and the model options that go with them.

The options are built from the model you pick rather than being a fixed form, so what you see here is what a chat with that model will show, with that model's real limits. See Chats for what the individual knobs mean.

Individual chats can override all of this without changing it.

About

Version, build number, commit and commit date. This is what to quote in a bug report.

Anything the packaging did not fill in is left out rather than shown as a zero or an invalid date — a build made straight from source honestly shows only its version.

Project → Project

The open project's name and the folder it lives in, plus its picture: upload a file, or pick one already in the project's assets.

The picture is stored inside the project, resized and re-encoded on the way in. It travels with the folder — into git, onto another machine — rather than belonging to the computer that chose it. It shows on the launcher tile, in the top bar, and here.

Project → Sources

External folders attached to this project. Each row shows the path as configured, the path it resolved to on this machine, and your local override if you set one. See Files, documents and sources.

Project → Assets

Files registered in the project. Import a copy, register a file in place without copying it, repoint an asset whose file moved, or remove the record.

Removing the record leaves the file on disk.

Project → Project Health

What is currently inconsistent in the project, and the buttons that fix it. Empty is the normal state. See When something goes wrong.

Where these are stored

Appearance, providers, keys and chat defaults belong to you and live in your operating system's application-data folder, so they follow you to every project you open on this machine. Zoom is the exception: it is per device.

The project name, picture, sources, assets and health belong to the project and live in it.