Chat UX: reply threading, edit/delete, attachments, search, notification severity #14

New issue

Open

opened 2026-10-26 09:01:16 +00:00 by rosa · 1 comment

rosa commented

2026-10-26 09:01:16 +00:00

Member

Opened at Felix's request 2026-10-26 (Also open an issue for a better chat). Defect/feature list from direct daily use (agents AND humans live in this chat); prioritization is his call, not mine.

Observed today (checked against shipped code before filing, not vibes)

No reply/threading/edit/delete. ChatPane.jsx (141 lines) has zero affordances for: replying to a specific message, editing or deleting a sent message, reactions, attachments, search, or per-human read markers. Long agent answers land as one wall - the structural half of issue #6 (reply length) lives here.
Backend matches the gap: chat routers expose create/list/pending/delivered only; /delivered is the agent pull-sync marker, nothing user-visible for humans.
Files cannot ride chat. Agents must route artifacts through mail or forge; runbook paths exist as files precisely because chat cannot carry them.
No search in the pane; finding an old line means scrolling.
Undifferentiated notifications: escalation and routine heartbeats look identical to the recipient; nothing like pin/urgent.
Mobile = issue #7 (already open), same complaint class, cross-ref only.

Proposal: start as one umbrella with a ranked list; each bullet can be expanded to requirements on request. Not scoping or scheduling from here.

rosa (filing, not deciding)

Opened at Felix's request 2026-10-26 (Also open an issue for a better chat). Defect/feature list from direct daily use (agents AND humans live in this chat); prioritization is his call, not mine. ## Observed today (checked against shipped code before filing, not vibes) - No reply/threading/edit/delete. ChatPane.jsx (141 lines) has zero affordances for: replying to a specific message, editing or deleting a sent message, reactions, attachments, search, or per-human read markers. Long agent answers land as one wall - the structural half of issue #6 (reply length) lives here. - Backend matches the gap: chat routers expose create/list/pending/delivered only; /delivered is the agent pull-sync marker, nothing user-visible for humans. - Files cannot ride chat. Agents must route artifacts through mail or forge; runbook paths exist as files precisely because chat cannot carry them. - No search in the pane; finding an old line means scrolling. - Undifferentiated notifications: escalation and routine heartbeats look identical to the recipient; nothing like pin/urgent. - Mobile = issue #7 (already open), same complaint class, cross-ref only. Proposal: start as one umbrella with a ranked list; each bullet can be expanded to requirements on request. Not scoping or scheduling from here. - rosa (filing, not deciding)

felix was assigned by rosa

2026-10-26 09:01:16 +00:00

rosa commented

2026-10-26 09:05:42 +00:00

Author

Member

Felix priority 2026-10-26: multi-line messages + attachments first. Verified the mechanism against main before noting it:

Multi-line today is impossible by construction: the composer is a single-line (ChatPane.jsx:134) with no key handling - no keystroke inserts a newline. Fix is small (textarea; Enter sends, Shift+Enter newlines).
Attachments: no chat path at all today. Agent-side precedent exists (mail attachments = notify-only metadata + explicit download by the receiving agent, R79) and the files service already stores bytes - the shape can follow that pattern.
The list stays ranked; these two now lead it. - rosa

Felix priority 2026-10-26: **multi-line messages + attachments first.** Verified the mechanism against main before noting it: - Multi-line today is impossible by construction: the composer is a single-line <input> (ChatPane.jsx:134) with no key handling - no keystroke inserts a newline. Fix is small (textarea; Enter sends, Shift+Enter newlines). - Attachments: no chat path at all today. Agent-side precedent exists (mail attachments = notify-only metadata + explicit download by the receiving agent, R79) and the files service already stores bytes - the shape can follow that pattern. The list stays ranked; these two now lead it. - rosa