[P2] TUI Interface for Headless Operations

[unclesp1d3r]

Priority: P2 — Ouroboros Stretch Goal

Source: Ouroboros design strategy — Control API + TUI

Context

Ouroboros envisions a terminal UI for operators who prefer CLI workflows or need headless access (SSH into a server, monitor campaigns without a browser). This builds on top of the Control API.

What hash_hive Would Need

1. Control API (prerequisite — see hash_hive Control API for Automation - MERN Migration Task 11 #25/Epic: Control API/Automation - Machine-Readable Interface for CLI and Scripting #38) — Machine-readable REST API for all operations
2. TUI framework — Terminal UI application (Ink for Node.js, or a separate Go/Rust binary)
3. Core views — Dashboard summary, campaign list/detail, agent status, results stream
4. Interactive operations — Create campaigns, manage agents, pause/resume from terminal
5. Live updates — WebSocket or polling for real-time terminal display

Dependencies

• Control API (hash_hive Control API for Automation - MERN Migration Task 11 #25/Epic: Control API/Automation - Machine-Readable Interface for CLI and Scripting #38) must be implemented first

Related hash_hive Issues

• Control API for Automation - MERN Migration Task 11 #25 (Control API), Epic: Control API/Automation - Machine-Readable Interface for CLI and Scripting #38 (Control API Epic)

---

Dependencies

Blocks: None
Blocked by: #38 (Control API — TUI requires machine-readable API)

[unclesp1d3r]

Dependencies

Blocked by: #25 / #38 (Control API) — TUI requires a machine-readable REST API for all operations.