en un clic
hud
Show or configure the OMQ HUD (two-layer statusline)
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Menu
Show or configure the OMQ HUD (two-layer statusline)
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Diagnose and fix oh-my-qwencode installation issues
Guide on using oh-my-qwencode plugin
Run deep investigation of architecture, bugs, performance issues, or dependencies and return structured findings with file:line evidence. Use when a user says 'analyze', 'investigate', 'why does', 'what's causing', or needs root cause analysis before making changes. Routes to architect agent or Qwen Code MCP for thorough cross-file reasoning.
Ask Claude via local CLI and capture a reusable artifact
Ask Gemini via local CLI and capture a reusable artifact
Full autonomous execution from idea to working code
| name | hud |
| description | Show or configure the OMQ HUD (two-layer statusline) |
| role | display |
| scope | .omq/** |
The OMQ HUD uses a two-layer architecture:
Layer 1 - Qwen Code built-in statusLine: Real-time TUI footer showing model, git branch, and context usage. Configured via [tui] status_line in ~/.qwen/config.toml. Zero code required.
Layer 2 - omq hud CLI command: Shows OMQ-specific orchestration state (ralph, ultrawork, autopilot, team, pipeline, ecomode, turns). Reads .omq/state/ files.
| Command | Description |
|---|---|
omq hud | Show current HUD (modes, turns, activity) |
omq hud --watch | Live-updating display (polls every 1s) |
omq hud --json | Raw state output for scripting |
omq hud --preset=minimal | Minimal display |
omq hud --preset=focused | Default display |
omq hud --preset=full | All elements |
[OMQ] ralph:3/10 | turns:42
[OMQ] ralph:3/10 | ultrawork | team:3 workers | turns:42 | last:5s ago
[OMQ] ralph:3/10 | ultrawork | autopilot:execution | team:3 workers | pipeline:exec | turns:42 | last:5s ago | total-turns:156
omq setup automatically configures both layers:
[tui] status_line to ~/.qwen/config.toml (Layer 1).omq/hud-config.json with default preset (Layer 2)focused; if HUD/statusline changes do not appear, restart Qwen Code once.Configured in ~/.qwen/config.toml:
[tui]
status_line = ["model-with-reasoning", "git-branch", "context-remaining"]
Available built-in items (Qwen Code v0.101.0+):
model-name, model-with-reasoning, current-dir, project-root, git-branch, context-remaining, context-used, five-hour-limit, weekly-limit, qwen-version, context-window-size, used-tokens, total-input-tokens, total-output-tokens, session-id
The omq hud command reads these state files:
.omq/state/ralph-state.json - Ralph loop iteration.omq/state/ultrawork-state.json - Ultrawork mode.omq/state/autopilot-state.json - Autopilot phase.omq/state/team-state.json - Team workers.omq/state/pipeline-state.json - Pipeline stage.omq/state/ecomode-state.json - Ecomode active.omq/state/hud-state.json - Last activity (from notify hook).omq/metrics.json - Turn countsHUD config stored at .omq/hud-config.json:
{
"preset": "focused"
}
If the TUI statusline is not showing:
omq setup to configure [tui] sectionIf omq hud shows "No active modes":