# More settings (H–Q) Plain-language reference for Omniscio settings whose keys begin with the letters H through Q. --- ## How you heard about us {#heardAboutUs} Records the acquisition channel you selected during initial setup ("how did you hear about Omniscio?"). The value is one of the canonical marketing-source options shown in the Setup wizard. It is written once, synced to your cloud profile, and then left alone — you will not be prompted again. This field feeds aggregate marketing reporting; it does not affect any app behavior. If you did not complete the onboarding step it will be absent. --- ## Tips & guidance {#helpfulHintsEnabled} The master switch for Omniscio's coaching cards — the tips, nudges and "did you know" suggestions that appear in your inbox: keyboard and coaching shortcuts, feature suggestions, gentle activity nudges (your inbox is piling up, you keep typing the same phrase, a quick reply is going unused), the weekly recap, reflection prompts, and one-time education cards. **Off by default and opt-in**, so nobody gets any of them out of the box; turn it on and the individual tip toggles underneath decide which ones you see (a tip needs both this and its own switch). Nothing in this class appears while it is off. Real alerts are not affected: a session that needs you, an error, a budget warning, a login problem or a cloud issue always comes through regardless of this setting. ## Hide asides by default {#hideAsidesByDefault} Controls how "aside" conversations (side-questions spawned with Ctrl+B that fork a session) are rendered in the transcript. When on, asides start collapsed to a header chip and you click to expand them. When off (the default), asides render fully expanded inline alongside the main session content. Turn this on if you use asides frequently and find them visually noisy in their expanded form. --- ## Hide repeated auto-wait turns {#hideAutoWaitedUnlessFinal} When enabled, collapses repeated "Auto-waited" turns — the prose-wait and scheduled-wakeup lifecycle rows a session emits while it silently waits for you — into a single expandable one-line marker, keeping only the most recent one visible. Only a message you send starts a new series — a message from another agent or a scheduled wake-up does not, so a coordinating session's routine check-ins fold too. The very first wait turn in a series is never hidden, nor is a turn that carries a user message or one that is still in flight. This is a pure display preference and does not alter what is saved. Off by default; opt in from Settings if your chat views feel cluttered by wait rows. Pairs with the fold-auto-wait-notices option. --- ## Hotkey training mode {#hotkeyTrainingMode} An opt-in training aid that blocks the first click on any control that also has a keyboard shortcut, showing a "Press <key>" coaching bubble at your cursor instead. A second click within about three seconds goes through normally as an escape hatch. This trains you to reach for the keyboard instead of the mouse. Keyboard shortcuts themselves are unaffected, and the mode has no effect on touch-only devices. Off by default. Find it in Settings → Appearance. --- ## Image bridge mode {#imageBridgeMode} Controls whether images you attach to a session are automatically described for text-only AI models. `off` (the default) leaves images unprocessed; `auto` sends attached images to a vision-capable model and injects the generated description into the session context. Use `auto` when you routinely work with text-only providers and need image content to reach the model. Note that `auto` adds an extra model call per image, so it has a small cost. --- ## Model for the first session title {#initialTitleModel} Which AI model writes a session's title the first time one is generated. Leave it on Automatic and Omniscio picks for you — a fast, low-cost model, which runs on your own machine when the on-device title model is available. Only used when session naming is set to AI titles; the separate refresh-title model handles later re-titling. ## Interruptions avoided card {#interruptionsAvoidedEnabled} Shows or hides the "Interruptions Avoided" card in the Statistics → Overview panel. The card displays a running tally of moments Omniscio handled something for you autonomously — self-archived items, automatic reply holds, dev-pipeline auto-approvals — so you were not interrupted. The underlying counting always runs (it is near-free), so toggling this only controls whether the card is visible. Default on. --- ## Omni Briefing — auto-play on open {#jarvisBriefingAutoOnOpen} When on, the Omni Session Briefing is automatically spoken aloud the moment you open a session, without you pressing a button. Requires Omni Briefing to be enabled. Off by default; useful for a hands-free workflow where you want to hear a spoken context summary immediately on focus. Combines with `jarvisBriefingHotkeyEnabled` for manual-trigger use. --- ## Omni Briefing — enabled {#jarvisBriefingEnabled} Master toggle for Omni Session Briefing, a voice-spoken summary of a session's recent context. When on, opening a session gives you the option to hear a spoken recap of recent activity before you type. Off by default. Requires at least one text-to-speech provider to be configured. See also `jarvisBriefingAutoOnOpen` and `jarvisBriefingHotkey`. --- ## Omni Briefing — hotkey {#jarvisBriefingHotkey} The global keyboard shortcut that fires an Omni Briefing on demand (default Ctrl+Shift+J). Accepts a single Electron accelerator string or a list of alternates. Registered only when `jarvisBriefingHotkeyEnabled` is true. Change it in Settings → Hotkeys if it conflicts with another application. --- ## Omni Briefing — hotkey enabled {#jarvisBriefingHotkeyEnabled} Whether the Omni Briefing global hotkey is registered with the OS. On by default once Omni Briefing is enabled. Turn off to stop the hotkey from being claimed globally while still keeping Omni Briefing available via the in-app button. --- ## Omni Briefing — model {#jarvisBriefingModel} The AI model used to generate the spoken briefing script. Defaults to a lightweight OpenRouter-hosted model. You can change this to any model Omniscio can reach if you prefer a different voice or cost profile. Accepts a model-id string up to 100 characters. Setting → Sessions → Per-feature AI models. --- ## JLS Image Studio app panel {#jlsImageStudioAppEnabled} Shows or hides the JLS Image Studio embedded website as a sidebar virtual project (the panel opens the live jls-image-studio.web.app in a webview). Off by default; turn on in Settings → AI Coach. Separate from the Image Studio tool service in Accounts & Providers, whose launch toggle was retired 2026-09-19 (only its API key remains). --- ## JLS Image Studio MCP integration **Retired (2026-09-19).** No AMC-built MCP server composes into a session any more, so the Image Studio launch toggle is gone. The service's API key is still configured in Accounts & Providers and is still read by the Image Studio CLI routes. --- ## Journal {#journalEnabled} Enables the personal journal feature: freeform writing with guided AI reflection modes, gratitude and daily-reflection templates, a problem-solving mode, and an AI mentor for Socratic self-discovery. Entries are synced, searchable, and taggable. Off by default (in-development, gated via the unreleased-feature registry until released). --- ## Key reminders prompt {#keyRemindersPromptEnabled} Controls whether a "Key Reminders" block is injected near your message on every session turn. When on (the default), each turn reminds the agent of the most important habits: assume you can and look harder, believe bug reports, act and prove it with evidence, default to yes, fix root causes, keep it simple, and only ask when it is genuinely your call. Turn off to stop injecting the reminder block. Settings → Sessions → Prompting. --- ## Kimi balance monitor {#kimiBalanceMonitorEnabled} When enabled, Omniscio periodically checks your Kimi (Moonshot) API account balance and raises an inbox alert when it falls below the threshold set in `kimiBalanceThresholdUSD`. Off by default. Requires a Kimi API key stored in Accounts & Providers. Kill switch: `AMC_DISABLE_KIMI_BALANCE_MONITOR`. --- ## Kimi balance alert threshold {#kimiBalanceThresholdUSD} The USD balance level below which a low-balance inbox alert fires for your Kimi (Moonshot) account. A value of `0` disables the alert entirely. Default is $5. Range: $0–$10,000. Only relevant when `kimiBalanceMonitorEnabled` is on. --- ## KMS summary model {#kmsSummaryModel} The AI model used to summarize notes in your Knowledge Vault (KMS). `null` (the default, labeled "Automatic" in the UI) inherits the global Utility AI model. Set a specific model string to override it for KMS summaries only. Advanced option; find it under Settings → Sessions → Per-feature AI models. Synonyms: knowledge vault summary model, note summary model. --- ## Launch on startup {#launchOnStartup} Whether Omniscio starts automatically when you log in to your computer (Electron login item registration). Off by default. Turn on if you want Omniscio running in the background from the moment your machine boots. Toggle in Settings → System. --- ## Load-balancing notices {#loadBalancingNoticeEnabled} Controls the inbox notice that says "your is carrying N active sessions" — raised when one of your Claude logins is carrying far more actively-running sessions than the others AND is climbing toward its usage limit, so you can spread work before you hit a wall. On by default; the card's own "Turn off these notices" button sets this to off. It silences **only the notice**: the load balancing itself keeps working exactly the same either way, so nothing about how your sessions are spread across logins changes. ## Marketplace {#marketplaceEnabled} Shows or hides the Plugin Marketplace virtual project in the sidebar. The Marketplace lets you browse, install, and manage community-built plugins. Off by default for all users (a force-off migration applied 2026-05-26); re-enable in Settings → AI Coach. Turning it off hides the sidebar row but does not uninstall any plugins you have already installed. --- ## Marketplace review queue {#marketplaceReviewEnabled} Shows or hides the Marketplace Review virtual project — an admin queue for reviewing and approving plugin submissions. Off by default; intended for plugin administrators. Re-enable in Settings → Features if you are a marketplace admin. Unrelated to the end-user Marketplace toggle above. --- ## Model for master-debt fixers {#masterDebtFixerModel} Which model the master-debt fixers run on when they clear failures that were already red on master, before your branch's own results are considered. DeepSeek V4.1 Flash is the default — that work is mechanical and highly repeated, so the cheapest capable engine is the right pick. If the engine you choose is not set up on this machine (no key, no access to Omniscio's shared gateway), the fixers quietly fall back to the reporting project's own engine, so a fix never stalls on this choice. --- ## Meeting transcription service {#meetingsSttProvider} Which speech-to-text engine transcribes your meetings. It is deliberately separate from the voice-typing engine, so you can use a different service for each. Defaults to **Local** — the free on-device engine — so meetings transcribe out of the box with no API key and no chance of a surprise bill. Choose a cloud engine (Deepgram, ElevenLabs, Groq, Grok, Gemini or Meta) if you want higher accuracy or better speaker separation; each of those bills **your own key** for that provider, which is exactly why none of them is the default. A meeting has to tell two people apart, and engines differ in how well they do that, so it is worth trying one before committing. ## Meeting summary model {#meetingSummaryModel} The AI model used to summarize meetings. `null` (the default, labeled "Automatic") inherits the global Utility AI model. Override with a specific model string to route meeting summaries to a different provider. Advanced; Settings → Sessions → Per-feature AI models. Synonyms: meeting notes model. --- ## MemPalace {#mempalaceEnabled} Enables the MemPalace episodic memory system, which mines your session history on a background schedule and writes an `.mcp.json` file that gives AI sessions access to your long-term context. Off by default (opt-in). Turn on in Settings → Features once you are comfortable with Omniscio having read access to past sessions for memory extraction. --- ## Mind map model {#mindmapModel} The AI model used to generate mind maps. `null` (the default, labeled "Automatic") inherits the global Utility AI model. Set a specific model string to override it for mind map generation only. Advanced; Settings → Sessions → Per-feature AI models. --- ## Mission Control {#missionControlEnabled} Master gate for the Mission Control project-management integration — the isolated plugin sidebar panel and all its sub-features. Off by default (opt-in / in-development). Turning it on reveals the Mission Control sidebar row, the PM inbox integration, the calendar overlay, and related settings. Turning it off hides all three but leaves your stored configuration intact — flipping it back on restores everything. --- ## Mobile device location {#mobileDeviceLocationEnabled} When on (the default), your phone reports its own coarse location — city, region, and country, resolved from its public IP by a cloud function — so the device-approval card in Omniscio can show where a device is connecting from. Turn off to disable that lookup entirely: the phone makes no geo call and the approval card shows only device and network information. This is a privacy control, not a security gate. --- ## Mobile fast load {#mobileFastLoadEnabled} Makes the Omniscio mobile web app load faster on phones by loading each screen's feature code the first time you open it, instead of pre-loading all of it at boot. **On by default** since 2026-09-24; existing installs were switched on once, and if you turn it off it stays off. When on, the phone parses less JavaScript before the UI mounts. Turn it off to load everything up front — steadier on a patchy connection, where a screen opened for the first time after an update has to wait for its code (on a dropped connection the phone shows "Waiting for your computer…" while it waits). Takes effect on the next page refresh; no rebuild needed. An emergency env override (`AMC_MOBILE_EAGER_BOOT=1`) forces the eager behavior even when this is on. --- ## Mobile font size {#mobileFontSize} The text size used in the Omniscio mobile web view. Separate from the desktop font size; defaults to `extra-large` because phones benefit from larger text out of the box. Options: `extra-small`, `small`, `medium`, `large`, `extra-large` (default), `xx-large`, `xxx-large`. Change in Settings → Appearance on your phone. --- ## Mobile header style {#mobileHeaderStyle} The visual style of the top header bar in the Omniscio mobile view. Options include: `current` (frosted glass + accent glow — the default), `bare`, `seamless`, `solid`, `dawn`, `card`, `hairline`, `condensed`, `island`, and `horizon`. Applies live without a restart; mobile only. Experimental — visible only when the "Mobile header and row style" lab feature is on in Settings → Appearance on a phone. --- ## Mobile instant shell {#mobileInstantShell} Controls the mobile service worker cache strategy. When on (the default), the installed mobile web app serves its cached shell immediately on every open and downloads new builds in the background, swapping atomically when complete. This makes every subsequent open feel instant. Off restores the legacy network-first behavior where each open waits for the latest `index.html` from the server. Renderer-side only — takes effect after the next page refresh. --- ## Mobile reliability alerts {#mobileReliabilityAlertsEnabled} When on, Omniscio raises an inbox alert if it detects that the mobile web app's load watchdog is struggling — for example if the phone appears to have lost reliable connectivity to the local server. Off by default. Enable if you want proactive notification of mobile connectivity issues. --- ## Mobile row density {#mobileRowDensity} Controls how tall the session-list rows are on phones. `normal` (the default) uses standard row height; `compact` condenses rows so more sessions fit on screen. Applies live; desktop rows are unaffected. Experimental — shown in Settings → Appearance on a phone only when the "Mobile header and row style" lab feature is on. --- ## Narration mode {#narrationMode} Controls whether and how the spoken-audio narration of AI replies fires. `off` disables narration entirely — no script is generated and no play button appears. `click` (the default) generates a spoken script and shows a per-message play button, but does not auto-play. `auto` generates the script and automatically plays it on each new completed reply in the open session. Requires the spoken-narration in-development feature to be revealed. Start with `click` to avoid unexpected audio. --- ## Narration prompt override {#narrationPromptOverride} An optional custom prompt that replaces the built-in prompt used to generate the spoken-narration script. Empty by default (uses the built-in prompt, which is recommended). Set only if you want to tune the wording or style of narrated recaps. Up to 10,000 characters. Part of the spoken-narration in-development feature. --- ## Narration read view {#narrationShowReadView} When on (the default), displaying a message's spoken-narration script also shows a "read view" overlay — a clean text rendering of the narration script alongside the play button. The play button itself is controlled separately (by whether narration data exists). Turn off to hide the read-view overlay while keeping narration playback. See spoken-narration-contract.md. --- ## Narration voice reply auto-send {#narrationVoiceReplyAutoSend} When on, the voice-reply window opened from a narration play button automatically sends your spoken words back to the session once you pause on a sufficiently long phrase — hands-free mode. Off by default, which means you review the transcription and send manually. Part of the in-development "Reply by Voice" narration feature; requires voice input to be on. --- ## KMS Vault Overview {#nothariOverviewEnabled} Shows or hides the Vault Overview table in the Knowledge Management System (KMS) panel — a searchable list of every indexed note with its title, summary, and size. On by default whenever KMS is enabled. Turn off if you prefer not to see the overview table surface. The underlying indexing is unaffected. --- ## OpenCode model {#opencodeModel} The model OpenCode sessions use, specified as `provider/model` (for example `openrouter/moonshotai/kimi-k2`). `null` or empty (the default) uses OpenCode's own built-in default model with the OpenCode/Anthropic key. The provider prefix selects which stored credential Omniscio injects at session spawn. Change this in Accounts & Providers → OpenCode if you want a specific model for all OpenCode sessions. --- ## Who pays for each provider {#providerFunding} **Replaced by [Who pays & who serves](settings-extra-s.md#supplyLists).** The "Use Omniscio … credits" switches that wrote this setting are gone: who pays is now a row in each model family's supply list, and your earlier choices were carried into those lists. What follows describes it as it was. Your choice, for each AI provider separately, between paying with your own key for that vendor and paying with Omniscio credits. Setting one provider never changes another — you can run DeepSeek on your own key and buy GLM on credits at the same time. Each provider you have chosen for is stored as a ranked list of funding sources: `own-key` (your own vendor key, billed by that vendor directly) and `omniscio` (Omniscio's gateway key, which draws down your prepaid credit balance and stops at zero). The session uses the first source that is actually ready, and moves to the next if the active one runs out mid-session. A provider you have never chosen for is absent from the list, which means **your own key first** — nothing starts spending credits by surprise. Ranking is only a preference: each source still has to pass its own readiness and plan checks, and an unready one is skipped rather than forced. Replaced eight older settings on 2026-09-13 — a single global funding order plus seven per-vendor "use Omniscio credits" toggles — which between them could not express a per-provider choice. Every existing opt-in was converted automatically. Object mapping each provider id to its ranked list; accepted source values: `own-key | omniscio`. --- ## Outbound webhooks {#outboundWebhooksEnabled} Master gate for the outbound webhook dispatcher — the feature that delivers a curated set of Omniscio events to customer-configured callback URLs. Off by default (in-development). The dispatcher re-reads this flag on every event so toggling it takes effect live without a restart. The feature is inert until the webhook management UI is available; turning this on early is safe but has no visible effect until webhooks are configured. --- ## Paste rich text as Markdown {#pasteRichTextAsMarkdown} When on (the default), pasting rich text (HTML from a webpage, a Google Doc, etc.) into an Omniscio composer converts it to Markdown before inserting it. Turn off if you want rich-text pastes stripped to plain text instead. Note: content pasted from Google Sheets is always stripped to plain text regardless of this setting, because the rich-text representation is unreadable noise. --- ## Agent persona {#personaPromptEnabled} Controls the persona block injected at the top of every session's system prompt. When on (the default), the agent adopts an upbeat, proactive, resourceful, friendly persona that defaults to yes, takes initiative, assumes a request is possible, and drives work to a finished result. Turn off to remove the persona and character block entirely, leaving a neutral tone. Settings → Sessions → Prompting. --- ## Pi model {#piModel} The model Pi sessions use, specified as `provider/model` (for example `anthropic/claude-sonnet-4-5` or `openai/gpt-4o`). `null` or empty (the default) uses the built-in Pi default model. The provider prefix selects which stored credential is injected at spawn. Change this in Accounts & Providers → Pi. --- ## Session tool picker tools {#pickerToolIds} A list of tool/engine IDs that appear in the new-session Tool dropdown (the start-config picker). Unset by default, which shows all available engines. Providing a list trims the picker to only those IDs. `claude-code` is always shown regardless. This only affects the per-session picker — not the per-project default setting. --- ## Pika voice {#pikaVoiceId} The voice preset sent to the Pika Speech text-to-speech service. Accepts a named preset string (one of Pika's `PIKA_PRESET_VOICES`). Default is `calm_documentary_narrator`. Pika is user-key-only (no relay); change this in Settings → Voice if you have a Pika key and want a different voice. --- ## Plugin auto-check updates {#pluginAutoCheckUpdates} When on (the default), Omniscio keeps your installed plugins up to date. At launch and on a background interval it applies an update that asks for nothing new by itself, and when a newer version wants access you have not approved it stops and asks you first, with the permission list shown. Turn off to disable the checks entirely: nothing is checked and nothing is updated in the background. --- ## Which boards appear on the calendar {#pmCalendarBoardIds} Narrows the Mission Control calendar overlay — due dates and sprint timelines drawn on your calendar — to specific boards. Leave it empty — the default — and every board shows up. Add boards here when only a couple of them matter on your calendar and the rest are noise. Has no effect unless the PM calendar overlay itself is on. Holds up to 100 boards. ## PM calendar overlay {#pmCalendarOverlayEnabled} Shows PM board due dates and sprint timelines as an overlay on the calendar view. On by default when Mission Control is enabled. Turn off if you want the calendar to show only alarms and scheduled items without project-management events. You can also limit the overlay to specific boards via the board-filter setting. --- ## Per-board inbox preferences {#pmInboxBoardPreferences} How much each board is allowed to put in your inbox, board by board. **All** sends every event from that board, **Assigned only** sends just the items assigned to you, and **None** silences it entirely. A board you have not set here follows the global PM inbox setting, so you only need an entry for a board you want louder or quieter than the rest. Use it when one busy board is drowning out the others. Holds preferences for up to 100 boards. ## PM inbox digest mode {#pmInboxDigestMode} When on, project-management inbox events (assigned, status-changed, due-approaching, overdue) are batched into a digest instead of surfacing as individual inbox rows. Off by default — events arrive individually so you see each one immediately. Turn on if you prefer a periodic summary over a continuous stream of PM notifications. --- ## PM inbox {#pmInboxEnabled} Enables the project-management inbox integration, which surfaces PM board events (assigned tasks, status changes, approaching due dates, overdue items) as inbox rows. On by default when Mission Control is enabled. Turn off to stop PM events from appearing in your inbox while keeping the rest of Mission Control active. --- ## PM inbox quiet hours {#pmInboxQuietHoursEnabled} When on, PM inbox notifications are suppressed during a configurable daily time window so you are not disturbed outside working hours. Off by default. Set the window with `pmInboxQuietHoursStart` and `pmInboxQuietHoursEnd` (in `HH:MM` format) and the time zone with `pmInboxQuietHoursTimeZone`. --- ## PM inbox quiet hours end {#pmInboxQuietHoursEnd} The time (in `HH:MM` 24-hour format) when the PM inbox quiet-hours window ends and notifications resume. Default `07:00`. Interpreted in the time zone set by `pmInboxQuietHoursTimeZone`. Only active when `pmInboxQuietHoursEnabled` is on. --- ## PM inbox quiet hours start {#pmInboxQuietHoursStart} The time (in `HH:MM` 24-hour format) when the PM inbox quiet-hours window begins and notifications are suppressed. Default `22:00`. Interpreted in the time zone set by `pmInboxQuietHoursTimeZone`. Only active when `pmInboxQuietHoursEnabled` is on. --- ## PM inbox quiet hours time zone {#pmInboxQuietHoursTimeZone} The time zone your PM inbox quiet hours are measured in — the daily no-notification window for project-management items. Leave it unset — the default — and quiet hours follow your computer's current zone. Set a specific zone (an IANA name like `America/New_York`) to pin them, so quiet hours stay at the same local wall-clock time even if you travel or your machine's zone changes. Only relevant while quiet hours are turned on. ## PM setup preset {#pmSetupPreset} The project-management workflow preset you selected during Mission Control setup. Options include general presets (`tasks`, `projects`, `operations`, `first-agent-board`) and tool-specific ones (`trello`, `jira`, `asana`, `linear`, `notion`, `clickup`, `airtable`, `engineering-linear`, `engineering-jira`). Written by the setup wizard; you can change it later to reconfigure the Mission Control experience to match a different workflow style. --- ## Pomodoro — auto-enable Focus Mode {#pomodoroAutoEnableFocusModeDefault} When on (the default), starting a Pomodoro focus block automatically enables Focus Mode, and entering a break automatically disables it. If you manually toggle Focus Mode during a run, you take back control and the Pomodoro service stops managing it for the rest of that run. Turn off if you want to run the Pomodoro timer without it touching your Focus Mode state. --- ## Pomodoro — bring to foreground on phase change {#pomodoroPhaseForeground} When on, the Omniscio window forces itself to the foreground every time the Pomodoro timer transitions between focus and break phases. Off by default — the audible chime and tray badge are usually enough. A per-preset `bringToForegroundOverride` takes precedence, and Focus Mode can still gate this behavior. --- ## Pomodoro schedule {#pomodoroScheduleEnabled} Master toggle for the Pomodoro schedule. When off, all scheduled Pomodoro session rows are ignored — no pre-start toasts and no auto-starts. On by default so a newly created schedule fires as expected. Turn off to pause the schedule temporarily without deleting it. --- ## Post-send navigation {#postSendNavigation} An ordered list of actions Omniscio tries in sequence after you send a message from the inbox. Options are `stay` (keep the current session open), `next_in_project` (move to the next session in the same project), `next_in_inbox` (move to the next inbox item), and `waiting_room` (go to the waiting room). The default order is `next_in_project`, `next_in_inbox`, `stay` — Omniscio picks the first option that has a valid destination. Reorder or remove options in Settings → Inbox. **Scope — typed replies only.** This setting governs what happens after you _type and send_ a reply. One-click triage gestures deliberately ignore it: archive, snooze, Continue, and Allow/Deny on a command prompt all advance the way archiving does — to the next session that needs you, and failing that the next visible session in the area you are already in. That is why approving a command can move you somewhere this list does not name. --- ## PR Merge Queue — auto-merge poll interval {#prMergeQueueAutoMergePollMinutes} How often (in minutes) the auto-merge daemon checks for eligible pull requests to process. Default is 10 minutes; valid range is 1–120. Values outside the range are clamped at startup. Only relevant when `prMergeQueueEnabled` and `prMergeQueueAutoMergeEnabled` are both on. --- ## PR Merge Queue {#prMergeQueueEnabled} Master gate for the PR Merge Queue integration. When on, the sidebar virtual project, the toolbar icon, and the Settings subsections for the merge queue become visible. When off, all three are hidden but your stored repo configuration and auto-merge daemon settings are preserved — toggling back on restores everything. Off by default; existing installs that already have repos configured are auto-enabled once via a one-time migration. --- ## PR Merge Queue — shard count {#prMergeQueueShardCount} The total number of machines sharing the PR merge workload (the modulo divisor used when sharding is on). Default is 2. A value less than 2 makes sharding a no-op so this machine handles everything. Only meaningful when `prMergeQueueShardEnabled` is on. Set each machine to a distinct shard index and the same shard count so they partition the work without overlap. --- ## PR Merge Queue — sharding {#prMergeQueueShardEnabled} When on, the auto-merge daemon only auto-processes pull requests whose PR number modulo the shard count equals this machine's shard index. This lets two or more independent Omniscio installs share the same repo's queue without ever merging the same PR twice. Off by default. Manual merge actions (the Merge button, `MERGE_PR`, `MERGE_BATCH`) are never shard-filtered — an explicit action always works. The shard configuration is also exported for the `merge-remote-prs` skill and the PR janitor cron. --- ## PR Merge Queue — shard index {#prMergeQueueShardIndex} This machine's 0-based position in the shard split (0 ≤ index < count). Give each install a distinct index — box A gets 0, box B gets 1, and so on. Default is 0. An out-of-range or negative value is fail-safe: this machine auto-spawns nothing rather than risk a double-merge. --- ## Provider config sync targets {#providerConfigSyncTargets} The list of other AI CLI provider IDs (for example `codex`, `gemini`, `opencode`, `cursor`) that Omniscio will install your shared MCP server configuration into when provider config sync is on. Empty by default. Part of the in-development provider-config-sync feature; each entry causes the sync to register your `sync_to_machine` MCP servers with that tool's own `mcp` CLI. --- ## Quick Chat per-target hotkeys {#quickChatHotkeysEnabled} Master enable for global keyboard shortcuts assigned to individual Team Chat Message targets (people and channels). Off by default. When on, each saved target that has a hotkey configured registers it as an OS-wide shortcut that opens the Quick Launch composer pre-aimed at that person or channel. Turn on only if you want one-key access to specific teammates or channels from anywhere on your machine. --- ## Quick Email saved recipients {#quickEmailRecipients} The list of contacts saved for Quick Email — the fast one-key email composer in Quick Launch (Ctrl+Space). Each entry has a display name, an email address, and an optional per-recipient global hotkey. Up to 50 recipients. Add and manage them in Settings → Quick Email. When a hotkey is set for a recipient, pressing it from anywhere on your machine opens the Quick Launch composer pre-filled for that person. --- ## Quick Email signature {#quickEmailSignature} An optional signature appended to the body of every email sent from the Quick Launch Quick Email composer. Blank by default (nothing appended). This is specific to Quick Email — it does not pull from your Gmail web signature. Up to 1,000 characters. Set it in Settings → Quick Email. --- ## Quick Email undo window {#quickEmailUndoSeconds} How many seconds a sent Quick Email is held in an undoable pending state before it is actually delivered. During this window you can cancel the send. Default is 10 seconds; valid range is 1–30. Increase if you frequently catch mistakes after hitting send; decrease if you want delivery to be more immediate. --- ## Quick Launch — follow cursor {#quickLaunchFollowCursor} When on, the Quick Launch floating modal opens on whichever monitor your mouse cursor is on rather than always opening on the primary display. Off by default. Useful if you work across multiple monitors and want Quick Launch to appear where you are looking. Takes effect on the next Ctrl+Space press — no restart required. --- ## Quick Launch hotkey {#quickLaunchHotkey} The global keyboard shortcut that opens the Quick Launch floating modal (default Ctrl+Space). Accepts a single Electron accelerator string or a list of alternates. Registered with the OS only when `quickLaunchHotkeyEnabled` is on. Change it in Settings → Hotkeys if it conflicts with another application (note: on Windows, Ctrl+Space is also the IME input-method toggle, which can cause a conflict — Omniscio will warn you if a CJK input method is detected). --- ## Quick Launch — preserve draft {#quickLaunchPreserveDraft} When on (the default), closing the Quick Launch composer without sending keeps your unsent draft — text and any pasted chips — so the next time you open Quick Launch it resumes where you left off. The Reset button or turning this off clears the draft instead. Sending always clears the draft regardless of this setting. Draft state is held in memory only; a full app restart always starts blank. --- ## Quick Launch — show engine picker {#quickLaunchShowHarnessPicker} When on, the New Session tab in Quick Launch shows two compact chips — Engine and Model — next to the project chip, letting you change the engine or model for just that one launch. Off by default. The resting state shows the project's resolved default; picking a chip overrides it for the next session only. Turn on if you frequently launch sessions with a non-default engine from Quick Launch.