Omniscio

Which hub an alert-started session uses

Every other way of starting a session uses the hub you are already in. The Start session button on an alert is the one exception: it resolves a hub of its own — the repo the alert names first, then your Start alert sessions in setting, then an automatic Omniscio checkout, and the built-in Claude hub last.

On this page

What it is

Most entry points already know their hub — the "+" button uses the active project, a repo tile launches into its own repo, and Quick Launch has its own Quick Launch Default Project setting (Settings → Quick Launch). The one place with a smarter answer is the Start session button on an alert.

An alert is Omniscio talking about itself — a failed land, a stuck gate, a bug report — so a session started from one usually belongs in the repo you develop the app in, not the general-purpose ~/Claude workspace. This page is the resolution that button uses.

Where to find it

  • On the alert itself — the Start session button, on any alert card in the inbox.
  • Settings → Inbox → Start alert sessions in — your own pick for which hub those sessions land in.

How it behaves

The button resolves its hub in this order:

  1. The repo the alert names, when it has one — its saved session repo, else the repo it is grouped under. This holds for Omniscio's own machinery alerts too: a worktree-cleanup card about one of your repos opens its session in that repo, not in the Omniscio checkout. Only an alert that names no repo, or one whose fix lives inside Omniscio (a rented cloud machine that did not attach, say), saves the Omniscio checkout as its session repo. A card raised before this rule keeps the repo it was saved with until it clears.
  2. Your setting — Settings → Inbox → Start alert sessions in. An explicit pick always wins over the automatic guess below.
  3. Automatic (the default) — the hub whose folder is a checkout of Omniscio itself. It is found by reading the repo (a package.json identity check, seeded by the ~/.claude/amc-repo.path pointer npm run setup writes), never by the hub's name — a real install can hold "Acme", "Acme Marketing" and "Acme Labs" side by side, so a name match has no principled answer. A linked git worktree is never chosen, only a main checkout.
  4. The built-in Claude hub (~/Claude).

If you have no Omniscio checkout registered as a hub — which is every non-developer install — step 3 finds nothing and the behavior is exactly as it always was: Claude is the default. Claude always stays available in the picker either way; it just stops winning automatically. A setting pointing at a hub you later deleted is ignored rather than obeyed, so the picker is never left pre-selecting somewhere a session cannot start.

One alert, one session

  • The dialog launches the alert you opened it on. If another card takes the inbox's top slot while the dialog is open, the session still starts from — and archives — the alert you picked.
  • No second card while a session is on it. Once a session has been started from an alert, a fresh copy of that same alert is held back while the session is still running, for up to 24 hours (6 hours for an alarm). A copy that shows something new (a new item, or a worse step), or that comes back after the problem had cleared, still comes through. A restart of the app forgets the hold, so at worst you see the card once more.

The other Start session dialogs opened from a stored item — a drip item, a scheduled message, a weekly summary or suggestion, a briefing, a failed scheduled job, a Help Desk report or ticket, a share, a Linear issue — are the same shared dialog and pick their hub the same way after their own saved repo: steps 2–4 above. Team Chat (its own remembered hub) and Supermail (always the Supermail host) choose differently, and so does the mobile Session tile.

Last verified 2026-11-05