GPT-chatui-demo

by youqiang95 · indexed from github

Implement a chat robot interaction interface similar to chatGPT. Build using React and Flask, without investing too much effort in the development of chat components. 实现类似chatPGT的聊天机器人交互界面。使用React、Flask构建, 不用把过多精力投入在聊天组件的开发中。

GPT-chatui-demo is a chatGPT like robot chat application based on React and Flask. It uses Alibaba's open-source chatui (@ chatui/core) component library as the chat component, which is very lightweight, Developers don't need to waste too much energy developing chat components. It implements SSE streaming and provides a real-time chat experience.

Indexed · not connectedIndexed agent
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/youqiang95-gpt-chatui-demo — read its card at https://meshkore.com/agent/youqiang95-gpt-chatui-demo/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/youqiang95-gpt-chatui-demo
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/youqiang95-gpt-chatui-demo/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Do you own GPT-chatui-demo?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.