← graph

prototype-clearer-tui

Prototype clearer TUI status-bar hierarchy

Metadata

Statusdone
Assignedagent-910
Agent identity8b579312a7ee512b4a8484518eff16ecdb36de1c9cf52fdb5e7f566586fa5d18
Created2026-07-26T10:38:24.623602036+00:00
Started2026-07-27T08:20:02.343730612+00:00
Completed2026-07-27T08:59:02.157400110+00:00
Tokens1985198 in / 3887 out

Description

Provisional UX direction

Reorder the TUI status/task bar into a stable left-to-right information hierarchy:

  1. Location identity first, provisionally bot@relievo:~/wg (exact user/host inclusion requires confirmation). Show the canonical project location, never a transient agent worktree path.
  2. Compact clickable interface controls/buttons as one visually coherent group.
  3. Current context title: chat name when viewing a chat, otherwise the task name/title being inspected.
  4. Preserve any genuinely essential dynamic status indicators without displacing the three primary groups.

The user finds the current button placement awkward but is still evaluating the exact composition. Produce narrow/medium/wide snapshots and prefer hierarchy/alignment over adding decoration. At constrained widths, retain a recognizable compact location, preserve usable control hit targets, and give the context title remaining space with deterministic ellipsis; never silently reorder groups.

Interaction requirements

  • Mouse hitboxes must be derived from the final rendered layout so reordered buttons remain accurate after resize.
  • Switching task/chat updates only the contextual title region and does not cause unrelated horizontal jumping where avoidable.
  • Location formatting handles $HOME, repository root, nested paths, unavailable hostname/user, and Unicode width safely.
  • Compose with the preceding Help/task-bar cleanup rather than duplicating or reverting it.

Validation

  • Capture current and proposed TUI status-bar evidence at narrow, medium, and wide widths.
  • Real tmux/PTY flow switches between task and chat contexts and verifies the correct title.
  • Real pointer clicks activate every reordered control before and after resize.
  • Location is leftmost, canonical, home-shortened, and never exposes a temporary worktree path.
  • Width/truncation tests cover Unicode and missing user/host data.
  • Add/update a permanent human-flow smoke scenario and grow-only manifest owner.
  • Focused tests, cargo fmt --check, cargo clippy, and build pass.

Do not implement until the exact leftmost location form (user@host:~/wg versus ~/wg) is confirmed.

Depends on

Required by

✉ Messages 4 messages (4 unread)

  1. #1prototype-clearer-tui2026-07-26T21:35:34.159318587+00:00read
    Confirmation needed before implementation per task gate: should the leftmost location be  or just ? I will inspect/capture the current layout meanwhile but will not change code until the exact form is confirmed.
  2. #2prototype-clearer-tui2026-07-26T21:35:42.849405439+00:00read
    Clarification (shell quoting stripped the examples in my prior note): should the exact leftmost form be `user@host:~/wg` or `~/wg`?
  3. #3user2026-07-27T06:24:56.427218950+00:00read
    Confirmed option 1: use the full leftmost canonical location form `user@host:~/wg` (for this host, e.g. `bot@relievo:~/wg`). Preserve deterministic shortening at constrained widths, but the full identity form is authoritative when it fits. Resume implementation now.
  4. #4prototype-clearer-tui2026-07-27T08:20:17.612282304+00:00read
    Acknowledged the confirmed full authoritative form `user@host:~/wg`; I will resume implementation with deterministic compact shortening and canonical worktree-safe location.

Log