# First Run And Setup

The setup flow is responsible for choosing a usable model path without assuming local Ollama is the only option.

## What Setup Probes

Setup can inspect:

- local platform and hardware
- existing Ollama availability
- configured custom endpoints
- OpenAI-compatible endpoint model lists
- optional voice, media, and tool dependencies
- unified-memory hardware constraints

## Model And Endpoint Choice

The model picker should show the union of enabled endpoints. If a sponsor endpoint, OpenRouter endpoint, or other external endpoint is selected, the next model step must list models from that endpoint as well as other toggled enabled endpoints.

The setup flow should not silently fall back to local Ollama when an external endpoint was selected.

## Sponsor Endpoint Banner

The setup banner is separate from consumer-visible sponsor endpoint labeling. Sponsor consumer headers should stay simple: a short sponsor-provided string and optional clickable link.

## Optional Dependency Setup

Optional installers can run before the TUI launches. If elevation is required in a terminal context, the TUI should temporarily clear or suspend its drawing state, present the password prompt directly, consume the password through the normal system elevation path, then restore the TUI state.

## Expected Outcome

After first run:

- an endpoint is selected
- a model is selected
- `.omnius/settings.json` exists if settings were persisted
- `.omnius/` is ignored by git
- the TUI can submit a prompt without re-entering setup