Repository navigation
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the chat UI/UX in the frontend, adding “Think longer” step display, widening the chat layout, and introducing a first pass at editing prior user queries in a conversation.
Changes:
- Add “thinking steps” capture/display via a collapsible dropdown in assistant messages.
- Add edit-query flow that truncates conversation history from the edited message onward and re-submits.
- Expand chat input/message container widths and adjust spacing/styling of message/source components.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 11 comments.
Show a summary per file
| File | Description |
|---|---|
| frontend/src/pages/Index.tsx | Adds edit-state handling, focus behaviors, and “thinking steps” streaming support; refactors assistant finalization. |
| frontend/src/lib/chat-store.ts | Extends Message with thinkingSteps storage. |
| frontend/src/lib/api.ts | Reworks extractSources parsing logic (but introduces a “first vs last Sources:” parsing bug + debug logging). |
| frontend/src/components/chat/ChatSources.tsx | Minor UI layout tweaks for sources list rendering. |
| frontend/src/components/chat/ChatMessage.tsx | Adds edit button UI and thinking dropdown rendering for assistant messages. |
| frontend/src/components/chat/ChatInput.tsx | Adds autofocus behavior and a data-chat-input marker; increases textarea max height. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Thanks for this, @achyu-dev. It needs a rebase before it can be reviewed, because the repository was restructured after it was opened. The frontend moved. #73 combined the services into a monorepo on 2026-09-07, so the frontend now lives at
Those changes add a Before you rebase, a few things worth knowing:
Once it's rebased onto |
|
Thank you for this, and sorry it has sat open since June. Closing it, but not because the work was wrong — the opposite. Two things have happened since you opened it:
So rather than ask you to rebase onto a moving target, the remaining work is written up as #112 against the current tree, with your screenshots referenced for the intended shape. Both parts are still wanted:
Editing a submitted query stays tracked separately in #70. If you would like to pick up #112, it is yours — it is a clean start against the current frontend rather than a rebase of this branch. |
Resolves #70 and also implements >