felixm
5eea909029
Style the hqt session's status bar with the same Frappé palette the TUI uses: blue session badge, Mantle background, peach current-window highlight, muted inactive windows, styled clock/date. The TUI window shows just its house glyph (no index/flag/text). Applied from the TUI's on_mount since the os.execvp bootstrap can't run follow-up tmux commands. All options are session-scoped (never -g), so the user's other tmux sessions and personal config are untouched. Window-scoped options (current-window highlight, pane borders, mode style) have no session scope in tmux, so they're painted per-window on every existing window in apply_theme and on each new harness window in new_window — otherwise a window spawned after mount would render with no peach highlight. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
hqt — HQ Terminal
A TUI for orchestrating AI coding harness sessions (Claude Code, Kiro, Aider, etc.) via tmux. Manage multiple AI sessions across projects from a single terminal interface.
Quick Start
uv pip install -e .
hqt
Commands
| Command | Description |
|---|---|
hqt |
Launch the TUI (inside tmux) |
hqt doctor |
Check system requirements |
hqt list |
List projects and sessions |
Key Bindings
| Key | Action |
|---|---|
q |
Quit |
n |
New session |
a |
Add project |
e |
Edit project |
Tab |
Switch panel |
d |
Delete session |
Enter |
Attach to session (auto-resumes if not running) |
r |
Rename session |
s |
Stop session |
Architecture
hqt uses a layered architecture: a Click CLI bootstraps into a Textual TUI, which drives service classes (ProjectService, SessionService) backed by SQLite via SQLAlchemy. Sessions are spawned as tmux windows through TmuxManager, with harness-specific configuration provided by pluggable HarnessConfigurator implementations discovered at runtime.