feat(frontend): agent chat streaming slice + RAG example demo#4780
feat(frontend): agent chat streaming slice + RAG example demo#4780mmabrouk wants to merge 2 commits into
Conversation
Ports the AgentChatSlice frontend (ai-sdk useChat over the agent /messages stream) and the RAG_QA_chatbot example onto the current functional agent branches. See the PR description for the note to Arda.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
dosubot
Bot
added
size:XXL
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Railway Preview Environment
|
The agent-chat slice transport relied on the server defaulting to a stream. The real /messages endpoint only streams when the client sends Accept: text/event-stream; otherwise it returns a batch JSON body, which useChat cannot render. Send the SSE Accept header so streamed assistant replies show up.
1 participant
What this is
This ports the AgentChatSlice frontend and the RAG_QA_chatbot example from
fe-feat/agent-streaming-sliceonto the restructured agent branches. It adds the slice (web/oss/src/components/AgentChatSlice), the agent-chat page route (oss + ee), the three npm deps it needs (ai,@ai-sdk/react,@ant-design/x-markdown), theNEXT_PUBLIC_AGENT_CHAT_*env flags, and the example backend.Note to Arda
Your branch carried the whole agent feature, not just the frontend. While you were building the chat slice, the agent backend was restructured into a stack of focused functional PRs (#4771 to #4777). So the backend, docs, and playground controls on your branch are now an older, pre-refactor copy of work those PRs supersede. To avoid regressing them, this PR takes only the parts that are genuinely yours and new: the frontend slice and the example. Nothing else from your branch is included.
What moved, so you can re-point any imports:
services/oss/src/harness/*is now in the SDK atsdks/python/agenta/sdk/agents/(ports + adapters). See feat(sdk): agent runtime behind backend/harness ports #4771.services/agent/src/tools/client.tsis nowcallback.ts. See feat(agent): runner wire contract and tool execution #4773.services/oss/src/agent/tools.pyis now atools/package. See feat(agent): agent workflow service and tool-resolution API #4772.docs/design/agent-workflows/ground-truth.md; the old POCs moved undertrash/. See docs(agent): agent-workflows design and ground truth #4777.The slice's wire contract (
transport.tsagainst the/messagesVercel stream) lines up with the backend in #4772 (the agent service) and #4771 (the SDK messages adapter), so it should run against the current backend unchanged.How to run
pnpm installinweb/for the new deps.NEXT_PUBLIC_AGENT_CHAT_APIto your agent/messagesendpoint.Stacking and review notes
pnpm lint-fixpass is expected before merge.