Omniscio

Session Starter Bot

Session Starter Bot is a per-channel automation in Team Chat: it watches a channel for messages matching keywords you choose and automatically starts an AI session for each one, in the project you nominate. You configure one bot per channel, and it runs whenever Omniscio is open. It can also post an acknowledgment, or reply back in the channel conversationally as your agent.

On this page

What it is

A per-channel automation in Team Chat that watches for messages matching your keywords and spawns an AI session automatically. You configure one bot per channel; it runs while Omniscio is open.

Where to find it

How to set it up

  1. In Team Chat, right-click a channel in the sidebar.
  2. Click Session Bot in the context menu (visible to the channel creator and workspace admins).
  3. Check Enable to turn it on.
  4. Choose a Target project for spawned sessions.
  5. (Optional) Enter Keywords as a comma-separated list. A message containing any keyword as a whole word (case-insensitive) triggers the bot, so bug matches "Bug: login fails" but not "Debug: …". Leave keywords empty to trigger on every message; the daily limits below still apply.
  6. (Optional) Set a Daily rate limit to cap how many sessions it spawns per day. The field starts at 200, which is also the limit used when you enter 0.
  7. Click Save.

How it behaves

Reply modes

The bot has two modes that control what happens after it spawns a session:

Canned acknowledgment (default)

When Post acknowledgment reply is checked, the bot posts a one-liner back to the channel confirming it started a session. This is purely informational and costs nothing extra. Uncheck it for silent operation.

You can customize the acknowledgment text in the Custom reply message field (up to 500 characters). Leave it blank to use the default ("Session started for this message in project ..."). The custom message field only appears when acknowledgment is enabled and conversational reply mode is off.

Adding the date the fix shipped (opt-in)

Turn on Add the date the fix shipped and the bot later edits its acknowledgment once the work it started becomes a pull request. The reply then reads like "On it, thank you!" followed by "Fix has been shipped 10/22/26." The date is the day the first pull request for that work was opened, on your computer's calendar.

  • The switch is off by default and only appears while Post acknowledgment reply is on and Reply conversationally is off.
  • The note never includes a link, because anyone in the channel can read it.
  • Each reply is updated at most once, so rebuilding the work into a new pull request does not change the date.
  • Omniscio checks every 10 minutes while it is open. A reply whose work never becomes a pull request stops being checked after 30 days.
  • It only covers replies posted after the switch was turned on, and only pull requests for work the bot's own session (or a session it started) did on this computer.

Conversational reply (opt-in)

Check Reply conversationally and the app reads the recent messages in the channel, hands them to a locked AI helper, and posts the reply it writes back as your agent (shown as "Your Name's agent"). The canned acknowledgment is skipped in this mode.

How it stays safe: the reply helper has no tools at all. It cannot run commands, open files on your computer or reach the app's controls, so a message in the channel can at most change the words of one reply. The app — not the helper — decides which channel the reply goes to. The helper runs hidden from your sessions list and closes itself once it has answered.

When it won't reply: reply mode needs a Claude connection the app can lock. With require approval before AI sessions start turned on, or when your only Claude access is the shared gateway, the bot stays quiet instead of replying without the lock.

If the helper's saved settings are damaged: it still starts with no tools. A helper whose lock the app cannot read gets nothing at all, never a reading or searching tool.

Reply sessions from before this update: older versions ran the reply bot as an ordinary session with tools. The first time the app starts after this update, it archives the ones it can recognise as reply bots, so they can't be resumed without the lock. It never touches a session that is running or pinned, it runs only that once, and anything you unarchive afterwards stays where you put it. Archived sessions stay in your archive if you want to read them. Reply sessions from before the app started recording which channel a bot replies in can't be recognised, so they are left as they are.

Safety and limits

  • Your own messages trigger normally. The bot responds to all human messages in the channel, including yours. Loop safety is handled by the agent-authorship flag (below), not by filtering your messages.
  • Minimum length. Messages under 10 characters are ignored.
  • Dedup. The same message is never processed twice on this device — an in-memory window for the fast path plus a record that survives an app restart (a repeat is skipped as "already processed").
  • Loop safety. An agent never replies to another agent's message. This is enforced by a per-channel flag that tracks whether the last message was authored by an agent, so the bot cannot trigger a runaway reply loop.
  • Rate limit. The daily cap (if set) resets at midnight. A 0 limit uses the built-in default of 200 spawns a day. When the channel's cap is reached, the first message refused that day gets one notice in the channel saying the limit was reached and when messages will be answered again, so a spent budget never looks like a broken bot.
  • A bot whose project was deleted says so. The person whose message is refused is told in the channel, once a day, that the bot's project is gone and that whoever looks after the bot needs to point it at a project again. The owner gets one inbox card per channel naming the channel, and nothing is lost.
  • One member's share, and they are told. However the channel's daily cap is set, no single member can trigger more than 50 sessions a day in one channel — so one person posting in bulk cannot use up the day's bot for everybody else. A member who reaches it is told in the channel, once, with the limit named and when it resets, rather than their next message quietly doing nothing. That count is kept in the app's database, so restarting Omniscio does not hand anybody a second share of the day.
  • A daily allowance of paid AI, measured. A channel's bot stops starting sessions for the day once its sessions have cost past that channel's daily allowance, counting what they actually cost rather than how many were started. It stops while the channel can still afford one more session at its own measured average cost, so a burst of messages cannot run past the allowance before the cost is counted. The first stop of the day raises one notice in your inbox for that channel. Sessions already running keep going — this bounds what the bot starts.
  • One member's share across every channel. On top of the 50-in-one-channel limit, no single member can trigger more than 100 sessions a day in total, added up across every channel they post in. It is a total, so triggering bots in several channels cannot multiply one person's share.
  • You can see why a message was skipped. Open Session Bot on the channel: a "Last message" line says what happened to the most recent message, for example "No keyword matched, so no session started" or "Started a session". The bot's own replies and system messages never replace it. It starts empty each time Omniscio starts, and every skip is also written to the app log.
  • A session-mode bot is confined to its own channel. Every session the bot starts — session mode and conversational reply alike — is locked to the channel that triggered it: it can read and post in that channel and reach its own model access, and nothing else through the app's control server. It still works with its full tools and treats the message as data, never as orders. The shipped-date note above follows the bot's branch.
  • App must be running. The bot runs inside Omniscio (renderer-triggered). Messages sent while the app is closed are not evaluated.
  • Single-device. If you run Omniscio on two machines simultaneously, both may trigger on the same message.

Workspaces

The bot works in both your company workspace and user-created (self-serve) workspaces. You can configure a bot on any channel in any workspace you belong to, and it triggers the same way regardless of which workspace type the channel is in.

Behind the scenes, one background watcher keeps listening to your company workspace's channels and up to 5 self-serve workspaces at the same time, whichever workspace you are looking at and even with Team Chat closed. Before 2026-10-27 the company workspace was only watched while it was the open workspace, so a company-channel bot went quiet whenever you were viewing a self-serve workspace. Desktop notifications for workspace messages are a planned follow-up.

Last verified 2026-11-06