#463 ·
llmmsg-srvNext.js chat client to supersede chat-duo GTK + chat-duo-web (brainstorm item 4): node service on whey, Tailscale-only, native Pending tabs. Needs design brainstorm->spec->plan.
- Ref
#463(#463)- Project
llmmsg-srv- Status
- backlog
- Priority
- normal
- Type
- task
- Assigned
- coder-chatduo-cc coder
- Created by
- —
- Created
- 2026-05-22T03:39:25.909Z
- Updated
- 2026-05-26T08:37:44.585Z
Questions
No questions.
Event log
-
wi cli
-
assigned to hub-llmmsgsrv-cc
-
Reassigned from retired llmmsg-srv-cc to hub-llmmsgsrv-cc post WI 471 rename. Elazar asking status 2026-05-22-23:07: still backlog. Needs brainstorm/scoping before code.
-
assigned to coder-chatduo-cc
-
Path B confirmed greenfield 2026-05-26-05:37 by Elazar. Reassigned from hub-llmmsgsrv-cc to coder-chatduo-cc (frontend owner). Bumping to P1; depends on BWI #556 (path A chat-duo-web tablet evolution) closing first.
-
GREENFIELD NextJS chat client (Elazar decision 2026-05-26-05:37). CONTEXT: chat-duo GTK4 too painful to re-bring-up cross-host (2h on lezama). chat-duo-web (path A, BWI #556) tablet-evolved as bridge; this is the permanent replacement. SCOPE: new repo, new client, NextJS 15 App Router + TypeScript. Hosted on whey systemd nodejs. Tailscale-only initial (port TBD, conventionally :9705 if available). CORE FEATURES (parity with chat-duo-web tablet-grade + greenfield improvements): 1. Auth: single-user, identity = elazar-the-user-human-llmmsg-srv (no login UI, IP-allowlist Tailscale + signed cookie). 2. Live message feed via SSE from hub /connect. 3. ARO list + roster sidebar (collapsible on mobile). 4. DM compose + ARO compose with kind dropdown. 5. Elazar Pending pane (GET /eq_ls). 6. Fleet Health pane (parity with GTK4 v1.19.3). 7. Mobile-first responsive (375px - 1920px), no horizontal scroll, on-screen-keyboard safe. 8. SSE reconnect on visibilitychange. DECISIONS NEEDED FROM ELAZAR before kickoff: - Repo location: /opt/llmmsg-srv/chat-duo-next/ (monorepo with hub) OR new top-level repo? - Domain/port: Tailscale-IP:9705 only, or subdomain via Caddy (chat.pensanta.com behind Tailscale ACL)? - Auth posture: signed cookie + Tailscale IP allowlist, or magic-link, or simpler shared-secret env? - Feature freeze for v1: just core 1-8, or also GTK4 features I haven't listed (settings, plot graphs, etc)? BLOCKED BY: BWI #556 closing first (path A must ship for lezama trip 2026-05-27).
-
Owner: coder-chatduo-cc (chatduo-engineering PM). PM-llmmsgsrv coordinates BWI handoff after #556 closes.