Utility AI model (which model runs background AI features)
Omniscio runs a small fast AI model in the background for dozens of minor jobs that do not need a full coding session, from session titles and suggestions to daily digests, summaries, and text correction. Out of the box that model is Luna, and adding your own DeepSeek API key silently routes all of that background work through your key instead.
On this page
What it is
Omniscio uses a small, fast AI model in the background for dozens of minor tasks that don't need a full coding session: generating session titles, drafting suggestions, writing daily digests and weekly summaries, summarising articles and meetings, correcting text, and more. This background workhorse is the Utility AI model (sometimes called the cheap/utility model internally).
Where to find it
The global picker sits at Settings → Sessions → advanced → Utility AI model, where you pick any model from a list or leave it on Automatic. The same advanced panel carries a Per-feature AI models section, so a single feature can be pointed at its own model without changing the rest.
How it behaves
The automatic default — Luna
Out of the box the Utility AI model is Luna (OpenAI's model served via OpenRouter), billed through Omniscio's own gateway. DeepSeek is never used for these helpers, even if you have saved a DeepSeek API key: they summarize email, calendar events and documents, and Google's rules for its user data do not allow sending that to DeepSeek. Your DeepSeek key still works for DeepSeek coding sessions (while no Google account is connected).
Global override
If you want to use a different model for ALL utility features — for example, a faster or cheaper alternative you have access to — set it in:
Settings → Sessions → advanced → Utility AI model
Pick any model from the list (DeepSeek models are not offered). Choosing Automatic (the default) restores Luna.
Per-feature overrides
The same advanced panel shows a Per-feature AI models section where you can pick a different model for one specific feature without changing the rest. The features with individual pickers are:
| Feature | Setting |
|---|---|
| Daily digest | dailyDigestModel |
| Weekly summary (Map + Verify steps) | weeklySummaryModel |
| Article reader | articleReaderModel |
| KMS / knowledge-vault summaries | kmsSummaryModel |
| Meeting summaries | meetingSummaryModel |
| Mind-map generation | mindmapModel |
| Supermail digest | supermailSummaryModel |
| Text correction | textCorrectionModel |
| Reply suggestions | replySuggestionModel |
| AI suggestions | aiSuggestionModel |
Setting any per-feature picker to Automatic (its default) means "use whatever the global setting resolves to" — it inherits from the global override, or Luna.
Precedence, from highest to lowest
- Per-feature explicit pick — a non-Automatic choice here wins everything.
- Global override — a non-Automatic global setting wins for all features that haven't set their own pick.
- Luna — the company-funded fallback when nothing above applies.
A DeepSeek model saved in either picker before this rule existed is ignored.
What this does NOT affect
- Coding sessions — the model a session's Claude agent uses is set per-session (provider, model picker in the new-session bar). The Utility AI model only covers background, sub-second calls, not full interactive sessions.
- Weekly summary Reduce step — that step always runs on Opus 4.7 because synthesis quality matters there. Map and Verify follow the utility model setting.
- Ask Omniscio — the Ask panel has its own model selection.
Related
Who pays for a non-Claude coding session, and which company serves it, is on Who pays & who serves — a separate thing from this utility model — and the wider provider list is on AI providers. Your own keys, including the DeepSeek key that triggers the automatic swap, are managed on API keys, and a provider of your own is set up on Custom providers.
Last verified 2026-09-28