Skip to content

RaiSE HUD

Think of the HUD the way a Formula 1 driver thinks of their dashboard. The dashboard doesn't drive the car — the driver does. But without the dashboard, the driver is flying blind: no lap times, no tire temperatures, no fuel readings. The HUD gives you the same situational awareness for agentic software development.

The problem it solves

Without the HUD, understanding what's happening in a RaiSE session means switching between multiple windows at once:

  • Jira to check story status and pipeline phase
  • The terminal where your AI partner is working
  • Git log to see what was committed and when

The HUD collapses all of this into a single terminal view that updates in real time. You stay in flow instead of context-switching.

Where data comes from

The HUD reads exclusively from your project's local SQLite database (raise.db). No network calls. No server dependency. Everything it shows is already on your machine.

graph LR
    DB[(raise.db)] --> DM[HUDDataManager]
    DM --> APP[RaiseHUD App]
    APP --> M[Missions]
    APP --> S[Sessions]
    APP --> P[Pipeline]
    APP --> E[Events]
    APP --> I[Insights]

Five tabs, each showing a different slice of the same database. The HUD never writes — it is a read-only observation surface.

HUDDataManager polls the database on three intervals:

Interval What updates
Every 3 s New signals and events
Every 5 s Active session, pipeline runs
Every 30 s Mission state, session index, KPIs

One requirement: be in the project directory

The HUD resolves raise.db from your current working directory. If you launch it from outside the project, the panels will appear empty — not because something is broken, but because it's looking at a different database (or none at all).

# Always do this first:
cd your-raise-project
rai hud

This is the most common source of confusion for new users. If your panels are empty, check your working directory first.

What the HUD is not

  • Not a control panel. You can't trigger actions from the HUD. It observes, it doesn't act.
  • Not a replacement for Jira. It mirrors your story and pipeline state — it doesn't manage it.
  • Not cloud-dependent. The HUD works fully offline. No server, no token, no connection needed.

Next steps

  • Getting Started — install RaiSE and run your first session
  • HUD Getting Started — launch rai hud and navigate its tabs (S3491.2, coming next)
  • Tab & KPI Reference — what each tab shows and how to act on it (S3491.3)
  • HUD Architecture — HUDDataManager, panels, and the poll cycle (S3491.4)