Which hub an alert-started session uses

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.
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 "Omniscio", "Omniscio Marketing" and "AMC Marketing" 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.

Every other start-session dialog — inbox cards, drip, the weekly-summary suggestion, and the Weekday Reflection Nudge — deliberately keeps the plain Claude default, and so does the mobile Session tile; only alerts opt in.

For agents

• app-repo-hub.ts resolves the hub and flags it on the project list.
• alert-session-default-hub.ts applies the setting over that guess.
• spawnable-hub-options.tsx puts the winner first in the picker.
• The invariant behind the picker's single icon: project-picker-icon-contract.md.

Related

• start-a-new-session.md — the launch itself: the button, the keyboard shortcut, and what the session row tracks
• add-a-project.md — a hub is a project; add one before you can point a setting at it
• default-claude-project.md — the ~/Claude workspace that step 4 falls back to
• clear-a-hub.md — what removing a hub does to a setting that named it
• project-folder-missing.md — what to do when the hub a session picked no longer exists on disk