Skip to content

HubWindow Operations

HubWindow is the SmrtHub experience. Engineering still refers to it by the internal project name, but every user simply knows it as SmrtHub—the single window, tray icon, and jump list that orchestrate captures, Support Bundles, and future workflows. This page captures what’s live today and documents where the refactor is headed so runbooks remain accurate while the UI modernizes.

Mid-refactor disclosure

The HubWindow shell is in an active rearchitecture (new layout system, unified settings, resurfaces for SmrtSpaces). Capabilities below are accurate for the current build; sections flagged (In progress) identify work that is already underway and will replace the interim behavior. We will refresh this doc as soon as the next UI drop lands.

What ships today

Surface What users can do right now
System tray menu Open SmrtArx, launch supported capture lanes, trigger Support Bundles, exit SmrtHub (secure SHUTDOWN via Supervisor), and monitor notifications. Tray actions route through ITrayController, so every click logs through Smrt.Logging.
Taskbar jump list One-click verbs (Restore, Open SmrtArx, Exit SmrtHub). Jump List actions reuse the single-instance IPC path so launching from Windows never spawns duplicates.
Shared state pane Shows live clipboard fragments, previews, SmrtSpace context, and per-feature status badges (red→amber→green confidence tint) so operators can verify output before pasting or SmrtSaving.
Quick action strips Inline controls for capture lanes, SmrtSave, and SmrtSpaces. These mirror the toggles described in each operations guide (engine picker, profile selector, Quick Save).
Notifications + toasts HubWindow relays uniform toasts (confidence scores, job duration, Support Bundle paths) and publishes the same events to Smrt.Notifications so other hosts stay in sync.
Supervisor integration Exit, restart, and health commands are piped to SmrtHubSupervisor. HubWindow exits immediately after sending SHUTDOWN, while the supervisor handles the orderly teardown.

Daily workflow

  1. Dock or collapse HubWindow – Users keep it docked on a secondary monitor or collapse it to a tray icon. Either state still exposes hotkeys and jump list triggers.
  2. Initiate capture/processing – Use the capture strips (or their tray/jump list equivalents) described in the individual operations guides. HubWindow badges each control while work runs.
  3. Review results inline – Shared state shows clipboard fragments and capture summaries. Confidence colors match across components so operators recognize success at a glance.
  4. SmrtSave / Quick Save – Clicking SmrtSave opens the unified dialog (SmrtSpace picker, templates, notes). Quick Save honors the active space and the toggles set per feature strip.
  5. Diagnostics & support – When something looks off, operators rely on the tray diagnostics menu (Support Bundle export, HTML log viewer, retention evidence) before escalating.

Controls & surfaces (current build)

  • Capture strips – Contextual entry points for the currently enabled capture lanes.
  • SmrtSave / SmrtSpace switcher – Centralized control for the working SmrtSpace so all components save into the same tree without extra clicks.
  • Notifications module – Shows recent toasts (extraction confidence, Support Bundle completion, Supervisor restarts) within HubWindow so operators have a quick audit trail.
  • Tray icon alignment – The tray honors High Contrast, light/dark themes, and PMv2 DPI updates. Clicking restores the window; right-click surfaces diagnostics and exit.

Upcoming refactor highlights (In progress)

  • Unified layout – HubWindow is moving to a flexible column layout so capture lanes, SmrtSpaces, and Support live in consistent tiles across resolutions.
  • Settings surface – Feature settings (provider credentials, hotkeys, retention toggles) move out of ad-hoc dialogs into a first-party Settings view hosted inside HubWindow.
  • SmrtSpace-aware navigation – Active space selection will drive breadcrumbs, Quick Save defaults, and upcoming dashboards (recent captures, support tickets).
  • Status timeline – A live activity log (similar to the shared state pane) will show job queues, Supervisor state changes, and recent capture activity without opening logs.
  • Accessibility & input – Keyboard-first navigation plus screen-reader annotations for every strip; touch affordances for Windows tablets.

We will annotate this page with exact build numbers as each of these improvements lands. For now, expect incremental updates with every supervisor + HubWindow drop.

HubWindow remains the anchor for all of these workflows. Even while the refactor reshapes the UI, operators should continue treating HubWindow as the place to launch automation, monitor health, and hand evidence to Support. Updates to this doc will track the refactor milestones so training material stays trustworthy.