# More settings (A)

Detailed reference for every setting whose key begins with the letter A, covering display options, agent controls, alarms, alternative AI providers, automations, and more.

## Accounts classic layout {#accountsClassicLayout}

Switches the Accounts settings page back to the previous flat provider list instead of the newer grouped "Other AI tools" layout. Turn this on if you prefer the simpler, single-column view of all configured providers. Off by default; the grouped layout is the current standard. No restart required.

## Agent inbox alerts {#agentAlertsEnabled}

When on (the default), sessions can drop a persistent row into your inbox by calling `POST /alert` on the local CLI control server. This is how agents surface status updates, completion notices, or anything they want you to see without stopping to ask. Turn it off to refuse cards posted from outside the app: an agent's `POST /alert` answers 403 and a plugin's card is not posted, while the agents themselves keep running. The cards Omniscio raises for itself — a failed backup, an account to sign in to again — are never affected.

## Update alerts for Claude Code and Codex {#agentCliUpdateAlertsEnabled}

When on (the default), Omniscio checks about every six hours whether Claude Code or Codex CLI has fallen behind its latest release and, if so, puts one card per tool in your inbox naming the installed and latest versions. The card's **Update now** button runs that tool's own updater in a terminal window on your computer — from your phone, it runs on the computer — and the card clears by itself once the tool is current. Each new version is announced once; a card you dismiss stays quiet until a newer version appears. Omniscio never updates Claude Code or Codex on its own. Turn it off to stop new cards; you can still update either tool any time from the Toolchain tools list.

## Update alerts for your other tools {#otherToolUpdateAlertsEnabled}

When on (the default), Omniscio checks about every six hours whether any of your other recommended tools — Git, GitHub CLI, OpenCode, Pi, Portless, Agent Browser, pnpm, yt-dlp, Bun, gws, kubectl, RTK, and gog, plus Playwright, AgentMail and Repomix while Auto-update Tools is off — has fallen behind its latest release and, if so, puts one card per tool in your inbox naming the installed and latest versions. The card's **Update now** button runs that tool's own updater in a terminal window on your computer, the same as the Toolchain tools list's Update button. RTK and gog are installed by hand, so their card says so and its button opens that tool's download page instead. Each new version is announced once; a card you dismiss stays quiet until a newer version appears. This switch is separate from the Update alerts for Claude Code and Codex switch above — turning either off leaves the other exactly as it was. Turn it off to stop new cards for these tools; you can still check for and update them any time from the Toolchain tools list.

## Max concurrent agent-driven sessions {#agentDrivenMaxConcurrent}

A global cap on how many agent-driven (externally scripted) sessions may run at the same time. Once this count is reached, any additional spawn request is refused until one finishes. Range: 1–10 — there is no "unlimited" value, so the highest you can set is 10. Applies only to sessions started by external scripts via the CLI; sessions you start yourself are not counted.

## Max dollars per agent-driven session {#agentDrivenMaxDollarsPerSession}

A USD ceiling for a single agent-driven session. **Not enforced today:** Omniscio stores this value and shows it back to you, but nothing stops a session when its cost reaches it, so treat it as a note to yourself rather than a brake. Range: 0.01–20 — there is no "no limit" value, so the loosest you can set is $20. The concurrent-sessions cap below *is* enforced; this one is not.

## Max turns per agent-driven session {#agentDrivenMaxTurnsPerSession}

A ceiling on the number of follow-up turns an agent-driven session may take. **Not enforced today:** Omniscio stores this value and shows it back to you, but nothing stops a session when it reaches the count, so treat it as a note to yourself rather than a brake. Range: 1–200 — there is no "unlimited" value, so the highest you can set is 200. The concurrent-sessions cap below *is* enforced; this one is not.

## Allow agents to ask you for a value {#agentInputRequestsEnabled}

When on (the default), a blocked session can pop a labeled modal asking you to fill in a value it must never store itself — most often an API key. You type the value, press Enter, and it goes straight to the proper Settings field; the agent never sees what you typed, only that the request was filled or cancelled. Turn this off to refuse all agent-triggered input prompts; the `/input-request` route returns `403` and the session must handle the refusal on its own.

