# Integrations & connections settings Controls which outside services Omniscio connects to and how it behaves when it does — email, file storage, calendars, messaging, project tools, and automation bridges. --- ## Gmail integration {#gmailEnabled} Turns the Gmail panel on or off in the sidebar. When enabled, you can read email threads, reply, archive, star, and snooze without leaving Omniscio. Requires your Google account to be connected. Off by default until you sign in. Disabling it hides the panel but does not disconnect your Google account — re-enable at any time to get the inbox back. Related settings: `gmailPageSize`, `gmailAutoMarkRead`, `gmailAutoFocusReply`. --- ## Auto-focus reply box {#gmailAutoFocusReply} Controls where keyboard focus lands when you open an email. When on, the cursor jumps straight into the reply text box so you can start typing immediately. When off (the default), focus stays on the message body, which keeps all triage keyboard shortcuts active: **E** to archive, **S** to star, **U** to mark unread, **!** for spam, **X** to select, **H** to snooze. Press **R** when you're ready to reply. Turn this on if you rarely use keyboard shortcuts and prefer to reply by default. --- ## Auto-mark as read {#gmailAutoMarkRead} When on, Omniscio automatically marks an email thread as read the moment you open it — the same behavior Gmail itself uses. When off, threads stay unread until you mark them manually, which is useful if you want to come back to something later. On by default, so opening an email does mark it read unless you turn this off. --- ## Threads per page {#gmailPageSize} Sets how many email threads load at one time in the Gmail panel. Accepts whole numbers from 1 to 100 (the UI enforces 10–100 in steps of 10). A smaller number loads faster; a larger number means less scrolling to reach older threads. The default is 20. Adjust it if you would rather load fewer or more threads in one sitting. --- ## Google CLI backend {#googleCliBackend} Chooses which command-line tool Omniscio uses to talk to Gmail and Google Calendar. **gog** is the default — it's already installed and signed in on this machine. **gws** is Google's official Workspace CLI (a Rust binary from github.com/googleworkspace/cli); it needs to be installed separately and requires its own `gws auth login` before you switch. Both backends do the same job — switch to gws only if you have a reason to prefer it or if gog stops working. --- ## Auto-import pasted Google Doc URLs {#googleDocImportEnabled} When on, pasting a Google Docs or Google Slides link into a chat session automatically fetches the document's text content and inserts it inline, so the session can work with the actual content rather than just a URL. Hold **Shift** while pasting to skip the fetch for that paste. Off by default; turn it on if you want pasted Doc links expanded into their content automatically. Nothing turns it on when you connect Google Drive. --- ## Google Drive integration {#driveEnabled} Adds a Google Drive panel to the sidebar for browsing folders, opening files, and uploading documents without leaving Omniscio. Requires your Google account to be connected. Turn off to hide the Drive panel; your Google sign-in is unaffected and the panel can be re-enabled later. Off by default until you connect Google. --- ## Dropbox integration {#dropboxEnabled} Adds a Dropbox panel to the sidebar so you can browse folders, open files, and upload documents from your Dropbox account directly in Omniscio. Requires a connected Dropbox account. Off by default. Disabling hides the panel but does not sign you out of Dropbox. --- ## OneDrive integration {#onedriveEnabled} Adds a Microsoft OneDrive panel to the sidebar for browsing, opening, and uploading files from your OneDrive storage. Requires your Microsoft account to be connected. Off by default. Turning this off hides the panel; your Microsoft sign-in persists and you can re-enable it at any time. --- ## Google Sheets integration {#sheetsEnabled} Adds a Sheets panel to the sidebar so you can browse and edit Google Sheets spreadsheets without leaving Omniscio. Requires your Google account to be connected. Off by default. Disabling hides the panel; your Google sign-in is unaffected. --- ## SMS integration {#smsEnabled} Turns SMS messaging on or off. When enabled, Omniscio can send and receive text messages through your chosen SMS provider (Pushbullet or a self-hosted native gateway). Off by default. Requires a Pushbullet account or a running native gateway app on your phone before enabling. Related: `smsProvider`, `smsNameInferCostCapUsdPerDay`. --- ## SMS provider {#smsProvider} Selects the backend used to send and receive texts. **Pushbullet** routes messages through Pushbullet's cloud service — easy to set up but requires a Pushbullet account. **Native (my phone)** sends over your own phone's real SIM via a self-hosted gateway app, with no third-party cloud in the path. Only visible when SMS is enabled. Default is `pushbullet`. Switch to `native` if you want full control over your messages and don't want them passing through a third-party server. --- ## AI name inference daily cost cap {#smsNameInferCostCapUsdPerDay} Limits how much Omniscio spends per calendar day on AI calls (via Claude Haiku) that figure out friendly names for unknown short codes — for example, turning `62438` into `"eBay security code"`. Once the daily cap is reached, name inference pauses until midnight and resumes the next day. Accepted range is $0.05 to $5.00. Default is a low value to keep costs predictable. Raise it if you receive many messages from short codes and want them named promptly. Only visible when SMS is enabled. --- ## Calendar integration {#calendarEnabled} Shows upcoming calendar events in the sidebar and sends reminders before meetings. Connects to Google Calendar (requires your Google account). When on, you can see your day's agenda and get notified before an event starts without switching to another app. Off by default until you connect Google. Disable to hide the calendar panel while keeping your Google account connected. --- ## Notion auto-sync {#notionAutoSyncEnabled} Keeps the currently open Notion page refreshed automatically while the Notion board is visible and Omniscio is in the foreground. When on, Omniscio re-checks the open page for edits in the background and periodically refreshes the view, pausing when the window is hidden. On by default. Turn off if you prefer to refresh manually with the refresh button, or if background network activity is a concern. --- ## Notion inbox notifications {#notionInboxEnabled} Surfaces recently-edited Notion pages as rows in the unified Inbox and adds a new row when a page changes, so you see Notion activity without switching apps. Requires the Notion board to be enabled and connected. Off by default. When on, Omniscio checks Notion in the background every few minutes. Disable to stop Notion items from appearing in the Inbox while keeping the Notion board itself active. --- ## Show images in Notion pages {#notionShowImages} Controls whether image blocks load when you open a Notion page inside Omniscio. Off by default for privacy — loading external images can reveal your IP address and that you viewed the content, similar to email tracking pixels. While off, an image block shows a placeholder with a link to open the page in Notion directly. Turn on if you want inline images to display and are comfortable with the privacy trade-off. --- ## Jira inbox notifications {#jiraInboxEnabled} Surfaces your assigned, not-yet-done Jira issues as rows in the unified Inbox and adds a row whenever one of them updates. Requires the Jira board (above) to be enabled and your Jira account connected. Off by default. When on, Omniscio polls Jira in the background every few minutes. Disable to stop Jira items from appearing in the Inbox without disconnecting Jira entirely. --- ## Linear inbox notifications {#linearInboxEnabled} Surfaces your unread Linear notifications — mentions, replies, status changes, and new assignments — as rows in the unified Inbox. Requires the Linear board to be enabled and connected. Off by default. When on, Omniscio checks Linear in the background every few minutes. Disable to stop Linear notifications from appearing in the Inbox while keeping the Linear board active. --- ## Canva integration {#canvaMcpEnabled} Connects your Claude sessions to Canva via an MCP (Model Context Protocol) bridge. When on, sessions can create and edit designs, search your Canva library, export to various formats, and manage brand assets — all through conversation. Requires your Canva account to be linked. Off by default. Disable to disconnect the Canva bridge without affecting your Canva account. --- ## Fathom integration **Retired (2026-09-19).** No AMC-built MCP server composes into a session any more, so the Fathom MCP connection and its toggle and API key are gone. The server code and its entry builder stay in the tree, unwired. --- ## Zapier integration {#zapierEnabled} Connects your Claude sessions to thousands of apps through Zapier's MCP server. When on, sessions can trigger Zaps, pass data between apps, and run automations across the 8,000+ services Zapier supports. To set up: create a Zapier MCP server at mcp.zapier.app, then paste the server URL into the field that appears below. Off by default. Disable to disconnect the Zapier bridge without removing your Zapier account. --- ## Webhooks {#webhooksEnabled} Lets external services send data into Omniscio by posting to a unique webhook URL you give them. Useful for CI/CD pipelines, monitoring tools, custom scripts, or any service that can make an HTTP POST request. When on, Omniscio listens for incoming webhook payloads and routes them to sessions or inbox rows. Off by default. Enable when you want to trigger Omniscio actions from an outside system. --- ## Supermail inbox notifications {#supermailInboxEnabled} Controls whether unread emails from the Supermail plugin appear as rows in the unified Inbox. When on, Supermail emails surface alongside your other inbox items so you can triage them in one place. Requires the Supermail plugin to be active. Off by default. Disable to stop Supermail items from appearing in the Inbox without removing the plugin. --- ## Pull request inbox notifications {#prInboxEnabled} Surfaces GitHub pull requests that are waiting on you — reviews you've been asked to do, and your own PRs that have changes requested — as rows in the unified Inbox. Requires the Pull Requests tab to be enabled and the GitHub CLI (`gh`) to be signed in. Off by default. When on, Omniscio checks GitHub in the background every few minutes. Disable to stop PR rows from appearing in the Inbox while keeping the Pull Requests tab active. --- ## PR merge-queue dry-run mode {#prMergeQueueAutoMergeDryRun} When on, the PR merge-queue daemon logs what it would auto-merge on each tick but does not actually spawn any Claude sessions or trigger merges. Use this to preview which pull requests the daemon would pick up and in what order before committing to live auto-merging. Off by default (live mode). Turn on to safely audit the queue configuration without side effects, then turn off when you're ready to go live. --- ## PR-prep prompt (advanced) {#prPrepPromptTemplate} The instructions Omniscio gives each session it starts to get one of your pull requests ready to merge. Leave it empty to use the built-in version — the default is written for the job and most people never change it. If you write your own, it **must** keep three things, or Omniscio quietly falls back to the built-in prompt instead of using yours: the hand-off that marks a branch ready, the line that signals the run succeeded, and the rule that never pushes to your main branch. There is an easier option — **Custom rules** just below — that adds your own instructions without you having to preserve any of that. Edit both in **Settings → PR Merge Queue**. --- ## Custom rules for the PR-prep prompt {#prPrepPromptCustomRules} Standing rules appended to the automatic PR-prep prompt — the easy way to add your own instructions without rewriting the whole prompt and having to keep its load-bearing lines intact. Whatever you put here is added **on top of** the built-in preparation prompt, or on top of your own prompt if you have set one above. Edit it in **Settings → PR Merge Queue**. --- ## Merge prompt (advanced) {#prMergeQueueMergePromptTemplate} The instructions Omniscio gives the session that merges one of your pull requests, in place of the built-in version. Leave it empty to use the built-in prompt. A per-repo override takes precedence over this global one, so set this only when every repo should behave the same way. Edit it in **Settings → PR Merge Queue**. --- ## Block remote images in emails {#emailBlockRemoteImages} Prevents external images from loading when you open an email in Omniscio's Gmail panel. Remote images can silently notify the sender that you opened the message and report your IP address — a technique often called a "tracking pixel." Blocking them keeps that information private. Inline images and attachments (images already embedded in the email) still display normally. Off by default. Turn on for stronger email privacy. --- ## Classic Email Cleanup layout {#emailCleanupClassicLayout} Switches the Email Cleanup tool back to its original flat sender list instead of the AI-guided walkthrough. The AI-guided walkthrough is the default — it steps you through senders one by one with suggested actions. Turn this on if you prefer a simple list view where you decide what to do for each sender yourself, without the guided flow. The underlying cleanup actions are the same either way. --- ## Slack integration {#slackEnabled} Turns the Slack integration on or off. When enabled, Omniscio can connect to your Slack workspace so sessions and inbox items can surface Slack activity. Requires your Slack account to be connected. Off by default until you sign in. Disable to disconnect the integration without removing your Slack account. --- ## RSS integration {#rssEnabled} Turns the RSS/Atom feed reader on or off. When enabled, you can subscribe to feeds and have new articles surface in the sidebar and optionally in the Inbox. Off by default. Enable and add feed URLs in the RSS settings to start receiving articles. Disable to hide the reader without losing your saved feed subscriptions. --- ## Telegram integration {#telegramEnabled} Turns Telegram messaging on or off in Omniscio. When enabled, Omniscio connects to your Telegram account via the MTProto protocol so you can send and receive Telegram messages from within the app. Requires your Telegram phone number and a sign-in confirmation code. Off by default. Disable to disconnect Telegram while keeping your account intact; re-enable to sign back in. ## Telegram Bot {#telegramBotEnabled} Turns the Telegram Bot channel on or off. This is a separate path from the Telegram integration above: instead of signing in as you, Omniscio runs a bot you create with BotFather, and you talk to your agents by messaging that bot. Each Telegram chat (a direct message, a group, or a forum topic) becomes its own agent session, replies come back to the same chat, and the conversation survives app restarts. Off by default. Turning it off stops the bot from listening but keeps the token and your allow lists; sign out from the card to clear them. ## Telegram bot token {#telegramBotToken} The token BotFather gave you when you created the bot (it looks like `123456789:AA…`). Omniscio verifies it with Telegram before saving and stores it encrypted; it is never shown again and never sent to any device. Paste a new token to switch bots. Signing out clears the token and detaches every chat from its session (the sessions themselves are kept). ## Telegram bot DM policy {#telegramBotDmPolicy} Who may send the bot a direct message. **Pairing** (default): an unknown sender gets a one-time code and their messages go nowhere until you approve the request in this card or from the CLI. **Allowlist**: only the user ids in the allowed-users list, with no pairing prompt. **Disabled**: direct messages are ignored. This is real authentication for who may drive a paid agent session — it is separate from the Approved Senders cost guard used by automations. ## Telegram bot allowed users {#telegramBotAllowedUserIds} Numeric Telegram user ids that may talk to the bot, in direct messages and as senders inside allowed groups. Approving a pairing request adds the sender here automatically. Empty means nobody is allowed (fail closed). You can find your own id by messaging the bot: the pairing prompt includes it. ## Telegram bot allowed groups {#telegramBotAllowedGroupIds} Numeric Telegram group or supergroup chat ids the bot will answer in (they usually start with `-100`). Empty means the bot ignores every group. A group message is only routed when the group is listed here **and** the sender is an allowed user **and**, if required, the bot was mentioned. ## Telegram bot requires @mention in groups {#telegramBotGroupRequireMention} When on (default), the bot only reacts to group messages that @mention it or reply to one of its messages, so unrelated group chatter never reaches an agent. Turn it off to route every message from an allowed sender in an allowed group.