Context
Part of #6230 (chat interface spec — the overall scope/backend/placement decision is still open there). Independent of that decision, it's useful groundwork to know what this codebase's existing ui-kit/apps/loopover-ui component library already has that a future chat surface could reuse — a message list, a composer/input box, a streaming-text renderer, anything typing-indicator-adjacent — versus what would need to be built from scratch.
Requirements
- Audit
apps/loopover-ui/src/components/** (and any shared ui-kit package if one exists separately) for components already resembling: a scrollable message/timeline list, a text composer with submit-on-enter, a streaming/incremental text renderer (check if anything here already handles SSE/streaming responses, since MCP tool results or an LLM response would need one), and any existing "typing"/loading-in-progress indicator pattern.
- Produce a short written inventory: what exists and is reusable, what's close but would need adaptation, what's entirely absent.
- Do not build anything new — this is a research/audit deliverable only.
Deliverables
Expected Outcome
Whoever eventually implements the chat interface (once #6230's scope is decided) starts from an accurate picture of what's reusable, instead of assuming a blank slate or missing something that already exists.
Links & Resources
Context
Part of #6230 (chat interface spec — the overall scope/backend/placement decision is still open there). Independent of that decision, it's useful groundwork to know what this codebase's existing
ui-kit/apps/loopover-uicomponent library already has that a future chat surface could reuse — a message list, a composer/input box, a streaming-text renderer, anything typing-indicator-adjacent — versus what would need to be built from scratch.Requirements
apps/loopover-ui/src/components/**(and any sharedui-kitpackage if one exists separately) for components already resembling: a scrollable message/timeline list, a text composer with submit-on-enter, a streaming/incremental text renderer (check if anything here already handles SSE/streaming responses, since MCP tool results or an LLM response would need one), and any existing "typing"/loading-in-progress indicator pattern.Deliverables
Expected Outcome
Whoever eventually implements the chat interface (once #6230's scope is decided) starts from an accurate picture of what's reusable, instead of assuming a blank slate or missing something that already exists.
Links & Resources
apps/loopover-ui/src/components/