Skip to content

fix(tui): swap ⌨ host-band glyph for a state triangle (▸/▾)#209

Merged
aoos merged 1 commit into
masterfrom
tui/host-band-glyph
Jun 29, 2026
Merged

fix(tui): swap ⌨ host-band glyph for a state triangle (▸/▾)#209
aoos merged 1 commit into
masterfrom
tui/host-band-glyph

Conversation

@aoos

@aoos aoos commented Jun 29, 2026

Copy link
Copy Markdown
Owner

The host-terminal band header led with a keyboard emoji () — the lone outlier against the dashboard's sparse glyph vocabulary ( islands, / state dots). Replace it with a directional triangle that doubles as an expand/collapse affordance:

▸ Host ● 2 terminals · not contained   [/] expand
▾ Host terminals · not contained   [/] collapse

points right when collapsed (closed), points down when expanded (open).

Two lines in renderBand (cmd/dejima/tui.go). No behavior change. Band tests assert the header contains "Host" (not the glyph), so they stay green; go test ./cmd/dejima/... and go vet clean locally.

🤖 Generated with Claude Code

The host-terminal band header led with a keyboard emoji — the lone
outlier against the dashboard's sparse glyph set (◆/●/○). Swap it for a
directional triangle that doubles as an expand/collapse affordance:
▸ when collapsed (points right), ▾ when expanded (points down).

Header text still contains "Host", so the band tests stay green.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ENXLudmsVvUbqa2hh1NvwS
@aoos aoos merged commit fe90bdd into master Jun 29, 2026
4 checks passed
@aoos aoos deleted the tui/host-band-glyph branch June 29, 2026 16:43
aoos added a commit that referenced this pull request Jul 3, 2026
…not the set-up-a-server question (#209) (#272)

detectFirstRunContext() classified a machine purely on daemon-reachability +
the DEJIMA_HOST env var. A teammate who ran `dejima join <invite>` has a saved
ACTIVE connection profile but no DEJIMA_HOST and no local daemon — so when that
remote was momentarily unreachable, the classifier fell through to
firstRunFreshHost and asked them to "set up a server on this machine" instead of
opening their dashboard. A live teammate hit exactly this.

Fix: once the daemon is unreachable, consult resolveTarget() (which already
resolves DEJIMA_HOST, the -p/--host flag, AND the saved active profile). If ANY
target exists (source != "local"), the machine is a client whose host is down —
route to firstRunClientUnreachable (troubleshoot → dashboard), never
firstRunFreshHost/Generic. Also generalize the "can't reach host" message to
name a profile/flag target, not only DEJIMA_HOST.

Regression tests: joined profile + unreachable → firstRunClientUnreachable; and
the negative guard (no target + unreachable → not a configured client) so the
fix doesn't over-broaden.


Claude-Session: https://claude.ai/code/session_01ENXLudmsVvUbqa2hh1NvwS

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant