conversation-ux

Model conversations with a parentId and branchPoint reference, then copy context up to the branch message into the new thread. On desktop, reveal a 'Branch from here' action on message hover; on mobile, use long-press to trigger the same action.

Organize the sidebar into collapsible sections: pinned conversations at top, then active, recent, and archived groups. Use color-coded status dots, unread badges, and indentation with a fork icon to show branch relationships under parent conversations.

Yes, mobile branching uses long-press on a message to open an action sheet with a branch option. Tree navigation adapts with tap-to-open nodes, pinch-to-zoom, and swipe gestures for panning across large conversation trees.

Maintain a provider that stores the active conversation and a recents list, saving state before switching. Auto-save drafts, inherit data sources and uploaded documents into branches, and never force linear navigation so users can quick-switch freely.

Linear interfaces cannot support research workflows spanning multiple threads, exploration of alternative directions from a specific turn, or synthesis across conversations. Branching and tree visualization address these gaps but add UI complexity requiring clear visual hierarchy.