| name | verifier-tui |
| description | Verify TUI client changes end-to-end by driving build/lurker-tui in an isolated tmux session against a seeded backend. Use when verifying changes under cmd/tui/ (rendering, keybindings, sidebar, buffer switching, mouse support) at the real terminal surface. Not for backend-only changes and not for running unit tests (task test-tui is CI's job). |
Verifier: TUI client
Runtime-verify cmd/tui/ changes by launching the real TUI in tmux against a seeded backend and capturing panes as evidence.
Build & launch
task seed-test
task dev-test
task build-tui
- Readiness probe for the backend:
curl -s localhost:8080/whoami.
- TUI config: defaults to
backend_url: http://localhost:8080 — no config file needed against dev-test. Explicit config falls back ./tui-config.yaml → ~/.config/lurker/tui.yaml (see cmd/tui/config.go).
- Run the TUI in an isolated tmux server (never the user's default server):
tmux -L lurker-verify new-session -d -s tui -x 200 -y 50
tmux -L lurker-verify send-keys -t tui "./build/lurker-tui" Enter
sleep 3
tmux -L lurker-verify capture-pane -t tui -p
- 200x50 gives the sidebar + viewport room; smaller panes truncate the sidebar.
Drive it
Keys (from cmd/tui/model.go handleKey):
C-k — channel switcher: send C-k, then type a fragment (e.g. go-nuts), then Enter. Most reliable way to switch buffers.Escape — toggles focus between sidebar and input (NOT a marker/overlay key like the web UI).Up/Down — navigate sidebar when it has focus; Enter selects.PgUp/PgDn — viewport scroll; PgUp at top requests older history.C-d twice — quit (double-tap confirm).
Sidebar renders unread counts as (N) suffixes, e.g. #go-nuts (3) — capture-pane and grep for them.
Fakes & fixtures
- Seeded networks never connect to real IRC. For live message arrivals use
cmd/fakeircd (task fake-ircd: IRC on :6667, control on :6668). Point a network at it via the REST API — no config file needed:
NET=$(curl -s -X POST localhost:8080/api/networks -H 'Content-Type: application/json' \
-d '{"name":"testnet","host":"127.0.0.1","port":6667,"tls":false,"nick":"lurkertest","connect_commands":["JOIN #verify"]}' | jq -r .id)
curl -s -X POST "localhost:8080/api/networks/$NET/connect"
echo "#verify :hello from bob" | nc -w1 127.0.0.1 6668
- Alternative: bootstrap via a
CONFIG_PATH yaml with a networks: entry at 127.0.0.1:6667 — but note YAML is authoritative, so the seeded libera/oftc networks get marked disabled and vanish from the sidebar. The API path avoids that.
- Server-side state assertions:
curl -s localhost:8080/api/state and inspect buffers[].unread / last_seen_id to check what the TUI actually told the backend.
Testability hook
model.sendWS func(cmd wsCmd) error — when non-nil, all outbound WS commands route through it instead of the real connection (sendCmdAsync in cmd/tui/model.go). Unit tests install a recorder to assert on mark_read etc.; see markerModel in cmd/tui/model_test.go. There is no inbound-injection hook at the runtime surface — inbound events are unit-tested via handleWSEvent(wsEvent{...}) directly.
Marker behavior (since 2026-07-03)
TUI has web-parity new-messages marker (ai-docs/behaviors/new-messages-marker.md, "TUI parity" section): entering a buffer sends mark_read and clears badges but keeps the ── New messages ── divider; the divider clears on buffer exit or Esc (Esc also toggles focus — pre-existing binding). Grep captured panes for New messages. Server-side check: /api/state buffers[].last_seen_id should advance after the TUI views a buffer.
Cleanup
tmux -L lurker-verify send-keys -t tui C-d; sleep 0.3
tmux -L lurker-verify send-keys -t tui C-d
tmux -L lurker-verify kill-server