## Agent instructions sync — canonical file {#agentInstructionsSyncCanonical}

Which file Omniscio treats as the source of truth when syncing agent instructions to other tools. `CLAUDE.md` is the default. Switch to `AGENTS.md` if that is your primary file. The file you pick is never written as a mirror target — only the other tools get copies. Only relevant when the Agent Instructions Sync feature is on.

## Agent instructions sync — git handling {#agentInstructionsSyncGitMode}

Controls whether the generated mirror files are tracked in git. `local` (default) keeps the copies out of git to avoid merge conflicts — useful when only you use the repo. `committed` adds them to the repo so teammates who use other AI tools (Codex, Cursor, Copilot, etc.) pick them up automatically. Switch between the two at any time; only newly written files are affected.

## Agent instructions sync — mirror targets {#agentInstructionsSyncMirrors}

The list of agent-instruction filenames to keep in sync alongside your canonical file. Accepted targets: `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, `.cursorrules`, `.clinerules/base.md`, `.github/copilot-instructions.md`, `.windsurfrules`. Each checked target gets an up-to-date copy of your canonical file every time it changes. The canonical file itself never appears in this list.

## Which model each agent tier uses {#agentModelTiers}

Your preferred Claude model for each of the four agent-facing tiers — genius, smart, worker, and basic. When an agent spawns another session it asks for a tier ("worker") rather than naming a model itself, and Omniscio looks the real model up here. That is deliberate: an agent's memory of model names is frozen at its training cutoff, so a model id it half-remembers can be wrong or unlicensed and the spawn then dies. Leave a tier unset and it uses the built-in default for that tier. Setting one here changes every future spawn that asks for it. Settings → Sessions → “Models agents may pick”.

## Short share links by default {#agentShortLinkDefault}

When on (the default), agents that publish a share are told to prefer the short `omnisc.io` link format and pass `shortLink: true` in their publish call. This only takes effect if your account holds the `custom_share_url` paid entitlement — the server enforces eligibility, so the setting is harmless on a free plan. Turn it off to stop agents defaulting to short links even on a paid plan. Your own in-app publish dialog is not affected.

## Alarm NLP daily cost cap {#alarmNlpDailyCostCap}

The maximum amount (in USD) that Omniscio may spend per day on AI-assisted natural-language alarm parsing — the Haiku calls that understand phrases like "remind me at 3:30 next Tuesday" instead of requiring a rigid date picker. Once the cap is reached for the day, the NLP parser pauses and only exact-format times are accepted until midnight. Range: 0–5, and the cap is checked as "spent so far ≥ cap", so **0 does not mean unlimited — it means never**: at zero the cap is already reached on the first request of the day, and the parser is off entirely until you raise it. 0.1 (the default) is the tightest useful setting; raise it to spend more.

## Bring app to foreground on alarm {#alarmsBringToForeground}

When on, Omniscio pops its window above all other apps the moment an alarm fires, so you can't miss it. When off, the alarm notification still appears (as a modal, banner, or silent banner depending on your assertiveness setting) but the app stays wherever it is. On by default; turn it off if you would rather your current window were left alone.

## Snooze cap {#alarmsDefaultMaxSnoozes}

The maximum number of times any alarm can be snoozed before only the Dismiss button remains. Set it to -1 for unlimited snoozes. Range: -1–20. Default is unlimited (-1). Raising it to a low number (like 3) helps prevent indefinitely snoozing an alarm you keep meaning to deal with.

## Default snooze length {#alarmsDefaultSnoozeMinutes}

How long a snooze lasts when you tap Snooze on a firing alarm. Accepted values: 5, 9, 15, or 30 minutes. Default is 9. You can still override the snooze length on individual alarms; this setting controls what the Snooze button does without a choice.

## Default alarm sound {#alarmsDefaultSound}

The sound file played when an alarm fires. Enter the filename or path of the audio file you want to use. Leave it blank to use the built-in default chime. Only applies when a per-alarm sound override is not set.

## Default alarm sound duration {#alarmsDefaultSoundDurationSeconds}

How many seconds the alarm sound plays before it stops automatically. Set to -1 to let the sound play in full without cutting it off. Range: -1–300. When the play mode is set to loop, this cap still applies and stops the loop after the configured duration.

## Default alarm sound fade-in {#alarmsDefaultSoundFadeInSeconds}

How many seconds the alarm volume takes to ramp from silent to full when it starts playing — a gradual crescendo instead of a sudden blare. Set to 0 for no fade-in (the sound starts at full volume). Range: 0–300. Useful for a gentler wake-up experience.

## Default alarm sound play mode {#alarmsDefaultSoundPlayMode}

Whether the alarm sound plays once and stops, or loops continuously until you dismiss or snooze. `once` plays it a single time; `loop` keeps repeating it. Default is `loop` — the alarm keeps sounding until you act, stopped by the duration cap above. Choose `once` if you would rather hear the chime a single time.

## Speak alarm label {#alarmsDefaultSpeakLabel}

When on, the alarm reads its own label aloud (using text-to-speech) the moment it fires, so you know what it's about without looking at the screen. Useful for accessibility or for use while away from your desk. Off by default.

## Enable alarms {#alarmsEnabled}

Master switch for the Alarms feature. When on, scheduled alarms fire at their set times with sounds, notifications, and any foreground or focus-pierce behavior you have configured. Turn it off to silence all alarms without deleting them; they resume firing when you turn it back on.

## Max ringing time {#alarmsMaxRingingMinutes}

How many minutes an alarm can ring before Omniscio automatically dismisses it to your inbox. Once this limit is reached the alarm stops ringing and leaves an inbox row you can review later. Range: 1–60 minutes. Prevents an alarm from ringing indefinitely if you step away.

## Pierce Focus Mode {#alarmsPierceFocusMode}

When on, alarms fire immediately even if Focus Mode is active and batching notifications. This lets urgent reminders break through without waiting for a focus-period to end. When off, alarms are held with other notifications until the current focus batch releases. On by default; turn it off if you would rather alarms respect Focus Mode's batching.

## Default project for sessions started from an alert {#alertSessionDefaultProjectId}

Which project a new session opens in when you start one straight from an inbox alert (and from the drip and "start a session" dialogs that share the same default). Leave it on Automatic and Omniscio picks this install's own repo hub when it has one, otherwise your Claude folder. A card that already remembers its own repo always wins over this. If the project you picked is later removed or can't host a session, the choice is quietly ignored rather than breaking the launch.

## Allow Anti-Gravity sessions in any project {#allowAntigravitySessionSpawn}

Opt-in toggle that lets you start Anti-Gravity (Google's Gemini-backed coding CLI) sessions across all your projects from the new-session menu. Off by default — no Anti-Gravity sessions can be started until you turn this on and configure the Anti-Gravity CLI. Changing it takes effect immediately.

## Allow Codex sessions in any project {#allowCodexSessionSpawn}

Opt-in toggle that lets you start OpenAI Codex CLI sessions across all your projects. Off by default. You also need the Codex CLI installed and an OpenAI API key saved before sessions will actually work. Turn it on to add Codex to the provider menu.

## Allow Cursor sessions in any project {#allowCursorSessionSpawn}

Opt-in toggle that lets you start Cursor (`cursor-agent` CLI) sessions from the new-session menu in any project. Off by default; requires the Cursor CLI on your PATH and a Cursor API key. Turn it on to expose Cursor as a selectable provider.

## Allow DeepSeek sessions in any project {#allowDeepseekSessionSpawn}

Opt-in toggle to expose DeepSeek (via its Anthropic-compatible API endpoint) as a provider in the new-session menu. Off by default. You need a DeepSeek API key saved in Settings → Accounts before sessions will run. Turn it on to add DeepSeek to your provider list.

## Allow Devin sessions in any project {#allowDevinSessionSpawn}

Opt-in toggle to expose Devin (Cognition's autonomous software-engineer API) as a provider in the new-session menu across all projects. Off by default; requires a Devin API key. Turn it on to be able to start Devin sessions from within Omniscio.

## Allow Gemini sessions in any project {#allowGeminiSessionSpawn}

Opt-in toggle that lets you start Gemini CLI sessions across all your projects. Off by default. You also need the Gemini CLI installed (`npm install -g @google/gemini-cli`) and a Gemini API key configured. Turn it on to add Gemini to your new-session provider options.

## Allow GLM sessions in any project {#allowGlmSessionSpawn}

Opt-in toggle to expose GLM (Zhipu z.ai's Anthropic-compatible API) as a session provider in the new-session menu. Off by default; requires a GLM API key saved in Settings → Accounts. Turn it on to add GLM to your available providers.

## Allow Grok sessions in any project {#allowGrokSessionSpawn}

Opt-in toggle to expose Grok Build (xAI's coding CLI) as a provider in the new-session menu. Off by default; requires the `grok` CLI installed and an xAI API key. Turn it on to start Grok sessions from within Omniscio.

## Allow Hermes sessions in any project {#allowHermesSessionSpawn}

Opt-in toggle to expose Hermes (Nous Research's local model CLI) as a provider in the new-session menu. Off by default; requires the Hermes CLI on your PATH and a model set up via `hermes setup`. Turn it on to add Hermes to your provider list.

## Allow Kimi sessions in any project {#allowKimiSessionSpawn}

Opt-in toggle to expose Kimi (Moonshot's Anthropic-compatible API) as a session provider in the new-session menu. Off by default; requires a Kimi API key saved in Settings → Accounts. Turn it on to add Kimi to your available providers.

## Allow Kimi Code sessions in any project {#allowKimicodeSessionSpawn}

Opt-in toggle to expose Kimi Code (Moonshot's own ACP coding CLI, separate from the Kimi API) as a provider in the new-session menu. Off by default; requires the `kimi` CLI installed and authenticated via `kimi login`. Turn it on to start Kimi Code sessions from within Omniscio.

## Allow MiniMax sessions in any project {#allowMinimaxSessionSpawn}

Opt-in toggle to expose MiniMax (Anthropic-compatible API) as a session provider in the new-session menu. Off by default; requires a MiniMax API key saved in Settings → Accounts. Turn it on to add MiniMax to your available providers.

## Allow OpenCode sessions in any project {#allowOpencodeSessionSpawn}

Opt-in toggle to expose OpenCode as a provider in the new-session menu across all projects. Off by default; requires the OpenCode CLI on your PATH. Turn it on to be able to pick OpenCode when starting a new session.

## Allow OpenRouter sessions in any project {#allowOpenrouterSessionSpawn}

Opt-in toggle to expose OpenRouter as a provider in the new-session menu across all projects, so you can start coding sessions on OpenRouter instead of Claude. Sessions reuse the same Claude command line, redirected to OpenRouter's Anthropic-compatible endpoint — the “connect with OpenRouter, no account needed” path offered during setup. Off by default, like the other vendor spawn toggles. It is switched on for you when you connect with OpenRouter during onboarding or from Settings → Accounts, and it reuses the same OpenRouter key that powers Omniscio's built-in AI helpers — one key, no second account to set up.

## Allow Pi sessions in any project {#allowPiSessionSpawn}

Opt-in toggle to expose Pi (Earendil's coding agent, installed via `npm i -g @earendil-works/pi-coding-agent`) as a provider in the new-session menu. Off by default. Turn it on to start Pi sessions from within Omniscio.

## Allow Qwen sessions in any project {#allowQwenSessionSpawn}

Opt-in toggle to expose Qwen (Alibaba's Anthropic-compatible DashScope API) as a session provider in the new-session menu. Off by default; requires a Qwen (DashScope) API key saved in Settings → Accounts. Turn it on to add Qwen to your available providers.

## Allow unverified plugin backends {#allowUnverifiedPluginBackends}

When on, third-party plugins installed from the marketplace are permitted to run a backend process with full system access. Off by default — this is a security-sensitive setting because a plugin's backend code runs with your OS permissions. Only enable it if you trust the plugins you install from the marketplace. Verified (first-party) plugins are unaffected by this toggle.

## Always use my default start config {#alwaysUseDefaultStartConfig}

When on, the tool/model/thinking picker that normally appears when you open a new session is hidden, and every session starts with your saved defaults immediately. You can still change the model for a single session before you send its first message. Turn it on to streamline session creation when you almost always want the same setup.

## Make sessions Omniscio-aware {#amcAwarenessPromptEnabled}

When on, a short note is silently added to every session's system prompt telling the agent that it is running inside Omniscio and explaining how to reach its local control server (CLI routes, alert posting, and so on). This allows capable agents to surface results in your inbox, publish shares, or request input — features they can't use if they don't know the app is there. On by default; turn it off to keep the note out of every session's system prompt.

## Anti-Gravity virtual project {#antigravityProjectEnabled}

Adds a dedicated Anti-Gravity virtual project to the sidebar, giving you a fixed place to launch and track Anti-Gravity sessions without them mixing into your other projects. Off by default; requires the Anti-Gravity CLI and `allowAntigravitySessionSpawn` to be on. Turn it on once Anti-Gravity is set up to keep your Anti-Gravity work organized.

## Archive digest cadence {#archiveDigestCadence}

How often Supermail automatically posts an "Archive Insights" digest to your inbox — a periodic AI summary of the senders whose emails you archive without reading, with suggestions for cleanup. Options: `off`, `daily`, or `weekly` (default weekly). You can always run an on-demand analysis inside Archive Insights regardless of this schedule; set it to `off` to stop the automatic posts entirely.

## Article Reader model {#articleReaderModel}

Which AI model is used to summarize articles you save in the Article Reader. `Automatic` (the default) inherits your global Utility AI model choice. Enter a specific model ID to override it for article summaries only. Found under Settings → Sessions → Per-feature AI models. Leave it on Automatic unless you want article summaries to use a different model than the rest of your utility tasks.

## Aside cost cap (USD) {#asideCostCapUsd}

The maximum amount in USD that a single "aside" (a side-question spawned via Ctrl+B) is allowed to spend. If an aside is estimated to exceed this cap before it starts, it is aborted instead of launched. Range: 0–50. Leave it unset or at 0 for no cap. Useful for keeping quick side-questions cheap even when your main sessions are running expensive models.

## Ask Omniscio (in-app help agent) {#askAmcEnabled}

When on, an "Ask Omniscio" virtual project appears in your sidebar — a friendly help agent pre-loaded with the Omniscio documentation and live app state. Ask it how to configure anything, what a setting does, or how to use a feature. On by default; turn it off to remove the tutor from your sidebar.

## Plain-language replies {#audienceStylePromptEnabled}

On by default. Adds a short instruction to every regular session telling the agent to write for a smart non-expert — plain everyday words instead of jargon or unexplained acronyms, start brief and add depth only if you ask, and clean scannable markdown that leads with the answer, uses clear headers and keeps bullets to one short idea each instead of walls of text. It is what keeps a fresh install from sounding verbose and developer-toned out of the box. Turn it off if you would rather agents write in their own default, more technical voice; nothing else about how they work changes. Settings → Features.

## Auth pathway {#authPathway}

Controls how native Claude sessions are credentialed. Three strictly isolated modes: `managed` (default) uses the pool of signed-in Anthropic OAuth accounts and saved API keys, with automatic load-balancing and failover; `apiKeyOnly` routes all sessions through your own Anthropic API key in a private slot; `passthrough` uses the credential from your own `claude login` terminal session stored in `~/.claude` (Omniscio stores nothing). Set via the pathway picker during onboarding or in Settings → Accounts. Switching modes takes effect on the next session you start.

## Auto-switch account on rate limit {#autoAccountSwitch}

When on, Omniscio automatically switches to another configured account if the current one hits a rate limit, rather than waiting for the limit to reset. This keeps sessions running smoothly when you have multiple Anthropic accounts in the managed pool. Off means sessions wait out the rate limit on their current account. Off by default since 2026-08-29 (fresh installs run a single account; earlier installs keep the setting they had). Only applies in `managed` auth pathway mode.

## Auto-capitalize Team Chat {#autoCapitalizeTeamChat}

When on (the default), the Team Chat message composer automatically capitalizes as you type — the first word, the start of each sentence (after `.` `!` `?`), and the beginning of each new paragraph — while skipping URLs, file paths, and abbreviations. This is a free, local transform; it never calls the AI and never costs anything. Turn it off if you prefer to control your own capitalization in chat.

## Apply updates automatically when idle {#autoInstallWhenIdle}

When on and an update has downloaded and is waiting to be installed, Omniscio applies it and restarts automatically — but only when no sessions are currently running and your computer has been genuinely idle. Off by default: without this toggle, Omniscio shows a nudge and waits for you to choose when to install. Turn it on for fully unattended updates during quiet periods.

## Auto-lander repos {#autoLanderRepos}

Per-repo configuration list for the in-source auto-lander feature. **Which repos get landed comes from your Dev Pipeline repo selection** — this list adds per-repo options on top of it: pausing one repo, setting the integration (target) branch it lands into, or turning on a dry-run mode that logs what would land without actually doing it. Adding an entry never removes a repo from the set, and an entry here does not add a repo your Dev Pipeline has turned off. To stop landing in one repo, turn it off in the Dev Pipeline panel; to stop landing everywhere, empty this list. The auto-lander master switch (`autoLanderEnabled`) must also be on.

## Auto Model Router {#autoModelRouterEnabled}

Master switch for the Auto Model Router. When on, each new session picks its AI model automatically based on the task — using your routing rules, task complexity, and keyword signals — instead of always defaulting to your global default model. Off by default: nothing changes until you turn it on. Manage your routing rules in Settings → Model Routing.

## Model routing rules {#autoModelRoutes}

Your personal list of routing rules for the Auto Model Router. Each rule maps a task description (plain English "when to use" text, plus optional fast-match keywords) to a specific provider and model. New sessions matching a rule start with that model automatically. Rules are evaluated in order; the first match wins. Only active when `autoModelRouterEnabled` is on. Add, edit, and reorder rules in Settings → Model Routing.

## Preview AI auto-replies before sending {#autoRespondPreviewBeforeSend}

When on (the default), an AI-written auto-reply generated by a channel automation is held as an approve/reject card in your inbox instead of being sent immediately. You see the exact reply text and where it will go before it reaches the recipient — protecting against a malicious incoming message tricking the AI into sending something harmful. Approve to send it or reject to drop it. Turn it off to send AI-written replies immediately without review. Plain template replies always send immediately regardless of this setting.

## Auto-update tools {#autoUpdateTools}

When on, Omniscio silently updates bundled tools in the background — Claude Code, Playwright, AgentMail, and Repomix — whenever new versions are available, without interrupting you. Git and GitHub CLI receive a notification instead of a silent update (they require more care). Off by default; turn it on to let Omniscio update them for you. Either way you are notified when updates are available.

## Auto-wait period {#autoWaitMinutes}

How many minutes Omniscio lets a waiting session run silently before surfacing it to your inbox as needing attention. This single knob governs the prose-wait cap, the background-task hold, the "Keep waiting" countdown banner, and every auto-wait notice in the UI. Range: 5–240, default 30. Read internally as `autoWaitMinutes ?? 30` when not set.

## Channel filters (automations) {#automationsEnabled}

Master toggle for the Channel Filters / Automations feature. When on, your configured rules and AI processing run automatically against incoming messages, emails, and other channel events. Turn it off to pause all automated processing without deleting your rules; they will resume when you turn it back on.